How We Streamlined Our SDLC with Observability - from GitHUB via Jenkins, Harbor, Argo to K8S
Talkat Observability Day North America 2024 · on Tuesday, 2024-11-12· at 15:55· Salt Palace | Level 2 | 255 B·
summary
Company runs ~2,000 developers across three clouds and wires Backstage, GitHub, Jenkins, Harbor, Argo, Crossplane and Prometheus into OpenTelemetry and Dynatrace to auto-trace every delivery flow, produce a deployment dashboard that shows which component versions live on each stage, and surface bottlenecks and wait times per pipeline step. A single source-of-truth of SDLC events and quality gates (using Captain-style pre/post checks and Dynatrace SLO baselining) catches regressions; internal metrics show only ~40% developer productive time and 36% attrition risk, driving focused optimizations.
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 2:08Company and SDLC overview
- 4:36Developer platform architecture
- 6:19Individual tool monitoring
- 9:59Pipeline observability
- 11:09Optimizing tool performance
- 13:19Streamlining artifact flows
- 17:10Key lessons learned
- 18:26Community and collaboration
- 21:15Q&A and closing
related talks
26mHow We Gained Observability Into Our CI/CD Pipeline
46mThe Software Factory
35mGaining Observability Into Your CI/CD Pipeline
29mAutomating Continuous Compliance for Scalable SaaS Delivery
30mOur Journey in Integrating GitOps Tools Into Delivery Pipelines
34mGitOps for the people
47mGitOps - Using Git as your source of truth for build, deploy and observability
55mBuild your APIs and DevOps Hybrid Skills