Standardizing CI/CD Observability With OpenTelemetry: Insights From the CI/CD Observability SIG
Talkat KubeCon + CloudNativeCon Europe 2025 · on Wednesday, 2025-04-02· at 12:00· Level 3 | ICC Capital Suite 10-12·
summary
OpenTelemetry CI/CD SIG standardizes a concrete schema of semantic attributes for pipelines, deployments, VCS, tests and artifact attestations, and provides receivers that convert GitHub/GitLab webhooks into traces via the OpenTelemetry collector contrib. Demos show the same P50 duration spike in both Honeycomb and SigNoza and a build/test run degrading from typical ~8 minutes to 1 hour 12 minutes. A new spec for environment variable context propagation just merged, and VCS metrics show average time to approval around 10 weeks versus 6 days to merge after approval.
AI-written summary · about
chapters (7)
- 0:00The need for CI/CD observability
- 2:45Semantic conventions overview
- 7:05Practical pipeline demo
- 10:57Analyzing VCS metrics
- 13:38Context propagation specification
- 17:20Future SIG developments
- 19:56Closing remarks and Q&A
related talks
20mStandardizing CI/CD Observability: Insights From the OpenTelemetry CI/CD SIG
25mBeyond Production: End-to-End CI/CD Observability With OpenTelemetry
11mTracing CI/CD with OpenTelemetry
28mEnd-to-end CI/CD observability with open source
38mThe Hater's Guide To OpenTelemetry
32mOpenTelemetry Semantic Conventions and How to Avoid Broken Observability
35mGaining Observability Into Your CI/CD Pipeline
45mFrom Noise To Signal: Building Smart Observability Pipelines With OpenTelemetry