Solutions
Follow an order from checkout to a service handoff.
An online marketplace sees orders take longer to move after checkout. Request traces and service signals show which handoff between services is slowing the order down.
The situation
On a busy sales day an online marketplace's customers still see an order confirmation, but the warehouse side reports that orders are arriving later than usual. Checkout succeeds; what happens next is slow.
That split is what makes it hard. The service that customers touch looks fine, and the service that is struggling is two steps further on.
What the team sees first
An alert on the order service shows the time to complete an order creeping up. Service health marks the checkout service as healthy and the fulfillment service as the one with rising latency, which tells the engineer which end of the order's path to open first.
How the investigation goes
A trace that begins at checkout runs through payment confirmation, stock reservation and the fulfillment request. The first two spans are short. The third is long, and inside it a call to a carrier-integration service waits on an external response.
Logs around that call show the carrier service retrying with growing delays. The dependency map shows that the carrier integration is also called by the returns service, which explains a complaint the support team had set aside earlier in the day.
What gets shared
Responders get one record that follows an order from checkout to the slow handoff, including what was checked and ruled out. The logistics team can tell customers truthfully why delivery estimates have moved, and the engineers can add a limit to the retries so one slow carrier cannot hold up every order.
What this shows
An order crosses payments, stock and delivery. Following a single order through all three is how the team finds the handoff that is slowing everything down.
These stories are illustrative examples. They describe invented scenarios in an industry, not a real customer, a real incident or any company's systems.
Start with your own services.
A trial workspace is free for 14 days. Send your telemetry and follow your own requests.