Observability and Open Telemetry
summary
OpenTelemetry under CNCF provides APIs, SDKs and an OTLP protocol for exporting metrics traces and logs, with automatic and manual instrumentation, a collector (receiver → processor → exporter) and sampling options: head‑based, tail‑based and probabilistic. Real adopters report concrete gains: retired 12 internal and external systems and saved ~15 minutes per mobile merge by centralizing telemetry. Zipkin, Prometheus and vendor endpoints (for example New Relic) are supported, and traces are the most broadly stable signal across languages.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:06What is observability
- 4:44OpenTelemetry overview
- 8:01Core concepts
- 10:50OpenTelemetry Collector
- 12:40Sampling techniques
- 14:07Exporting data
- 15:09Industry adopters
- 16:34Future of OpenTelemetry
- 17:16Enablers and integrations
- 18:19Adoption considerations
- 19:03Summary
related talks
19mOpenTelemetry's Path to Observability's Future
47mWhat Is This OpenTelemetry Thing?
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
18mOpenTelemetry and Observability: What, Why, and Why Now?
36mObservability For You and Me with OpenTelemetry
43mWhat is this OpenTelemetry thing?
34mOpenTelemetry: The Vision, Reality, and How to Get Started
30mOpenTelemetry 101