Four pods each run at 90% CPU at peak. At 10 seconds a rolling update to v2 starts with maxUnavailable 25% and maxSurge 0. New pods take 20 seconds to become ready.
From 10 to 150 seconds, answer at least 99% of requests and finish the rollout.
ready00:00 / 02:30Success · 10 s–p99 · 10 s–
Goal · measured 00:10–02:30
0 changes · par 2
Requests answered ≥ 99.0%not measured yet
Rollout complete ≥ 100%not measured yet
Service map
Rolling update · pausedSelect a component to inspect
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.