Why Distributed Tracing Matters
Follow a request across many services.
The microservices visibility gap
When one user request flows through many services, a failure or slowdown is hard to locate. Distributed tracing stitches the whole journey into a single, viewable timeline.
Trace and span
Two core concepts:
- A trace represents one end-to-end request
- A span represents one unit of work within it (e.g. a single service call)
All lessons in this course
- Why Distributed Tracing Matters
- Micrometer Tracing
- Exporting Traces to Zipkin
- Correlating Logs and Traces