Practical Introduction to OpenTelemetry Tracing
summary
A small demo system is built: Apache API 6 gateway, a Spring Boot Kotlin catalog, a Python Flask pricing service and a stock service, all wired with Docker Compose and a Jaeger all‑in‑one collector via Docker Compose. Auto‑instrumentation via the JVM agent captures HTTP and framework spans while added manual @WithSpan annotations record method-level attributes (product ID). Sampling is set to 100% for the demo, coroutines produce parallel price/stock calls visible as separate spans, and traces successfully show end‑to‑end flow.
AI-written summary · about
chapters (15)
- 0:00OpenTelemetry tracing intro
- 1:05Why tracing matters
- 3:13OpenTelemetry as standard
- 4:35How collector works
- 6:20Auto-instrumentation quick
- 7:22Demo setup overview
- 9:10Configuring APISIX
- 10:33JVM auto-instrumentation
- 12:17Spring Boot walkthrough
- 15:33Docker Compose Jaeger
- 17:16Starting architecture
- 18:23Analyzing traces Jaeger
- 21:34Manual instrumentation
- 23:58Verifying traces Jaeger
- 24:43Summary next steps
related talks
41mPractical introduction to OpenTelemetry tracing
30mPractical introduction to OpenTelemetry Tracing
38mPractical introduction to OpenTelemetry tracing
45mPractical introduction to OpenTelemetry tracing
43mPractical Introduction to OpenTelemetry Tracing
51mPractical introduction to OpenTelemetry tracing
47mA Practical Introduction to Open Telemetry
40mPractical introduction to OpenTelemetry tracing
