WAN tickets: one per incident, notice UniFi updates, maintenance button
Lint / JS (eslint) (push) Successful in 42s
Lint / Python (flake8) (push) Successful in 1m35s
Lint / Notify on failure (push) Skipped
Lint / Deploy (push) Skipped
Security / Python Security (bandit) (push) Successful in 1m3s
Test / Python Tests (pytest) (push) Successful in 1m5s
Lint / Python (flake8) (pull_request) Successful in 58s
Lint / JS (eslint) (pull_request) Successful in 8s
Lint / Notify on failure (pull_request) Skipped
Lint / Deploy (pull_request) Skipped
Security / Python Security (bandit) (pull_request) Successful in 1m1s
Test / Python Tests (pytest) (pull_request) Successful in 1m10s
Lint / JS (eslint) (push) Successful in 42s
Lint / Python (flake8) (push) Successful in 1m35s
Lint / Notify on failure (push) Skipped
Lint / Deploy (push) Skipped
Security / Python Security (bandit) (push) Successful in 1m3s
Test / Python Tests (pytest) (push) Successful in 1m5s
Lint / Python (flake8) (pull_request) Successful in 58s
Lint / JS (eslint) (pull_request) Successful in 8s
Lint / Notify on failure (pull_request) Skipped
Lint / Deploy (pull_request) Skipped
Security / Python Security (bandit) (pull_request) Successful in 1m1s
Test / Python Tests (pytest) (pull_request) Successful in 1m10s
A UniFi Network update on 2026-11-12 dropped the UDM's WAN, Smart Power power-cycled the modem, and Gandalf opened two tickets for the one event. - Modem and WAN reports from one check cycle open a single ticket, led by the most urgent, with the rest listed under "Also seen in this incident". A report while the modem has an open alert, or one that ended under 30 minutes ago, becomes a comment on that ticket instead. - UniFi update log entries (NETWORK_UPDATED, FIRMWARE_UPDATED_V2 and the like) add a note to modem/WAN tickets from 20 minutes before the update to 15 after, and hold new modem/WAN tickets for 15 minutes. - A Maintenance button for admins starts a global suppression for 30 min to 4 hours, with a banner on every page and End now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
6b03fe7b44
commit
379e3be365
11 files changed
+541
-28
No files matched your search
@@ -309,6 +309,12 @@ can view it; only the `admin` group can edit, and every change is logged with wh
|
||||
- Suppression history (last 50)
|
||||
- Available targets reference grid (all known hosts + interfaces)
|
||||
|
||||
**Maintenance**: admins get a **Maintenance** button in the header. It starts a global suppression for
|
||||
30 min, 1, 2 or 4 hours with a reason (by default "Maintenance"). While it runs, every page shows a banner
|
||||
saying when tickets resume, with **End now** for admins. Gandalf keeps checking and recording alerts, and
|
||||
anything still failing when maintenance ends gets a ticket as usual. Use it before a UniFi update, a switch
|
||||
swap or recabling.
|
||||
|
||||
---
|
||||
|
||||
## Alert Logic
|
||||
@@ -386,7 +392,23 @@ Outages can be over between polls: two real ones lasted about two minutes agains
|
||||
So WAN outages and modem restarts also come from the UniFi system log, and a drop in the modem's uptime
|
||||
records a restart even if nothing logged it. A single short outage only appears in the panel's history.
|
||||
|
||||
To silence modem alerts during maintenance, create a `host` suppression with the modem's `name`.
|
||||
**One ticket per incident.** The modem and WAN reports from one check cycle open a single ticket, led by
|
||||
the most urgent (a P2 "WAN modem unreachable" leads, and an RPDU power-cycle seen in the same cycle is listed
|
||||
under "Also seen in this incident"). A report that comes while the modem has an open alert, or one that
|
||||
ended under 30 minutes ago, becomes a comment on that alert's ticket instead of a new ticket. If the
|
||||
comment can't be posted, the report gets its own ticket as before.
|
||||
|
||||
**UniFi updates.** UniFi logs `NETWORK_UPDATED` (Network app) and `FIRMWARE_UPDATED_V2` (device firmware)
|
||||
once an update has finished. Updating the Network app can drop the UDM's WAN, and Smart Power may then
|
||||
power-cycle a modem that was fine. When Gandalf reads one of these entries it:
|
||||
|
||||
- comments on modem and WAN tickets first seen from 20 minutes before the update to 15 minutes after,
|
||||
naming the update (for example "UniFi Network 11.0.97 to 11.0.99") as the likely cause;
|
||||
- opens no new modem or WAN tickets for 15 minutes after the update. A problem still there after that gets
|
||||
its ticket as usual; a power-cycle report during the hold only goes into the event history.
|
||||
|
||||
To silence modem alerts during maintenance, create a `host` suppression with the modem's `name`, or use
|
||||
**Maintenance** (below) to pause every ticket.
|
||||
|
||||
### Baseline Tracking
|
||||
|
||||
|
||||
Reference in new issue
Block a user