OpenTelemetry 101
summary
OpenTelemetry provides a unified API/SDK, an extensible Collector with receivers/processors/exporters, and OTLP (over gRPC and HTTP with protobuf or JSON). Key specifics: tracing is GA with many 1.0+ libs, metrics are RC and integrate with Prometheus, logs remain experimental (protocol more advanced than SDK). Auto-instrumentation agents, eBPF-based instrumentation for Go, an operator for Kubernetes and an official end-to-end demo exist. Start by enumerating languages, signals, sources, and target backends.
AI-written summary · about
chapters (10)
- 0:00Introduction to OpenTelemetry
- 1:44What is observability?
- 4:57OpenTelemetry project overview
- 8:53Core components explained
- 15:11Project maturity status
- 17:20Traces and metrics progress
- 19:27Logging and future signals
- 21:33Beyond three pillars
- 24:21eBPF and operational tools
- 26:30How to get started
related talks
34mOpenTelemetry: The Vision, Reality, and How to Get Started
32mOpenTelemetry feat. logs, metrics and traces
18mOpenTelemetry and Observability: What, Why, and Why Now?
46mThe State of OpenTelemetry
15mOpenTelemetry: The Vision, the Reality and How To Get Started
01h 08mOpenTelemetry: The First Release, What’s Next, and How to Get Involved
50mGuide to Observability with OpenTelemetry
20mObservability and Open Telemetry