The Hater's Guide To OpenTelemetry
summary
OpenTelemetry frames itself as a standards‑style schema for metrics, traces, logs and profiles, promising vendor‑agnostic telemetry and OTLP traces from Docker Compose; it already ships a Collector that supports collector multi‑pipelines and teeing to multiple backends. Concrete numbers: HTTP semantic conventions stabilize after roughly four years with 17 core attributes and many contributors, issue age drops from ~18–20 weeks to ~1 week, while a lingering problem—schema transform merging of competing attribute values—remains unresolved since 2021. Elastic profiler is donated and integration work is ongoing.
AI-written summary · about
chapters (7)
- 0:00The history of standards
- 4:38The case against OpenTelemetry
- 8:47Obsolescence and vendor threat
- 13:11The slow pace of standardization
- 18:40Handling complexity and usability
- 26:21Governance and user expectations
- 29:32Conclusion and Q&A
related talks
46mThe State of OpenTelemetry
15mOpenTelemetry: The Vision, the Reality and How To Get Started
30mOpenTelemetry: The Road Ahead + Meet the Co...
43mWhat is this OpenTelemetry thing?
09mOpenTelemetry or OpenTeleMessy?
32mOpenTelemetry Semantic Conventions and How to Avoid Broken Observability
18mOpenTelemetry and Observability: What, Why, and Why Now?
30mOpenTelemetry 101