Fold alerts under their host, recurring maintenance, run playbooks from alerts, and an Updates page

- Servers can say what they run on (or it is worked out from the Proxmox node); when the host is
  down the guests' offline alerts fold under it: held back, not counted, not notified, still recorded.
- Recurring maintenance schedules made into ordinary windows a week ahead (maintenance_schedules).
- Run a Semaphore template limited to a server from its page or an alert, and watch the run.
- Agents report pending updates (apt, dnf, zypper, Windows Update); an Updates page lists them.
- Migrations 0024 and 0025.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-10-17 01:35:15 +02:00
1 parent 44e393f172
commit 171511c6db
45 files changed
+6772 -44

No files matched your search

+39
View File
@@ -400,6 +400,45 @@ the problems themselves, and each integration's status, refreshing every 30
seconds with the screen kept awake where the browser allows. Esc returns to the
app.
**Alerts folded under their host.** A server can say which server it runs on (a
virtual machine on its Proxmox host): on its page, "Runs on" — and left alone it
is worked out when the server is linked to a Proxmox guest and exactly one
server is named after that guest's node. When the host stops reporting, the
guests' own "server offline" alerts are folded under the host's ("also takes down
anna, elsa") instead of being one alert each: they are held back like a silenced
alert, not counted, left out of notifications and osTicket tickets, and labelled
"caused by pve1" on the Alerts page. They are still recorded as down (for the
uptime ribbons and "Since you last looked"), and if the host comes back while a
guest is still down, that guest alerts then as new — an outage is never swallowed.
Links that loop back on themselves cover nothing, and setting one that would is
refused.
**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
time. Each time becomes an ordinary maintenance window a week ahead (shown on the
timeline with vertical stripes, and in Scheduled), so any single one can be
cancelled and stays cancelled. Turning a schedule off or removing it takes back
the windows that haven't begun.
**Running a playbook** from an alert or a server: a server's page has a "Run a
playbook" card, and alerts about a server have a "Run…" button, which pick a
Semaphore template and run it limited to that server (ansible's `--limit`, which
you can edit to match the host name in your inventory — or untick it to run on
everything, which asks more sternly). Semaphore is told who started it, the run
shows waiting → running → success or failed, and the audit log records what ran
and where. Operators and admins only.
**Updates** (Operations → Updates) shows what each agent says is waiting to be
installed — how many, how many are security fixes, whether a restart is due, and
how long updates have been waiting — plus the Docker containers with a newer image.
The Linux agent asks apt, dnf or zypper (only what they already know; nothing is
installed or refreshed) and the Windows agent asks Windows Update (at most every six
hours, cached under `%ProgramData%\HomelabManager`). A server whose agent hasn't
said — an older agent, or another package manager — shows "not reported", never "up
to date"; run its install command again to update its agent. It only looks: to apply
updates, run a playbook.
**Customising the dashboard.** Customise (top of the dashboard) lets you move each
card earlier or later among its neighbours and hide the ones you don't use —
hidden cards stay listed, dimmed, while you arrange so they can be brought back,