← Mira AI Front #3 · NOC Watch

A NAS goes silent.
Mira opens the ticket before you notice.

Every 5 minutes, Mira reads the radacct table. If a NAS device has had zero accounting activity for 30 minutes, that's an outage. She opens a critical ticket, computes affected subscribers, and closes it automatically when the device starts talking again.

outage timeline · CORE-03 · 14:22 → 15:11
13:48 14:22 14:27 15:11 15:11+ Last acct packet CORE-03 stops 34 min silence Mira polls, threshold breached TKT-2851 auto-created acct resumed Ticket auto-closed
How it's wired

Boring plumbing. Reliable outcomes.

Cron every 5 minutes

*/5 * * * * — hits /api/mira/noc-watch. Reads max(accttime) per NAS-IP-Address from radacct.

30-min threshold

Configurable per device class. Backhaul routers: 15 min. APs: 30 min. OLTs: 10 min.

Dedup logic

Before creating a ticket, checks for an open ticket with [NOC] tag and matching NAS. No spam. No thrash.

Affected subscribers

Computes count of currently-authenticated subscribers with that NAS-IP in their last session. Shown in the ticket.

Auto-resolve

When accounting resumes, the ticket closes automatically with downtime duration recorded.

Slack + email

Critical tickets notify #noc-alerts on Slack and page the on-call engineer via email. Configurable per severity.

Outages happen. Blindness doesn't have to.

Wake up to a resolved ticket,
not an angry customer.