- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
AWS CodePipeline is a fully managed continuous delivery service that helps you automate your release pipelines for fast and reliable application and infrastructure updates.
Set up tracing on AWS CodePipeline to collect data about pipeline executions, analyze performance bottlenecks or operational issues, and monitor your deployment workflows.
Pipeline Visibility | Platform | Definition |
---|---|---|
Partial retries | Partial pipelines | View partially retried pipeline executions. |
*Running pipelines | Running pipelines | View pipeline executions that are running. Queued or waiting pipelines show with status “Running” on Datadog. |
**Logs correlation | Logs correlation | Correlate pipeline and job spans to logs and enable job log correlation. |
Approval wait time | Approval wait time | View the amount of time jobs and pipelines wait for manual approvals. |
Custom spans | Custom spans | Configure custom spans for your pipelines. |
*AWS CodePipeline running pipelines don’t have Git information until they have finished.
**AWS CodePipeline logs correlation is only available for AWS CodeBuild actions.
To set up the integration between AWS CodePipeline and Datadog CI Visibility, create two AWS resources:
You can create these resources separately, or at the same time, during the EventBridge Rule creation process. For more information about monitoring pipeline events, see the official AWS guide.
https://webhook-intake./api/v2/webhook
.DD-API-KEY
as the API key name and input your Datadog API Key in the Value field.{
"source": ["aws.codepipeline"],
"detail-type": ["CodePipeline Pipeline Execution State Change", "CodePipeline Action Execution State Change", "CodePipeline Stage Execution State Change"]
}
DD-CI-PROVIDER-AWSCODEPIPELINE
as the key and true
as the value.Once the rule is created, the integration is complete, and you can monitor your pipelines in Datadog.
You can optionally restrict the pipelines that are monitored by Pipeline Visibility.
To do this, add the detail.pipeline
filter in the rule event pattern defined when creating the EventBridge Rule. For example:
{
"source": ["aws.codepipeline"],
"detail-type": ["CodePipeline Pipeline Execution State Change", "CodePipeline Action Execution State Change", "CodePipeline Stage Execution State Change"],
"detail": {
"pipeline": ["first-pipeline", "second-pipeline"]
}
}
The event pattern above sets up the integration only for the first-pipeline
and second-pipeline
pipelines.
If you are using Test Visibility and your pipeline contains one or more AWS CodeBuild actions to execute tests, you can correlate your tests with the related pipeline inside Datadog Pipeline Visibility. For instructions, refer to Add the pipeline execution ID.
The AWS CodePipeline integration supports correlating CodeBuild actions with their respective job and pipeline spans. To enable log collection for your CodeBuild actions, see the AWS log forwarding guide.
source:codebuild
and sourcecategory:aws
tags.The pipeline execution ID is an identifier Datadog needs to uniquely identify a pipeline execution. Perform the following steps to assign a pipeline execution ID to correlate pipelines with tests and custom commands:
DD_PIPELINE_EXECUTION_ID
, and the value #{codepipeline.PipelineExecutionId}
. Leave the type as Plaintext.The steps above allow you to add the pipeline execution ID to your CodeBuild action environment variables. For more information on working with variables, see the official AWS guide.
View your data on the CI Pipeline List and Executions pages after the pipelines finish.
The CI Pipeline List page shows data for only the default branch of each repository.
Additional helpful documentation, links, and articles: