Simulator
Your fleet. Your investigation.
Follow the evidence, test a hypothesis, and bring your services back.
When a dependency misbehaves
Two simulated services. One simulated fault: stopped, starved of CPU, or out of disk. Find the boundary of the failure.
- 01Baseline
- 02Start
- 03Investigate
- 04Recover
- 05Verify
- 06Reset
Fleet topology 02
A successful control action is followed by three healthy verification cycles.
gateway-a
Choose a check. Explore in any order.
Safe to try. An action that finds nothing to change says so; the evidence decides whether it helped.
Evidence notebook 0
Open a record to inspect its result. Select evidence to support your diagnosis. Export within 24 hours to preserve detailed observations.
Simulated checks will appear here when the collector runs.
A little direction?
Explore unaided, or choose just the support you need. Help is recorded, never forced.
✧ AI investigatorUPCOMING
The read-only AI assistant is not implemented yet. All current guidance is deterministic. No model requests are sent.
Your working diagnosis
Incident report
After an investigation starts, its latency, failures and your actions appear here. Press play to replay it.
Action timeline
Recovery attempts and verification will appear here.
Investigation history
Your investigations will be kept here.