Practical introduction to OpenTelemetry tracing
summary
Shows how OpenTelemetry actually replaces vendor lockin by letting apps export traces to an OpenTelemetry collector and then to Jaeger or Zipkin, with a demo of auto-instrumentation vs manual instrumentation across Python, JVM, Go, NodeJS and Rust, including Kubernetes metadata collection and use of vcluster for isolation. Demonstrates context propagation through queues by propagating trace context via MQ/headers, reveals what required code changes, what metadata appears, what failed (recommendation demo flaked) and what number of services end up traced.
AI-written summary · about
chapters (14)
- 0:00OpenTelemetry tracing intro
- 1:07Observability needs tracing
- 2:57W3C Trace Context explained
- 4:49OpenTelemetry tracing implementation
- 7:22Auto vs manual instrumentation
- 9:50Demo setup multi-tech
- 13:23Deploying e-commerce stack
- 15:44Python auto-instrumentation demo
- 17:30Adding Kubernetes metadata
- 19:21Enriching traces with annotations
- 22:14Full control over spans
- 23:51Propagating context async
- 27:49Summary and resources
- 28:34Q&A trace sync and Go
related talks
45mPractical introduction to OpenTelemetry tracing
30mPractical introduction to OpenTelemetry Tracing
43mPractical Introduction to OpenTelemetry Tracing
38mPractical introduction to OpenTelemetry tracing
51mPractical introduction to OpenTelemetry tracing
38mPractical introduction to OpenTelemetry tracing
41mPractical introduction to OpenTelemetry tracing
47mA Practical Introduction to Open Telemetry