Tracing requests across services without the guesswork
Start at the slow request
A checkout request takes 1.8 seconds. The gateway log reports success and the database dashboard looks normal. Reconstruct that single request before averaging it into a dashboard.
Keep the context
Propagate trace context from the gateway to the orders service. Include it in queue metadata so a consumer can associate later work with the originating request. Record operation names and durations without customer payloads.
Read the critical path
Two parallel calls lasting 300 milliseconds each can add roughly 300 milliseconds to elapsed time. Three sequential retries can cost far more. Inspect the waterfall, change the slow dependency or retry policy, then compare traces under similar load.