End-to-end CI/CD observability with open source
summary
Claims that CI/CD pipelines become debuggable by shipping traces, metrics and logs via OpenTelemetry collector and consuming them in Prometheus Loki Jaeger or Grafana Signals; shows Jenkins plugin and deployment patterns (sidecar, daemonset, central collector), correlates spanIDs across pipeline stages, and uses DORA metrics with targets like lead time <1 hour and failure rate 0-15%. Demonstrates reliability patterns—idempotency, checkpointing, automated retries—and a DNS flake example that delayed a demo.
AI-written summary · about
chapters (11)
- 0:00CI/CD observability matters
- 3:45S sur approach to pipelines
- 5:11Observability in CI/CD
- 6:37OpenTelemetry for CI/CD
- 9:29Deploying collectors
- 11:35Instrumenting pipelines
- 14:24Visualizing CI/CD metrics
- 17:14Reliable CI/CD pipelines
- 21:11Optimizing CI/CD performance
- 24:51Data-driven deployments
- 25:34Key takeaways
related talks
35mGaining Observability Into Your CI/CD Pipeline
30mMaking your CI/CD Pipelines Speaking in Tongues with Open...
06mProject Lightning Talk: Quick Intro to CI/CD Observability with OpenTelemetry
45mFrom Noise To Signal: Building Smart Observability Pipelines With OpenTelemetry
25mBeyond Production: End-to-End CI/CD Observability With OpenTelemetry
44mHow We Gained Observability Into Our CI CD Pipeline
26mHow We Gained Observability Into Our CI/CD Pipeline
29mFrom Flaky Builds to Self-Healing Deployments: An OTel-Driven CI/CD...