Coding with the lights ON - OpenTelemetry from code to prod
summary
OpenTelemetry instrumentation flips observability from absent to actionable: about 10 lines of code adds traces and metrics collected by an OpenTelemetry collector and routed to Jaeger, Prometheus, Grafana; traces reveal concrete failures like an N+1 query and a measured 1.5s slowdown in production. A developer IDE plugin surfaces those traces next to source, enabling automated checks and regressions and feeding a continuous feedback loop linked from continuous feedback.org.
AI-written summary · about
chapters (5)
- 0:00Start
- 8:15The DevOps Loop
- 16:13The Sample Application
- 37:17The story of Bill, the Prequel
- 44:34Getting Started with CF
related talks
55mCoding with the lights ON - OpenTelemetry from code to prod
41mModern Application Debugging: An Introduction To OpenTelemetry
31mOpenTelemetry and Continuous Feedback – Things you need to Know at Runtime
33mThe Observant Developer - OpenTelemetry from code to prod
38mPractical introduction to OpenTelemetry tracing
23mModern Application Debugging: An Intro to OpenTelemetry
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
49mAdding OpenTelemetry to Production Apps Lessons Learned