Dependency map, impact preview in maintenance, and a calmer Alerts page

- Map: a Dependencies view showing what would go down with a picked box and what it relies on
- Maintenance: lists what depends on a target and can silence those too (same time, audited); the recurring form and update drawer show the same note
- Alerts: a headline on where things stand, held-back alerts nested under their cause, severity edge on rows; caused-by now carries the explaining alert's id

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-10-18 19:17:09 +02:00
1 parent ec9c2f73f0
commit 9caa414829
19 files changed
+944 -40

No files matched your search

+14 -1
View File
@@ -304,7 +304,10 @@ already failing, so old failures aren't announced. Toggle it under Settings →
Notifications. For Gitea this follows the repo's most recent run on any
workflow or branch, the same as the Gitea page shows.
**Alerts** (Operations → Alerts, visible to every role) lists everything that's
**Alerts** (Operations → Alerts, visible to every role) opens with one line on where things stand — how many problems need attention and, when some are
held back, which problem explains how many ("nasbox accounts for 3") — and marks each row with a coloured edge by severity. Held-back alerts are nested under
the alert that explains them (switch "Group under their cause" off for the flat list; the choice is remembered): the cause says "Show the 3 alerts held back
under this" and opens them. It lists everything that's
wrong right now in one place, instead of waiting for a notification or visiting
each page: servers that stopped reporting, full or nearly full disks and volumes
(critical from 95%), Synology volume/disk problems, failed or uncovered Proxmox
@@ -398,6 +401,10 @@ Uptime Kuma monitors watch it. Hover or tab to a box to light up its
connections; each box links to its page. A monitor Uptime Kuma can't be read for
leaves a note rather than a silent gap.
The Map's second view, **Dependencies**, draws what needs what with the foundations on the left (the servers and services that take part in
a dependency or a "runs on" link, each with its status). Pick a box and what would go down with it turns red and what it relies on blue,
with a sentence underneath — "If it goes down, 4 things go with it: …" — so the answer to "what breaks if I reboot this?" is there before you do it.
**Wall display** (`/wall`, also on the dashboard and the user menu) is a
full-screen status board for a spare monitor or tablet: the overall state in
large type, servers online, alerts, maintenance windows and failing integrations,
@@ -429,6 +436,12 @@ so it is folded only when every enabled instance of that kind is explained. A se
is offline isn't announced; if it is still failing once the server is back, the next failed call alerts. (DNS providers raise no
alerts of their own, so they aren't part of this.)
**Seeing the impact before maintenance.** Choosing a server or integration under Maintenance → Start maintenance lists what depends on it and
will look down while it is — and offers to put those under maintenance too, for the same time, with the reason "Depends on …" (ticked by default;
each is its own window, listed and ended like any other, and audited). The recurring-schedule form shows the same note for what is picked and can add
the dependents to the selection. The "Update this server now" drawer shows what depends on the server and may look down while it restarts; it doesn't
silence them, because their windows would outlast the run — use Maintenance first if you want that.
**Recurring maintenance** (Maintenance → Recurring) repeats a window on the days
and clock time you choose — "Sundays 02:00–04:00 on these servers" — in the time
zone of the browser it was made in, so 02:00 stays 02:00 across summer and winter