Web calls orders, which checks every token with an internal auth service over mutual TLS. At 8 seconds web v311 deploys. At 10 seconds sign-ins start failing, and alerts fire for web and orders.
From 20 to 60 seconds, get at least 99% of requests succeeding again.
ready00:00 / 01:00Success · 10 s–p99 · 10 s–
Goal · measured 00:20–01:00
0 changes · par 1
Requests succeeding ≥ 99.0%not measured yet
Service map
Sign-in chain · pausedSelect a component to inspect
SYSTEM BOUNDARYmTLSUsers400 req/sCLIENTWebv310 · 4 instancesSERVICEOrders6 podsSERVICEAuth (internal)cert notAfter 10:00SERVICE
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
Sign-in chain · pausedSelect a component to inspect
SYSTEM BOUNDARYmTLSUsers400 req/sCLIENTWebv310 · 4 instancesSERVICEOrders6 podsSERVICEAuth (internal)cert notAfter 10:00SERVICE
SYSTEM BOUNDARYmTLSUsers400 req/sCLIENTWebv310 · 4 instancesSERVICEOrders6 podsSERVICEAuth (internal)cert notAfter 10:00SERVICE
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.