AWS CodePipeline Integration
Monitor pipeline execution status, stage duration, and deployment frequency metrics for your AWS CodePipeline CI/CD workflows. Get automated DORA metrics and AI pipeline regression detection to improve engineering velocity.
How It Works
Enable CodePipeline EventBridge Events
AWS CodePipeline automatically emits pipeline execution, stage execution, and action execution state change events to EventBridge. No additional configuration is needed to enable these events.
Deploy TigerOps Pipeline Event Forwarder
Run the TigerOps CloudFormation stack to create the EventBridge rule and Lambda forwarder that streams CodePipeline execution events to TigerOps in real time.
Deploy CloudWatch Metric Streams
Additionally stream the AWS/CodePipeline namespace metrics to TigerOps for aggregate pipeline success/failure counts and stage-level execution counts across all pipelines.
Configure DORA Metric Dashboards
TigerOps automatically computes deployment frequency, change failure rate, and mean time to recovery from CodePipeline events and displays DORA metrics on pre-built dashboards.
What You Get Out of the Box
Pipeline Execution Status
Real-time pipeline execution state (InProgress, Succeeded, Failed, Superseded) per pipeline with historical success/failure rate trending across all CodePipeline pipelines.
Stage Duration Analysis
Execution duration per stage including Source, Build, Test, and Deploy. Identify the slowest stages in your pipeline and track duration regressions after configuration changes.
Deployment Frequency Metrics
Daily, weekly, and monthly deployment counts per pipeline and per environment. Track deployment frequency as a DORA metric and set goals for high-performing engineering teams.
Change Failure Rate Tracking
Track failed pipeline executions as a percentage of total executions. TigerOps correlates pipeline failures with the specific action (CodeBuild, CodeDeploy, Lambda) that caused failure.
Mean Time to Recovery
Measure the time from pipeline failure detection to the next successful execution as the MTTR metric. Track MTTR trends over time to measure pipeline reliability improvements.
AI Pipeline Regression Detection
TigerOps detects when pipeline success rates drop below historical baselines and automatically correlates with recent source code commits, configuration changes, or infrastructure events.
CloudFormation Stack for CodePipeline Event Forwarder
Deploy the TigerOps EventBridge forwarder to capture pipeline execution events and compute DORA metrics automatically.
# TigerOps CloudFormation — CodePipeline Event Forwarder
# aws cloudformation deploy \
# --template-file tigerops-codepipeline.yaml \
# --stack-name tigerops-codepipeline \
# --capabilities CAPABILITY_IAM
Parameters:
TigerOpsApiKey:
Type: String
NoEcho: true
ProductionPipelinePattern:
Type: String
Default: ".*-production$"
Description: Regex to identify production pipelines for DORA metrics
Resources:
CodePipelineEventRule:
Type: AWS::Events::Rule
Properties:
EventPattern:
source:
- aws.codepipeline
detail-type:
- CodePipeline Pipeline Execution State Change
- CodePipeline Stage Execution State Change
- CodePipeline Action Execution State Change
Targets:
- Arn: !GetAtt PipelineForwarder.Arn
Id: TigerOpsPipelineForwarder
# Also stream CloudWatch pipeline metrics
TigerOpsCodePipelineStream:
Type: AWS::CloudWatch::MetricStream
Properties:
Name: tigerops-codepipeline-stream
FirehoseArn: !GetAtt TigerOpsDeliveryStream.Arn
RoleArn: !GetAtt MetricStreamRole.Arn
OutputFormat: opentelemetry0.7
IncludeFilters:
- Namespace: AWS/CodePipeline
TigerOpsDeliveryStream:
Type: AWS::KinesisFirehose::DeliveryStream
Properties:
HttpEndpointDestinationConfiguration:
EndpointConfiguration:
Url: https://ingest.atatus.net/api/v1/cloudwatch
AccessKey: !Ref TigerOpsApiKey
RequestConfiguration:
CommonAttributes:
- AttributeName: service
AttributeValue: codepipelineCommon Questions
How does TigerOps compute DORA metrics from CodePipeline?
TigerOps uses CodePipeline execution events from EventBridge to compute all four DORA metrics: Deployment Frequency (successful pipeline executions to production), Change Failure Rate (failed executions / total executions), Lead Time for Changes (source commit to successful deploy), and Mean Time to Recovery (failure to recovery duration).
Can TigerOps distinguish between staging and production pipeline executions?
Yes. TigerOps uses pipeline name patterns or tags to classify executions by environment. You can configure regex patterns or exact pipeline name lists to separate staging, QA, and production deployment metrics in TigerOps dashboards.
Does TigerOps support CodePipeline V2 pipelines?
Yes. Both CodePipeline V1 and V2 pipeline types emit the same EventBridge event schema. TigerOps supports pipeline variables, trigger filters, and execution conditions available in V2 pipelines through the same event forwarder.
Can TigerOps track CodeDeploy blue/green deployment outcomes within pipelines?
Yes. TigerOps ingests CodeDeploy deployment events alongside CodePipeline action execution events. Blue/green deployment success and rollback events are captured and linked to the parent pipeline execution for full deployment traceability.
How does TigerOps alert on pipeline failures?
TigerOps creates incidents immediately when CodePipeline emits a FAILED execution event. Alerts include the pipeline name, failed stage and action, failure message, and a direct link to the CodePipeline console execution detail page for fast investigation.
Stop Measuring Deployment Frequency in Spreadsheets
Automated DORA metrics, pipeline failure alerts, and AI regression detection. Deploy in 5 minutes.