Start maintenance on everything, all servers or all integrations at once
The Start maintenance list gets a "Many at once" group: Everything, All servers, All integrations, All DNS providers (enabled ones only). Each target still gets its own window, existing ones are extended, and the action is one audit entry. "Everything" asks for confirmation first, and "End all" on the Active list ends every running window together. The top banner and the wall display summarise long lists instead of printing every name. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
65263a64e3
commit
bff0c2169e
7 files changed
+287
-4
No files matched your search
@@ -338,7 +338,11 @@ this server's IP address, allowed to create tickets), entered on the osTicket in
|
||||
provider while you work on it (server offline / disk, storage and Synology
|
||||
health, Proxmox backup alerts, Proxmox Backup Server verification alerts, and
|
||||
"integration down" for that service type).
|
||||
Every window has a fixed end (5 minutes to 7 days) and expires on its own, and
|
||||
For a power cut or a rack reboot, the "Many at once" choices at the top of the
|
||||
list start a window on every server, every (enabled) integration, every
|
||||
(enabled) DNS provider, or all of them in one go — asking first before
|
||||
"Everything" — and "End all" on the Active list closes them together. Each is
|
||||
still its own window, so any can be ended alone. 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, the Maintenance
|
||||
|
||||
Reference in new issue
Block a user