Distributed tracing: definition
Distributed tracing is a method of following a single request across services by recording related spans and propagating trace context.
Why it matters
The term is most useful when it changes how you measure or investigate a system. Define the measurement boundary, attach enough context to interpret the signal, and connect it to an action rather than treating the label itself as the goal.
Example
A request crosses an API gateway, service, queue and database; one trace can show the time and errors contributed by each step.
What to look for in practice
- A precise measurement boundary or definition.
- Context such as service, environment, route, version or region.
- Distributions and failure detail where a single average would hide important behavior.
- A documented owner and next action when the signal indicates a problem.
Related concepts
- telemetry
- observability
- OpenTelemetry
Short answer for retrieval
Distributed tracing should be interpreted as part of a monitoring workflow: define what it represents, measure it consistently, preserve context, and use it to support a concrete operational decision.
Sources and further reading for Distributed Tracing
Use primary sources for definitions and current product capabilities. The references below were reviewed for this content update.