Storm engine
One outage should produce one page, not forty.
When a rack loses power or a shared volume stalls, every service on top of it fails within seconds. Most tools treat each failure as its own incident, and the person on call wakes up to a phone that will not stop.
The storm engine looks across a rolling 30-minute window for failures that are almost certainly the same event. It groups them by machine first, then by namespace, then by region — the same order a human would reason in.
The result is a single incident with forty pieces of evidence attached, rather than forty incidents with one each. Everything is still there when you need to unpick it later, but you are woken once.
At a glance
- runs
- every 30 seconds
- lookback
- 30 minutes
- clusters by
- machine → namespace → region
- pages sent
- one per outage
All six engines run on every plan with agents.
Install on one machine and the first score lands 20 seconds later.
Deploy an agent→