A slow citizen checkout spans the API gateway, payments service, and notify service, and ops needs the path of one request end to end. Which observability approach should they use?
Select an answer to reveal the explanation.
Short Explanation
A checkout that crawls is like a package with three warehouses and no tracking number—you need the stamps on every hop. Distributed tracing stitches those hops into one request path across API, payments, and notify. Metrics alone won’t tell you which stop burned the seconds.
Full Explanation
Distributed tracing follows a single request across services by propagating context and recording spans. For multi-hop citizen workflows, traces reveal latency and errors at each stage rather than only host-level metrics. Cloud+ observability scenarios expect operators to configure tracing when cross-service request paths must be diagnosed.