Behind the Proposals...
summary
OpenTelemetry uses OTEPs to capture the why, design direction, trade‑offs and migration plan and formally needs four approvers though contentious proposals often gather 12–20 approvals; the events OTEP reached about 20 approvers. Design work pairs spec PRs, SDK implementations and SIG meetings, plus blog posts and GitHub discussions for end‑user feedback. Examples: deprecating span events in favor of logs/events while keeping OTLP intake compatibility, HTTP semantic convention migrations with opt‑in/dual‑pump transition paths, and explicit deprecation timelines.
AI-written summary · about
chapters (8)
- 0:00OpenTelemetry design proposals
- 3:55What is an OTEP
- 7:49Who approves proposals
- 12:24Resolving OTEP disagreements
- 16:40Engaging end users
- 18:27Breaking changes in projects
- 23:28Deprecation strategies
- 28:03Design process advice
related talks
42mOTel Me How To Get My Open Source Community Taken Seriously: Lessons...
18mOpenTelemetry and Observability: What, Why, and Why Now?
34mOpenTelemetry: The Vision, Reality, and How to Get Started
33mOpenTelemetry Project Update
47mWhat’s New in OpenTelemetry
15mOpenTelemetry: The Vision, the Reality and How To Get Started
32mOpenTelemetry Semantic Conventions and How to Avoid Broken Observability
04mOpen Telemetry Project Updates