← Home

A real AlertINT investigation, from first alert to finding

Checkout couldn’t reach payment.
The errors showed up next door.

For 20 minutes checkout couldn’t reach payment, and every order failed there. Seven alerts fired across five services, none of them a payment error: no request got through, so payment had nothing to fail. Two minutes and 12 seconds after the first alert, AlertINT named the broken call.

7 alerts5 services2m 12s to the finding
Checkout failures and quiet payment metricsCheckout errors rise to 100 percent during the connection failure. Payment errors remain near zero. Select a milestone to inspect the finding or recovery.0%100%-10:00−3:300:00+5:00+10:00+16:30+24:21+28:00alert: above 5% for 3 min
AlertINT → Slack · +2:12confidence 0.60

Checkout PlaceOrder failing, likely from PaymentService/Charge UNAVAILABLE

The finding points to the call from checkout to payment, so whoever is on call starts there, not in checkout’s own code.

✓ Right call. It left payment’s own health open; payment was fine.

Reconstructed traces · Recorded milestones

Original capture ↗

Why payment looked quiet

Checkout

Orders fail at the payment call.

PaymentService/Charge UNAVAILABLE

Requests never reach payment.

Payment

No incoming requests. Nothing to fail.

Let AlertINT handle the investigation.

We set it up on your services and keep it running.

Try it on your alerts →