Practical introduction to OpenTelemetry tracing
summary
OpenTelemetry gets the request ID across a polyglot e‑commerce demo (Kotlin/Spring Boot, Rust inventory, Go and Ruby warehouses, Python pricing, Redis cache, Postgres) and exports traces to Jaeger collector, showing a single business trace split into ~20 spans. Entry uses an api6 gateway with sampling on; JVM and Python use auto-instrumentation vs manual instrumentation (annotations and API). Async handoff embeds the W3C traceparent in MQTT metadata and the demo works end-to-end (stop/restart analytics removes and restores the span).
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 5:49What is tracing and why it matters
- 9:05OpenTelemetry overview and benefits
- 11:14Auto vs manual instrumentation
- 13:22Live demo setup and components
- 25:11Auto instrumentation in action
- 29:26Manual instrumentation with code
- 33:16Handling asynchronous tracing
- 38:57Q&A and resources
related talks
51mPractical introduction to OpenTelemetry tracing
30mPractical introduction to OpenTelemetry Tracing
41mPractical introduction to OpenTelemetry tracing
38mPractical introduction to OpenTelemetry tracing
43mPractical Introduction to OpenTelemetry Tracing
45mPractical introduction to OpenTelemetry tracing
28mPractical Introduction to OpenTelemetry Tracing
38mPractical introduction to OpenTelemetry tracing