Open Telemetry
summary
OpenTelemetry unifies OpenTracing and OpenCensus into an API-plus-SDK that lets libraries emit traces, metrics and logs; Beam gets official support alongside existing options like Spandex (DataDog-only) and OpenCensus. It models work as spans with parent/child context and uses head sampling and tail sampling to cut costs. Concrete tools: telemetry.execute for sync start/stop/failure hooks, collectors that stitch traces, and visual outputs (single-request flame graphs that reveal N+1 queries, stack traces and network latency). Watch for incomplete traces and clock skew.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:04Observability problem
- 6:17Distributed tracing basics
- 10:56Built-in tracing limitations
- 11:17Observability superpowers
- 13:49Distributed tracing culture shift
- 14:10Common pitfalls
- 15:16Open Tracing vs Open Census
- 16:40OpenTelemetry merger
- 17:42OpenTelemetry in Erlang/Elixir
- 18:03Telemetry for metrics
related talks
20mObservability and Open Telemetry
47mWhat Is This OpenTelemetry Thing?
43mWhat is this OpenTelemetry thing?
46mThe State of OpenTelemetry
22mOpenTelemetry – An Observability Framework for Cloud-Native Software
48mOpenTelemetry: Backwards Compatibility with OpenTracing and OpenCensus
20mKeynote: (Open)Telemetry Makes Observability Simple
34mOpenTelemetry: Overview & Backwards Compatibility of OpenTracing + OpenCensus
