5.1Why Distributed Tracing?

In a microservices architecture, a single user request may traverse 5, 10, or 20 services. When that request is slow or fails, you need to answer: which service is the bottleneck? Distributed tracing provides the answer by tracking each request's journey across service boundaries, recording timing, status, and metadata at every hop.