Distributed Tracing in Java? OpenTelemetry for the Rescue!
summary
Shows how OpenTelemetry instruments Java services end to end: use the Java agent for zero‑code captures of HTTP, DB and messaging calls, fall back to manual spans for custom logic, send data through the collector via OTLP over gRPC with sampling to avoid storage overload, and analyze traces in a backend like Jaeger (timeline/gantt view exposes critical paths — e.g. a slow SQL query or staircase Redis calls — so fixes target the true bottleneck).
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 2:09Why distributed tracing matters
- 10:01How distributed tracing works
- 17:20OpenTelemetry overview
- 25:06Automatic vs manual instrumentation
- 27:56Automatic instrumentation in Java
- 31:49Manual instrumentation in Java
- 42:23OpenTelemetry flexibility and summary
- 44:09Q&A session
related talks
30mInstrument Your Java Applications with OpenTelemetry!
37mMake your Java application observable with no code changes using OpenTelemetry
47mI'm Tracing You!
38mPractical introduction to OpenTelemetry tracing
47mUsing metric and traces to diagnose our cloud-native applications
43mPractical Introduction to OpenTelemetry Tracing
49mOpenTelemetry for Java Developers
32mDistributed Tracing in Action: Our Journey with OpenTelemetry