Engine, Demo

1 · Poll

Fetch every device & monitor across all consoles, every 5 min.

2 · Confirm

Flap protection. Must stay down 2 cycles before filing.

3 · File

One incident, one ticket, with an SOP anyone can act on.

4 · Resolve

Auto-recovers, or a human marks it fixed. Comments track it all.

Live device feed

Engine run log

The Asana ticket it files SOP + live comment thread

No open ticket. Knock the site offline to watch Engine file one, complete with a troubleshooting SOP and an automated comment trail.

Faithful demo of Engine. The real service files this exact ticket body (a triage SOP, the device list, a lifecycle explainer, and a hidden beacon-entity tag for idempotent auto-close) and posts the comments below as the incident moves. Acknowledge it, mark it fixed by hand, or click Bring it back to watch it auto-recover.

Engine titles every ticket by severity: [OUTAGE] when a whole site or its outside-in monitor is down (the scenario above), [DEGRADED] when individual devices drop but the site itself stays reachable. A device that keeps flapping gets a single sticky [CHRONIC] ticket instead of repeat noise, and new tickets are held during scheduled maintenance windows (overnight console auto-updates) so routine reboots never page anyone.