Runbooks per alert kind, high-vulnerability threshold, wall display extras
A "What to do" note (text and/or link) can be written once for a whole kind of alert and shows beside every alert of that kind; alerts now carry their kind and source type. New optional setting: warn when a Docker host has N or more high vulnerabilities (off by default). The wall display gains tiles (Hetzner and game servers running, critical vulnerabilities, stuck downloads) and a summary line for each group of integrations, also in share links. Migration 0074; docs and tests included. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
d9083adb5b
commit
3d9a2310bb
35 files changed
+9129
-30
No files matched your search
@@ -131,8 +131,8 @@ All modules from the original plan are built:
|
||||
container (from Dockhand's own cached update check, plus a button
|
||||
to trigger a fresh one), a live running/total widget (with an
|
||||
updates-available count), and the **vulnerabilities** Dockhand's own
|
||||
scans found per host (critical ones listed; a warning is raised for
|
||||
critical ones, and it can be switched off).
|
||||
scans found per host (critical ones listed; a warning is raised for the critical ones — and, if you give a number, for hosts with that many high ones — and
|
||||
it can be switched off).
|
||||
- **Uptime Kuma** — every monitor's status (up/down/pending/maintenance),
|
||||
response time, and 24h/30d uptime, with certificate days remaining where
|
||||
applicable. Each monitor is matched to one of your servers when its
|
||||
@@ -421,7 +421,7 @@ with a sentence underneath — "If it goes down, 4 things go with it: …" — s
|
||||
|
||||
**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,
|
||||
large type, servers online, alerts, maintenance windows and failing integrations — and, for what is connected, how many Hetzner servers and game servers are running, how many critical vulnerabilities and stuck downloads there are, and one line for each group of the menu (Infrastructure, Apps …) saying whether it is well —
|
||||
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.
|
||||
@@ -613,7 +613,7 @@ check the UPS first, then…" — on a server's page (the Runbooks card) or an
|
||||
integration's card. A note can be for anything about the thing, or for one kind of
|
||||
alert (a disk filling up). On the Alerts page an alert about a server or integration
|
||||
shows a Runbook link when a note fits it, and opens it in a side panel with the notes
|
||||
that fit that alert first. Everyone signed in reads them; operators write them. The
|
||||
that fit that alert first. A note can also be written once for a whole **kind** of alert — the *What to do* link beside an alert, "when a Hetzner certificate is about to end: renew it in the console, then…", with an optional page to open — and then shows beside every alert of that kind, whatever it is about. Everyone signed in reads them; operators write them. The
|
||||
text is plain: a blank line is a new paragraph, `- ` a list, ``` around lines a block
|
||||
of commands, backticks inline code; links become clickable, and nothing typed in a
|
||||
note can run as HTML.
|
||||
|
||||
Reference in new issue
Block a user