CI Pipeline Visibility in Datadog
This product is not supported for your selected
Datadog site. (
).
Overview
CI Visibility provides a pipeline-first view into your CI health by displaying important metrics and results from your pipelines. It helps you troubleshoot pipeline failures, address performance bottlenecks, and track CI performance and reliability over time.
Setup
Select your CI provider to set up CI Visibility in Datadog:
For customization options, see the following sections:
Supported features
Pipeline visibility and execution
| AWS CodePipeline | Azure Pipelines | Buildkite | CircleCI | Codefresh | GitHub Actions | GitLab | Jenkins | TeamCity | Other CI Providers |
|---|
Logs collection
Retrieval of pipeline or job logs from the CI provider. Logs are displayed on the Logs tab in the Pipeline Execution view. | | | | | | | | | | |
Infrastructure correlation
Correlation of host-level information for the Datadog Agent, CI pipelines, or job runners to CI pipeline execution data. | | | | | | | | | | |
Running pipelines
Identification of pipelines executions that are running with associated tracing. | | | | | | | | | | |
Partial retries
Identification of partial retries (for example, when only a subset of jobs were retried). | | | | | | | | | | |
Step granularity
Step level spans are available for more granular visibility. | | | | | | | | (Presented as job spans) | | |
Manual steps
Identification of when there is a job with a manual approval phase in the overall pipeline. | | | | | | | | | | |
Automatic analysis
| AWS CodePipeline | Azure Pipelines | Buildkite | CircleCI | Codefresh | GitHub Actions | GitLab | Jenkins | TeamCity | Other CI Providers |
|---|
Job failure analysis
Analysis and categorization of job failures using LLM models based on relevant logs. More info. | | | | | | | | | | |
Critical path
Identification of CI jobs that are on the critical path of the pipeline. More info | | | | | | | | | | |
Duration breakdown
| AWS CodePipeline | Azure Pipelines | Buildkite | CircleCI | Codefresh | GitHub Actions | GitLab | Jenkins | TeamCity | Other CI Providers |
|---|
Execution time
Time for which a pipeline has been actively running jobs. | | | | | | | | | | |
Queue time
Time for which a pipeline or job was in the queue before execution. | | | | | | | | | | |
Approval wait time
Time for which a pipeline or job has been waiting for a manual approval. | | | | | | | | | | |
Customization and extensibility
| AWS CodePipeline | Azure Pipelines | Buildkite | CircleCI | Codefresh | GitHub Actions | GitLab | Jenkins | TeamCity | Other CI Providers |
|---|
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. | | | | | | | | | | |
Static tags
Support for setting static pipeline tags in the CI provider that do not change between executions. | | | | | | | | | | |
Runtime tags
Support for adding user-defined text and numerical tags to pipelines and jobs in CI Visibility. | | | | | | | | | | |
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 to find all events with a specific parameter. | | | | | | | | | | |
Use CI pipelines data
When creating a dashboard or a notebook, you can use CI pipeline data in your search query, which updates the visualization widget options. For more information, see the Dashboards and Notebooks documentation.
Alert on pipeline data
You can export your search query to a CI Pipeline monitor on the Executions page or the Test Runs page by clicking the Export button.
Further reading
Additional helpful documentation, links, and articles: