Devices send events to an ingest API, which queues them in memory for 4 consumers that write 200 events a second each to a database that can take 1,000 a second. At 10 seconds devices reconnect after an outage and send 1,200 events a second for the rest of the run.
From 10 to 60 seconds, lose no events and keep database load at or under 90%.
ready00:00 / 01:00Success · 10 s–p99 · 10 s–
Goal · measured 00:10–01:00
0 changes · par 1
Events lost ≤ 1 eventsnot measured yet
Peak database load (%) ≤ 90%not measured yet
Service map
Event ingestion · pausedSelect a component to inspect
SYSTEM BOUNDARY800/sDevices500/sCLIENTIngest API0 queuedSERVICEConsumers4 × 200/sSERVICEDatabase800/s of 1000DATA 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
Event ingestion · pausedSelect a component to inspect
SYSTEM BOUNDARY800/sDevices500/sCLIENTIngest API0 queuedSERVICEConsumers4 × 200/sSERVICEDatabase800/s of 1000DATA STORE
SYSTEM BOUNDARY800/sDevices500/sCLIENTIngest API0 queuedSERVICEConsumers4 × 200/sSERVICEDatabase800/s of 1000DATA 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–
Queued events
10,000
Press Start
00:0001:00
Queued–
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.