OpenTelemetry or OpenTeleMessy?
summary
Claim: OpenTelemetry Collector centralizes export but forces large, brittle YAML configs and lots of auth/connectivity fiddling. Evidence: language SDK inconsistencies, tracing libraries being the most mature while logs are new, and profiling is being added. Numbers: adoption is large (second‑largest CNCF project) and semantic conventions are stabilizing. What was built and works: auto-instrumentation on EKS can yield quick traces; what breaks is cross‑language parity and debugging mismatched exporters. Near term: tracing is most mature and collector v1 approaching guide rollout choices.
AI-written summary · about
chapters (7)
- 0:00Introduction and Agenda
- 0:44What is Open Telemetry?
- 1:32Core Problems Solved by Open Telemetry
- 3:26Challenges and New Problems
- 5:35When Does Open Telemetry Make Sense?
- 6:47Strategies for Implementing Open Telemetry
- 8:25Future Outlook and Conclusion
related talks
19mOpenTelemetry's Path to Observability's Future
30mOpenTelemetry 101
20mObservability and Open Telemetry
39mOpenTelemetry: Meet the Community, Build the Roadmap
47mWhat Is This OpenTelemetry Thing?
32mOpenTelemetry feat. logs, metrics and traces
01h 08mOpenTelemetry: The First Release, What’s Next, and How to Get Involved
15mOpenTelemetry: The Vision, the Reality and How To Get Started