Checkout calls a payment provider. At 10 seconds the provider starts timing out on 5% of calls. The code catches the exception, logs it at debug, and returns 200 with an empty receipt. Only warn and above reach the log platform.
From 10 to 60 seconds, make every failure visible in the logs while keeping log volume at or under 20 GB a day.
ready00:00 / 01:00Success · 10 s–p99 · 10 s–
Goal · measured 00:10–01:00
0 changes · par 1
Failures visible in logs ≥ 99.0%not measured yet
Log volume (GB/day) ≤ 20 GB/daynot measured yet
Service map
Checkout errors · pausedSelect a component to inspect
Users300 checkouts/sCLIENTCheckout APIcatch → 200 {}SERVICEPayment providerokTHIRD PARTYLogs10 GB/dayDATA STORE
All components healthy.requestretrytrial call (half-open)failed
What changed
Turn on a fault or change a defence while the run plays. Its effect shows here: the 5 seconds before against 5 seconds after it settles.
Service map
Checkout errors · pausedSelect a component to inspect
Users300 checkouts/sCLIENTCheckout APIcatch → 200 {}SERVICEPayment providerokTHIRD PARTYLogs10 GB/dayDATA STORE
Users300 checkouts/sCLIENTCheckout APIcatch → 200 {}SERVICEPayment providerokTHIRD PARTYLogs10 GB/dayDATA STORE
All components healthy.requestretrytrial call (half-open)failed
What changed
Turn on a fault or change a defence while the run plays. Its effect shows here: the 5 seconds before against 5 seconds after it settles.
Dashboard
Requests per second
100/s
Press Start
00:0001:00
Answered–
Failed–
Latency
100 ms
Press Start
00:0001:00
p50–
p95–
p99–
Events and logs
Nothing yet. Faults, timeouts, retries, breaker changes, shedding, cache expiry and your own changes appear here, and as markers on the charts.
Slowest recent request
Press Start to see requests.
This is a simulation. Its numbers come from a model of a typical system, not from measuring real servers. The same link and seed always give the same run. How the Chaos Lab works.