Checkout requests pass through five microservices, and some take 4 seconds. The team needs to see which service in the chain spends most of that time for an individual slow request. Which observability data answers this directly?
Choose one.
Distributed tracing follows a single request across service boundaries.
A trace is the record of one request from end to end, made of spans: each span is a named, timed operation in one service. Spans nest into a timeline that shows where the milliseconds went. Metrics give aggregates across many requests, logs give per-service local detail, and Kubernetes Events describe object state changes, so none of them shows one request's path through the chain.
- Notice the request crosses several services.
- Notice the need is about one individual request, not an average.
- Recall that traces break a request into timed spans per service.
- Choose traces.
Exam tip: One request across many services, and where its time went, is a job for traces.
Observability in Cloud Native: Metrics, Logs, and Traces — the lesson that teaches this.