A request goes through a gateway, orders and payments. The gateway already creates an X-Request-Id, but nothing passes it on and nobody logs it. At 10 seconds 2% of orders start failing and support tickets arrive.
From 10 to 60 seconds, make every log line of a failed request findable by its id.
ready00:00 / 01:00Success · 10 s–p99 · 10 s–
Goal · measured 00:10–01:00
0 changes · par 2
A request's log lines findable by id ≥ 99.0%not measured yet
Service map
Request logs · pausedSelect a component to inspect
req_7f3a91c2no idGatewayX-Request-IdSERVICEOrdersdrops idSERVICEPaymentsno id in logsTHIRD PARTYLogs0% of a request's lines findableDATA 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
Request logs · pausedSelect a component to inspect
req_7f3a91c2no idGatewayX-Request-IdSERVICEOrdersdrops idSERVICEPaymentsno id in logsTHIRD PARTYLogs0% of a request's lines findableDATA STORE
req_7f3a91c2no idGatewayX-Request-IdSERVICEOrdersdrops idSERVICEPaymentsno id in logsTHIRD PARTYLogs0% of a request's lines findableDATA 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.