Add runbooks, backup coverage, inventory, roles from groups, Prometheus metrics and event webhooks
- Runbooks: notes per server/integration, shown next to matching alerts - Backup coverage page across Proxmox and PBS, with a digest section - Hardware inventory with warranty, power and running cost - Authentik group to role mapping with preview and safeguards - /metrics (bearer token) and signed outgoing event webhooks - Docs: README, DATABASE, NOTIFICATIONS, ROLES and new API.md Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
c36e2092c5
commit
c17e9aa140
55 files changed
+7177
-27
No files matched your search
@@ -440,6 +440,52 @@ to date"; run its install command again to update its agent (how, and how to
|
||||
tell it worked: [AGENT_UPDATE.md](AGENT_UPDATE.md)). It only looks: to apply
|
||||
updates, run a playbook.
|
||||
|
||||
**Runbooks.** Write down what to do when something is wrong — "if elsa is down,
|
||||
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
|
||||
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.
|
||||
|
||||
**Backup coverage** (Infrastructure → Backup coverage) answers "what isn't backed
|
||||
up?" for every Proxmox guest: is a backup job covering it, when was it last backed up
|
||||
(from the newest snapshot on a Proxmox Backup Server, or the last successful Proxmox
|
||||
backup task that names the guest), and did that go well — Recent backup, Stale (older
|
||||
than 1, 2, 3, 7 or 14 days, your choice), Failed, No backup, or Unknown (a job covers it
|
||||
but nothing says when it last ran, typical when backups go somewhere other than a
|
||||
Backup Server — never guessed at). Worst first, searchable, with CSV, and the weekly
|
||||
digest lists what needs a look.
|
||||
|
||||
**Inventory** (Infrastructure → Inventory) keeps the hardware behind it all: name and
|
||||
kind, maker, model, serial, where it sits (and rack unit), when it was bought and for
|
||||
how much, when its warranty ends, its typical power draw, and which server it is.
|
||||
Summary cards show how much is under warranty (and what ends within 90 days), the total
|
||||
draw, and — with a price per kWh set at the foot of the page — a rough yearly running
|
||||
cost. Everyone signed in can look; operators keep it up to date; the weekly digest
|
||||
mentions a warranty ending within 60 days.
|
||||
|
||||
**Roles from groups** (Settings → Sign-in, off until switched on): name the groups
|
||||
that mean administrator and operator, and at each sign-in a person's role follows the
|
||||
groups the identity provider (Authentik) reports; everyone else becomes a viewer, or
|
||||
keeps what they have. "Check" shows what each person would become from the groups they
|
||||
had last time, before you switch it on. Safeguards: a sign-in with no groups at all (a
|
||||
wrong claim name) leaves roles alone, the only administrator is never demoted by a
|
||||
group rule, the first person ever is still the administrator, and while it is on the
|
||||
Users page shows roles instead of letting you set them. The Users page also shows the
|
||||
groups each person had at their last sign-in.
|
||||
|
||||
**Prometheus and webhooks** (Settings → API and webhooks). `/metrics` answers in
|
||||
Prometheus's text format — servers up or not, load, memory, disks, waiting updates,
|
||||
agent versions, alert counts, which integrations work, maintenance, what is about to
|
||||
expire — to a request with a metrics token (a bearer token made on that page, shown
|
||||
once, only its hash kept). Event webhooks send a signed JSON message to a URL when an
|
||||
alert begins or ends or maintenance starts or finishes, for Home Assistant, n8n or a
|
||||
status board. Both are described, with the exact series and message formats, in
|
||||
[API.md](API.md).
|
||||
|
||||
**Weekly digest** (Settings → Notifications, off until switched on) sends one message a
|
||||
week through your notification channels: what is wrong now, what was down and for how
|
||||
long, what happened, disks heading for full, things about to expire, updates waiting
|
||||
|
||||
Reference in new issue
Block a user