Native Instrumentation for Open Source Software with OpenTelemetry
Talkat KubeCon + CloudNativeCon North America 2021 · on Friday, 2021-10-15· at 15:25· Room 402 AB + Online·
summary
OpenTelemetry splits a tiny stable API vs SDK separation so libraries ship only interface code while applications load one SDK at runtime, avoiding dependency conflicts; tracing APIs are stable now, metrics targeted by year end and logs early 2022. Azure SDKs report instrumentation across Java, .NET, Python and JS; recommended practice is instrumenting public API spans, propagating context implicitly (and offering explicit hooks), follow semantic conventions, start opt‑in to limit telemetry cost and benchmark for overhead.
AI-written summary · about
chapters (10)
- 0:00Introductions
- 0:35Instrumentation challenges
- 3:17OpenTelemetry architecture
- 5:12Stability and roadmap
- 7:42Azure SDK implementation
- 10:51Semantic conventions
- 11:58Context propagation
- 15:21Mitigating instrumentation risk
- 17:37Performance and costs
- 19:37Recap and call to action
related talks
18mNo Dependencies. No Plugins. Just Native OpenTelemetry
30mInstrument Your Java Applications with OpenTelemetry!
01h 01mPractical OpenTelemetry in .NET 8
43mWhat is this OpenTelemetry thing?
32mOpenTelemetry feat. logs, metrics and traces
20mObservability and Open Telemetry
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
30mOpenTelemetry 101