Observability and instrumentation via OpenTelemetry
summary
OpenTelemetry basics map logs, metrics, traces and baggage to concrete actions: a single HTTP add request generates multiple spans (route span plus a child add-sum span with event metadata), automatic instrumentation via openTelemetry instrument produces full SDK spans out of the box, and manual calls add events and parent IDs visible in the console exporter. Demo uses Python, the console exporter for visibility, and recommends efficient storage like graphon Tempo after showing that even one request yields a surprising volume of trace data.
AI-written summary · about
chapters (11)
- 0:00Observability with OpenTelemetry
- 1:06Four data signals in OpenTelemetry
- 4:20Demo setup and scenarios
- 5:29Version one: no instrumentation
- 6:30Version two: manual instrumentation
- 9:05Version three: logs + manual
- 11:01Version four: automatic instrumentation
- 14:00Mix manual and automatic
- 16:35Tracing challenges and fixes
- 17:41Tools for traces storage
- 19:29Q&A on tracing
related talks
27mEnd-to-end visibility in the cloud w/OpenTelemetry
22mOpen Telemetry for API Monitoring
36mObservability For You and Me with OpenTelemetry
27mDistributed Tracing with OpenTelemetry
40mPractical introduction to OpenTelemetry tracing
46mThe State of OpenTelemetry
34mOpenTelemetry for Dummies: Instrumenting Go Apps
32mOpenTelemetry feat. logs, metrics and traces