The State of OpenTelemetry
summary
OpenTelemetry unifies headers, a wire protocol and exporters so agents send spans and metrics over OTLP collector (gRPC or JSON/HTTP) to vendor back ends; tracing is tracing mature with 11 language SDKs and Java auto-instrumentation, metrics are stable, and logs draft remains immature. Demo sends curl-generated traces through the collector into Elastic and shows per-request spans, dependency latency, and errors; sampling supports head-based and tail-based sampling (collector-side) to reduce volume. Ongoing work includes continuous profiling (eBPF) and a control plane for agent configuration.
AI-written summary · about
chapters (11)
- 0:00Start
- 7:04Agents
- 9:41Problem
- 11:19API Headers Only
- 11:49W3C Trace Context
- 12:06OpenTelemetry
- 21:16Java Agent Setup
- 21:42Manual Instrumentation
- 22:39OTel for JavaScript
- 36:19Differentation on the
- 36:59Standardization
related talks
30mOpenTelemetry 101
32mOpenTelemetry feat. logs, metrics and traces
38mThe State of OpenTelemetry
34mOpenTelemetry: The Vision, Reality, and How to Get Started
20mObservability and Open Telemetry
43mWhat is this OpenTelemetry thing?
18mOpenTelemetry and Observability: What, Why, and Why Now?
36mObservability For You and Me with OpenTelemetry