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:
1 parent
27a191b54c
commit
3e6404371b
7 files changed
+217
-53
No files matched your search
@@ -327,8 +327,9 @@ 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, 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
|
||||
(daily, weekly, one-off, cron or switched on by hand), finds the servers,
|
||||
integrations and DNS providers its monitors are the address of, and makes a
|
||||
window here for each, for the slot 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
|
||||
|
||||
Reference in new issue
Block a user