Distributed tracing groups one request under a trace ID and records its operations as spans. Their start and end times plus parent links reveal slow steps and failures across services.
The demo shows a gateway request containing API and database spans on a shared timeline. Sampling may leave some requests unrecorded, and sensitive user data should stay out of span attributes.
When to use
Use it to locate latency or errors in a request that crosses multiple services.