Challenge 29 · intermediate · Microservices
The missing trace
The same four services: gateway, orders, inventory and pricing. Tracing is on, and to save money every service keeps 10% of its spans, deciding for itself. At 10 seconds orders v119 ships, replacing its HTTP client library. Afterwards, orders' spans show a long gap where its calls to inventory and pricing used to be, and pricing's logs carry trace ids nobody else has.
From 15 to 60 seconds, make at least 99% of stored traces complete (every service's spans in one trace), while keeping no more than 15% of spans.
Goal · measured 00:15–01:00
0 changes · par 2- Stored traces that are complete ≥ 99.0%not measured yet
- Share of spans kept ≤ 15% of spansnot measured yet
Service map
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.
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.