OpenTelemetry and Observability: What, Why, and Why Now?
summary
OpenTelemetry provides vendor-agnostic instrumentation and a single collector binary that runs as agent or gateway, using the OTLP wire format (gRPC/HTTP), semantic conventions and a pipeline of receivers, processors and exporters to send metrics traces and logs to multiple backends. It is not a backend itself, includes an eBPF network auto-instrumentation option, and aims to reduce toil by letting teams own their telemetry. Project size: ~52 GitHub events/hour and ~800 unique contributors/month across ~150 organizations.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:13Forward- Looking Statements
- 1:25What is Observability?
- 2:37What can you do with it?
- 5:38Solutions to the Telemetry problem
- 6:36What is OpenTelemetry?
- 8:40OT data pipelines
- 10:28Data Ownership
- 12:03CNCF Support
- 16:33OpenTelemetry Project Resources
related talks
30mOpenTelemetry 101
20mObservability and Open Telemetry
36mObservability For You and Me with OpenTelemetry
34mOpenTelemetry: The Vision, Reality, and How to Get Started
37mObservability For You And Me With Opentelemetry
19mOpenTelemetry's Path to Observability's Future
46mThe State of OpenTelemetry
15mOpenTelemetry: The Vision, the Reality and How To Get Started