The invoices API returns a customer's invoices. Most customers have a few dozen. At 10 seconds a new customer goes live with 40,000 invoices, about 5% of all requests.
From 15 to 60 seconds, keep p99 at or under 200 ms and answer at least 99% of requests.
ready00:00 / 01:00Success · 10 s–p99 · 10 s–
Goal · measured 00:15–01:00
0 changes · par 1
p99 latency ≤ 200 msnot measured yet
Requests answered ≥ 99.0%not measured yet
Service map
Invoices API · pausedSelect a component to inspect
SYSTEM BOUNDARY≈50 rowsUsers400 req/sCLIENTInvoices API3 instances · 17% busySERVICEDatabaseno LIMITDATA 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
Invoices API · pausedSelect a component to inspect
SYSTEM BOUNDARY≈50 rowsUsers400 req/sCLIENTInvoices API3 instances · 17% busySERVICEDatabaseno LIMITDATA STORE
SYSTEM BOUNDARY≈50 rowsUsers400 req/sCLIENTInvoices API3 instances · 17% busySERVICEDatabaseno LIMITDATA 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.