Where’s the Auto in Auto-Instrumentation? A Look at Current Automation Strategies with OTel
Talkat Observability Day North America 2024 · on Tuesday, 2024-11-12· at 13:30· Salt Palace | Level 2 | 255 E·
summary
Documentation for auto-instrumentation improves but practical details matter: OpenTelemetry now covers 11 languages and uses specific mechanisms like Node.js extension monkey‑patching, Java/.NET/Python bytecode agents and middleware injection, and the OTel Operator to inject SDKs into Kubernetes. eBPF enables observability for compiled Go but with limited visibility and caveats. Auto instrumentation requires instrumented libraries, cannot capture custom user or organizational context, sometimes adds notable overhead (PHP), and usually succeeds as a low-effort starting point — enable it and add manual spans where traces cross boundaries.
AI-written summary · about
chapters (16)
- 0:00Auto-instrumentation challenges
- 1:04Goals and scope
- 3:09Metadata sources for telemetry
- 4:54OpenTelemetry instrumentation
- 6:21Auto-instrumentation methods
- 8:46Library instrumentation
- 12:00No-code instrumentation
- 13:47Bytecode injection
- 15:32eBPF for binaries
- 15:54Kubernetes operator
- 16:58Auto-instrumentation limits
- 18:23Manual annotations for telemetry
- 20:06Start with auto-instrumentation
- 21:49Implementation advice
- 22:33Q&A: off-the-shelf software
- 23:15Q&A: overhead and replacement
related talks
22mFine-Tuning Auto-Instrumentation
45mSimplifying Instrumentation in complex systems at scale with Open Telemetry
20mStrategies for Auto-Instrumenting Go Applications Without Code Changes
26mWelcome to the OTEL California
39mAuto-Instrumenting Go Libraries for Tracing with eBPF and OpenTelemetry
30mObserving Python applications with OpenTelemetry
06mIgnite | Discovering the Magic Behind OpenTelemetry Instrumentation
23mOpenTelemetry Auto Instrumentation for Effortless Observability