OpenTelemetry: Backwards Compatibility with OpenTracing and OpenCensus
summary
OpenTelemetry merges OpenTracing and OpenCensus into a single API and implementation set, reusing the OpenCensus agent/collector and providing a shim so existing OpenTracing instrumentation maps to the new model; Java shim available proves the approach. Key concrete changes include a concrete span context with trace/span IDs, W3C tracecontext propagation, attributes/events replacing tags/logs, linked spans, and exporters for Jaeger/Zipkin. Project targets parity by September, moves cores to read-only by November, and offers two years support while migrating agents and gRPC formats.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:51Cloud-native telemetry
- 6:06Both widely adopted
- 8:30Instrumentation APIs
- 9:49Canonical implementations
- 11:22Data infrastructure (coming)
- 17:01Open Telemetry Goals: 2019
- 18:11Open Telemetry Goals: Long-term
- 19:11Open Telemetry community membership
- 19:56Open Telemetry governance
- 20:59Scope Diff: Open Telemetry vs Open Tracing
- 21:52Tracing: the Mental Model Network Call
- 22:45Changes: SpanContext
- 29:44Changes: Tracer
- 31:34The Open Tracing + Open Telemetry Shim
- 33:10Open Tracing bridges: other languages
- 35:44Philosophical alignment
- 36:51Removing artificial barriers
- 41:36Open Telemetry vs OpenCensus
- 43:43Transition plan for OpenCensus library
- 45:58Transition plan for OpenCensus Service
related talks
34mOpenTelemetry: Overview & Backwards Compatibility of OpenTracing + OpenCensus
34mOpenTelemetry: Overview & Backwards Compatibility of OpenTracing + OpenCensus
21mOpen Telemetry
38mOpenTracing Project Intro
46mThe State of OpenTelemetry
01h 08mOpenTelemetry: The First Release, What’s Next, and How to Get Involved
20mKeynote: (Open)Telemetry Makes Observability Simple
20mObservability and Open Telemetry