Context Propagation in OpenTelemetry: Beyond “Hello World” Examples
summary
OpenTelemetry often propagates HTTP traces automatically using the Traceparent header, but distributed flows break when using Kafka, DocumentDB or Kubernetes jobs unless context is handled explicitly. The demo shows Jager missing downstream spans until code injects and extracts context: put trace IDs into Kafka message headers, stash them in documents, and pass them to jobs via V1 env vars; after those changes the end-to-end trace appears.
AI-written summary · about
chapters (6)
- 0:00Context propagation in OpenTelemetry
- 7:27Distributed tracing basics
- 10:20Context in HTTP and Kafka
- 15:16Injecting context into document DBs
- 16:42Tracing Kubernetes job flows
- 19:12OpenTelemetry implementation key takeaways
related talks
47mI'm Tracing You!
31mDistributed Context Propagation: How you can use it to Improve Observability..
54mA TRACE TO REMEMBER: COMPOSITIONAL TRACING
27mAchieving End-to-end Visibility into Complex Event-sourcing Transactions using Distributed Tracing
45mPractical introduction to OpenTelemetry tracing
29mThe Fundamentals of OpenTelemetry
43mTracing Kafka with OpenTelemetry
49mDistributed Tracing: How the Pros Debug Concurrent and Distributed Systems