From Schema to Shipping Data, Making...
summary
OpenTelemetry teams describe concrete stability work: migrating Kubelet stats receiver metric names over 10 releases using per-component feature gates, declaring the Kubernetes attributes processor V1 stable and landing the change in release 147, porting 34 metrics to semantic conventions, and adding a migration mechanism that double-publishes old and new names during rollout. Also planned: stable core collector distros, Prometheus interoperability fixes, OTTL stabilization, and machine-generated telemetry schema translations for backward compatibility.
AI-written summary · about
chapters (11)
- 0:00Introduction to OpenTelemetry
- 1:03What is OpenTelemetry
- 3:50Why schema stability matters
- 7:42Defining stability in OpenTelemetry
- 10:11Stabilizing collector components
- 11:56Kubernetes semantic conventions work
- 16:52Aligning schema and collector efforts
- 17:55Future stability plans
- 19:17Default stable collector experience
- 20:21Telemetry schemas for painless migration
- 21:24Q&A session
