OpenTelemetry Is Not a Silver Bullet
summary
Claim: OpenTelemetry is a foundation not a finished product; deployments hit real failures like collector crashes under preload, version drift causing weeks of triage, and collectors starving CPU/RAM on burstable instances. Concrete outcomes include storage filling unnoticed, missing end‑user dashboards, and tracing/ingest pipelines lagging as volume grows. Recommendations: target critical systems first, invest in training and owning tooling, add robust alerting and visualization layers, and treat observability as continuous engineering rather than one‑off setup.
AI-written summary · about
chapters (10)
- 0:00Introduction and Speaker Introduction
- 0:11The Importance of Open Telemetry
- 0:58Vision and Goals of Open Telemetry
- 3:53Challenges in Documentation and Development
- 7:33Scaling and Infrastructure Issues
- 11:54Gaps Between Promise and Practice
- 14:58Case Studies and Implementation Pitfalls
- 19:06Lessons Learned and Recommendations
- 21:56Realistic Expectations and Practical Recommendations
- 26:08Conclusion and Final Thoughts
related talks
05mOpenTelemetry in production for a year plus: the good the bad the ugly
19mOpenTelemetry's Path to Observability's Future
35mOpenTelemetry for Busy People
38mThe State of OpenTelemetry
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
15mOpenTelemetry: The Vision, the Reality and How To Get Started
36mObservability For You and Me with OpenTelemetry
37mObservability For You And Me With Opentelemetry