The path
One order, from the alert to the timeout
order_8421 is a real order that failed. Every surface below is filtered to it, so nothing has to be matched up by timestamp between two tools.
- alert T+0:00 · orderorder_8421
The alert fires on the checkout route only
Error rate on POST /checkout crosses its threshold while the rest of the site holds. That scoping is the first fact: this is not the sale traffic, it is the payment path.
- trace T+0:25 · orderorder_8421
The trace ends at Stripe
Open one failed order and the waterfall is unambiguous. Three retries sit at the bottom, red, each timing out at exactly 1.75 s — the client's own deadline, not the provider's.
- logs T+2:10 · orderorder_8421
The logs say the pool was empty
The lines written during those spans carry the same trace id. Retry budget exhausted, then connection pool at capacity — the timeout was a symptom of waiting for a connection, not of Stripe being slow.
