Match Uptime Kuma monitors to integrations and DNS providers as well as servers

A monitor whose address is the host of an integration's or DNS provider's own
address now gets a maintenance window there, alongside the existing match
against servers. Matching stays exact (no inference through DNS), and monitors
that match nothing are listed with their address in the sync result.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-10-12 00:13:04 +02:00
1 parent 27a191b54c
commit 3e6404371b
7 files changed
+217 -53

No files matched your search

+11 -3
View File
@@ -86,9 +86,17 @@ the dashboard views themselves load fine.
but this. The login is sent as Uptime Kuma's own `login` event over `ws://` or `wss://` to the same address
as the integration, so use an `https://` address if it crosses anything but a trusted network.
- For each window Uptime Kuma reports (its running time slot and the next one), the app finds the
monitors it covers, matches their targets to servers the same way the Uptime Kuma page does, and makes a
maintenance window on each matched server. A window that hasn't started shows as *Scheduled* and silences
nothing yet.
monitors it covers and matches each monitor's address to something here: a **server** (the monitor's host
is one of its IP addresses, its hostname or its short name — the same matching the Uptime Kuma page
uses), an **integration** or a **DNS provider** (the monitor's host is the host of the address it was
added with, as the same name or the same IP). It then makes a maintenance window on each match. A window
that hasn't started shows as *Scheduled* and silences nothing yet.
- Matching is exact. Nothing is worked out through DNS, so a website that only resolves to the same address
as a reverse proxy does not put the proxy into maintenance. A monitor that matches nothing is listed in the
result as `name (address)` so you can see why. The usual fix is to make the address agree: a Proxmox
integration added by IP will not match a monitor that watches its hostname, and vice versa.
- A window on an integration silences that integration's alerts, including "integration down" for that
type of service — see the Maintenance page for the full list.
- Tick *Keep maintenance windows in step with Uptime Kuma's schedule* to run this automatically every
15 minutes. Without it, the *Sync schedule* button does the same once.
- Windows are capped at 31 days, and only slots starting within two weeks are mirrored. A window Uptime