Mirror Uptime Kuma's maintenance schedule as maintenance windows
Uptime Kuma shares its maintenance windows only over its dashboard Socket.IO connection, which takes a login. With a login username and password on the integration, "Sync schedule" on the Maintenance page (and a 15-minute background pass when switched on) reads each window's running and next time slot and the monitors it covers, and makes a maintenance window on every server those monitors match. Windows that haven't started are listed as Scheduled and silence nothing until they begin; ones ended or cancelled by hand stay ended, and ones removed in Kuma are removed here. maintenance_windows gets a source column (migration 0017) and active windows now require their start to have passed. Adds socket.io-client, and tests against a stand-in Uptime Kuma speaking the same protocol. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
5e416b0273
commit
9e483f2163
21 files changed
+3259
-31
No files matched your search
@@ -325,12 +325,18 @@ health, Proxmox backup alerts, Proxmox Backup Server verification alerts, and
|
||||
Every window has a fixed end (5 minutes to 7 days) and expires on its own, and
|
||||
a problem that began during a window and is still present when it ends alerts
|
||||
then — a forgotten window can't hide an outage. A banner shows what's currently
|
||||
silenced to every signed-in user. If you also run Uptime Kuma, "Import from
|
||||
Uptime Kuma" on the Maintenance page reads which of its monitors are
|
||||
currently in maintenance and starts (or extends) a window here for whichever
|
||||
server each one's target matches, for a duration you choose — Uptime Kuma's
|
||||
metrics only say what's in maintenance right now, not for how long, so this
|
||||
doesn't try to mirror its schedule, only its current state.
|
||||
silenced to every signed-in user. If you also run Uptime Kuma, the Maintenance
|
||||
page can take its maintenance windows over: "Sync schedule" reads each window
|
||||
(daily, weekly, one-off, cron or switched on by hand), finds the servers its
|
||||
monitors belong to, and makes a window here for the one running now and the next
|
||||
one — listed under Scheduled until it starts, then silencing alerts like any
|
||||
other. Tick "Keep maintenance windows in step" on the Uptime Kuma integration
|
||||
and this happens by itself every 15 minutes, so a daily window needs no
|
||||
clicking at all; a window changed, switched off or deleted in Uptime Kuma is
|
||||
followed, and one you end or cancel here by hand stays ended. Reading the
|
||||
schedule needs a login on the Uptime Kuma integration (see INTEGRATIONS.md).
|
||||
"Import now" is the older, simpler route: it only looks at what is in
|
||||
maintenance this moment and starts a window for a duration you choose.
|
||||
|
||||
**Ports** — each server's detail page has a Ports card for finding free ports
|
||||
and remembering what each one is for. "Scan…" runs a TCP scan of a port range
|
||||
|
||||
Reference in new issue
Block a user