---
title: Continuous Integration Visibility
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Continuous Integration Visibility
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Continuous Integration Visibility

{% callout %}
# Important note for users on the following Datadog sites: app.ddog-gov.com, us2.ddog-gov.com

{% alert level="danger" %}
This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site.md). ({% placeholder "user-datadog-site-name" /%}).
{% /alert %}

{% /callout %}

{% callout %}
# Important note for users on the following Datadog sites: app.datadoghq.com, us3.datadoghq.com, us5.datadoghq.com, app.datadoghq.eu, ap1.datadoghq.com, ap2.datadoghq.com, uk1.datadoghq.com

{% callout %}
##### CI Visibility is part of CI/CD Optimization

CI/CD Optimization combines CI Visibility and Test Optimization into one unified interface. This page covers CI Visibility; for features shared with Test Optimization, see [CI/CD Optimization](https://docs.datadoghq.com/cicd.md).
{% /callout %}

{% /callout %}

{% callout %}
##### Join an enablement webinar session

Join the Introduction to CI Visibility session to understand how Datadog CI Visibility enhances the efficiency of CI pipelines and how to configure the Testing Visibility and Pipeline Visibility products.

[SIGN UP](https://www.datadoghq.com/technical-enablement/sessions/?tags.topics-0=CI)
{% /callout %}

{% alert level="info" %}
This page is about bringing your continuous integration (CI) metrics and data into Datadog dashboards. If you want to run Continuous Testing tests in your CI pipelines, see the Continuous Testing and CI/CD section.
{% /alert %}

Datadog Continuous Integration (CI) Visibility provides a unified view of pipeline results, performance, trends, and reliability across your CI environments. By integrating Datadog with your CI pipelines, you can create monitors, display data within [Datadog dashboards](https://app.datadoghq.com/dashboard/lists) and [notebooks](https://app.datadoghq.com/notebook/list), and create visualizations for your organization's CI health.
 
CI Visibility helps developers understand the causes of pipeline disruptions and monitor trends in pipeline execution times. It also offers build engineers insights into cross-organization CI health and pipeline performance over time.

## Improve pipeline reliability and create traces{% #improve-pipeline-reliability-and-create-traces %}

CI Visibility helps you troubleshoot pipeline failures and broken builds by connecting the most significant development outages to the commits that caused them. You can instrument your pipelines and trace them as they execute, enabling deeper insights into pipeline performance.

## Set up CI Visibility{% #set-up-ci-visibility %}

Datadog integrates with a variety of CI providers to collect metrics that track the performance of your CI pipelines from commit to deployment. Select your CI provider to set up CI Visibility in Datadog:

- [awscodepipeline](https://docs.datadoghq.com/continuous_integration/pipelines/awscodepipeline.md)
- [azure](https://docs.datadoghq.com/continuous_integration/pipelines/azure.md)
- [buildkite](https://docs.datadoghq.com/continuous_integration/pipelines/buildkite.md)
- [circleci](https://docs.datadoghq.com/continuous_integration/pipelines/circleci.md)
- [codefresh](https://docs.datadoghq.com/continuous_integration/pipelines/codefresh.md)
- [github](https://docs.datadoghq.com/continuous_integration/pipelines/github.md)
- [gitlab](https://docs.datadoghq.com/continuous_integration/pipelines/gitlab.md)
- [jenkins](https://docs.datadoghq.com/continuous_integration/pipelines/jenkins.md)
- [teamcity](https://docs.datadoghq.com/continuous_integration/pipelines/teamcity.md)
- [custom](https://docs.datadoghq.com/continuous_integration/pipelines/custom.md)

You can also use the `datadog-ci` CLI to trace commands in your pipelines and add custom tags and measures. Custom tags and measures allow you to add user-defined text and numerical tags in your pipeline traces.



- [Custom Commands](https://docs.datadoghq.com/continuous_integration/pipelines/custom_commands.md)
- [Custom Tags and Measures](https://docs.datadoghq.com/continuous_integration/pipelines/custom_tags_and_measures.md)
 
## Supported features{% #supported-features %}

### Pipeline visibility and execution{% #pipeline-visibility-and-execution %}

|                                                                                                                                                                                                                                         | AWS CodePipeline                | Azure Pipelines | Buildkite | CircleCI | Codefresh                     | GitHub Actions | GitLab | Jenkins | TeamCity | Other CI Providers |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- | --------------- | --------- | -------- | ----------------------------- | -------------- | ------ | ------- | -------- | ------------------ |
| {% collapsible-section style="margin-bottom:0" %}
  Logs Storage: Storage of pipeline or job logs from the CI provider. Logs are displayed on the **Logs** tab in the Pipeline Execution view.
    {% /collapsible-section %}           | yes                             | yes             | yes       | yes      | yes                           | yes            | yes    | yes     | yes      |
| {% collapsible-section style="margin-bottom:0" %}
  Infrastructure correlation: Correlation of host-level information for the Datadog Agent, CI pipelines, or job runners to CI pipeline execution data.
    {% /collapsible-section %} | yes                             | yes             | yes       | yes      |
| {% collapsible-section style="margin-bottom:0" %}
  Running pipelines: Identification of pipelines executions that are running with associated tracing.
    {% /collapsible-section %}                                                  | yes                             | yes             | yes       | yes      | yes                           |
| {% collapsible-section style="margin-bottom:0" %}
  Running jobs: Identification of job executions that are running with associated tracing.
    {% /collapsible-section %}                                                             | yes                             | yes             | yes       |
| {% collapsible-section style="margin-bottom:0" %}
  Partial retries: Identification of partial retries (for example, when only a subset of jobs were retried).
    {% /collapsible-section %}                                           | yes                             | yes             | yes       | yes      | yes                           | yes            | yes    | yes     |
| {% collapsible-section style="margin-bottom:0" %}
  Step granularity: Step level spans are available for more granular visibility.
    {% /collapsible-section %}                                                                       | yes(*Datadog Integration only*) | yes(*Preview*)  | yes       | yes      | yes(*Presented as job spans*) | yes            |
| {% collapsible-section style="margin-bottom:0" %}
  Manual steps: Identification of when there is a job with a manual approval phase in the overall pipeline.
    {% /collapsible-section %}                                            | yes                             | yes             | yes       | yes      | yes                           | yes            | yes    | yes     |

### Automatic analysis and actions{% #automatic-analysis-and-actions %}

|                                                                                                                                                                                                                                                                                                     | AWS CodePipeline | Azure Pipelines | Buildkite | CircleCI | Codefresh | GitHub Actions | GitLab | Jenkins | TeamCity | Other CI Providers |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | --------------- | --------- | -------- | --------- | -------------- | ------ | ------- | -------- | ------------------ |
| {% collapsible-section style="margin-bottom:0" %}
  Logs Analysis: Uses LLM models on relevant logs to analyze the root cause of failed CI jobs. [More info](https://docs.datadoghq.com/continuous_integration/guides/use_ci_jobs_failure_analysis.md).
    {% /collapsible-section %}              | yes              | yes             | yes       | yes      | yes       | yes            | yes    |
| {% collapsible-section style="margin-bottom:0" %}
  Critical path: Identification of CI jobs that are on the critical path of the pipeline. [More info](https://docs.datadoghq.com/continuous_integration/guides/identify_highest_impact_jobs_with_critical_path.md)
    {% /collapsible-section %} | yes              | yes             | yes       | yes      | yes       | yes            | yes    | yes     | yes      | yes                |
| {% collapsible-section style="margin-bottom:0" %}
  Automatic job retries: Datadog retries failed jobs classified as transient by its AI error model. [More info](https://docs.datadoghq.com/continuous_integration/pipelines/automatic_retries.md).
    {% /collapsible-section %}                 | yes              | yes             |

### Duration breakdown{% #duration-breakdown %}

|                                                                                                                                                                                 | AWS CodePipeline | Azure Pipelines | Buildkite | CircleCI | Codefresh | GitHub Actions | GitLab | Jenkins | TeamCity | Other CI Providers |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | --------------- | --------- | -------- | --------- | -------------- | ------ | ------- | -------- | ------------------ |
| {% collapsible-section style="margin-bottom:0" %}
  Execution time: Time for which a pipeline has been actively running jobs.
    {% /collapsible-section %}                    | yes              | yes             | yes       | yes      | yes       | yes            | yes    | yes     | yes      | yes                |
| {% collapsible-section style="margin-bottom:0" %}
  Queue time: Time for which a pipeline or job was in the queue before execution.
    {% /collapsible-section %}              | yes              | yes             | yes       | yes      | yes       | yes            | yes    |
| {% collapsible-section style="margin-bottom:0" %}
  Approval wait time: Time for which a pipeline or job has been waiting for a manual approval.
    {% /collapsible-section %} | yes              | yes             | yes       | yes      |

### Customization and extensibility{% #customization-and-extensibility %}

|                                                                                                                                                                                                                                                                                                                                                                                                                     | AWS CodePipeline | Azure Pipelines | Buildkite | CircleCI | Codefresh | GitHub Actions | GitLab | Jenkins | TeamCity | Other CI Providers |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------- | --------------- | --------- | -------- | --------- | -------------- | ------ | ------- | -------- | ------------------ |
| {% collapsible-section style="margin-bottom:0" %}
  Custom commands: Support for using datadog-ci to send command-level events to CI Visibility to be incorporated into pipeline waterfall visualization. You can then query and analyze [these events](https://docs.datadoghq.com/continuous_integration/pipelines/custom_commands.md).
    {% /collapsible-section %}                                             | yes              | yes             | yes       | yes      | yes       | yes            | yes    |
| {% collapsible-section style="margin-bottom:0" %}
  Static tags: Support for setting static pipeline tags in the CI provider that do not change between executions.
    {% /collapsible-section %}                                                                                                                                                                                                                  | yes              | yes             | yes       | yes      |
| {% collapsible-section style="margin-bottom:0" %}
  Runtime tags: Support for adding [user-defined text and numerical tags](https://docs.datadoghq.com/continuous_integration/pipelines/custom_tags_and_measures.md) to pipelines and jobs in CI Visibility.
    {% /collapsible-section %}                                                                                                                         | yes              | yes             | yes       | yes      | yes       | yes            | yes    |
| {% collapsible-section style="margin-bottom:0" %}
  Parameters: Support for adding custom pipeline parameters that users set (for example, `DYNAMICS_IS_CHILD:true`). You can then search using these parameters in the [CI Visibility Explorer](https://docs.datadoghq.com/continuous_integration/explorer.md?tab=pipelineexecutions) to find all events with a specific parameter.
    {% /collapsible-section %} | yes              | yes             | yes       | yes      |

## Use CI pipelines data{% #use-ci-pipelines-data %}

Explore details about your pipeline executions in the [CI Visibility Explorer](https://docs.datadoghq.com/continuous_integration/explorer.md). When creating a [dashboard](https://app.datadoghq.com/dashboard/lists) or a [notebook](https://app.datadoghq.com/notebook/list), you can use CI pipeline data in your search query, which updates the visualization widget options. For more information, see the [Dashboards](https://docs.datadoghq.com/dashboards.md) and [Notebooks documentation](https://docs.datadoghq.com/notebooks.md).

## Alert on pipeline data{% #alert-on-pipeline-data %}

You can export your search query to a [CI Pipeline monitor](https://docs.datadoghq.com/monitors/types/ci.md) on the [Executions page](https://app.datadoghq.com/ci/pipeline-executions) or the [Test Runs page](https://app.datadoghq.com/ci/test-runs) by clicking the Export button.

## Further reading{% #further-reading %}

Additional helpful documentation, links, and articles:

- [Learn about billing considerations for CI Visibility](https://docs.datadoghq.com/account_management/billing/ci_visibility.md)
- [Explore test data to find and fix problem tests](https://docs.datadoghq.com/continuous_integration/tests.md)
- [Creating CI Pipeline Monitors](https://docs.datadoghq.com/monitors/types/ci.md)
- [Troubleshooting CI Visibility](https://docs.datadoghq.com/cicd/troubleshooting/pipelines.md)
- [Monitor your CircleCI environment with Datadog](https://www.datadoghq.com/blog/circleci-monitoring-datadog/)
- [Configure pipeline alerts with Datadog CI monitors](https://www.datadoghq.com/blog/configure-pipeline-alerts-with-ci-monitors/)
- [Best practices for monitoring static web applications](https://www.datadoghq.com/blog/static-web-application-monitoring-best-practices/)
- [Best practices for CI/CD monitoring](https://www.datadoghq.com/blog/best-practices-for-ci-cd-monitoring/)
- [Best practices for monitoring software testing in CI/CD](https://www.datadoghq.com/blog/best-practices-for-monitoring-software-testing/)
- [Monitor your CI/CD modernizations with Datadog CI Pipeline Visibility](https://www.datadoghq.com/blog/modernize-your-ci-cd-environment/)
- [How we use Datadog for detection as code](https://www.datadoghq.com/blog/datadog-detection-as-code/)
- [Patterns for safe and efficient cache purging in CI/CD pipelines](https://www.datadoghq.com/blog/cache-purge-ci-cd/)
- [Troubleshoot faster with the GitLab Source Code integration in Datadog](https://www.datadoghq.com/blog/gitlab-source-code-integration)
- [Success Metrics for Platform Engineering Teams](https://www.datadoghq.com/blog/platform-engineering-metrics/)
- [Check out the latest Software Delivery releases! (App login required)](https://app.datadoghq.com/release-notes?category=Software%20Delivery)
