Dependencies beyond servers, web push, inventory auto-fill with QR labels, Windows agent health
- Dependencies: servers and integrations can depend on each other; alerts are folded under the root cause, and a failure explained by something down isn't announced - Web push: hand-written VAPID and RFC 8291 encryption, per-device subscriptions, a fifth notification channel, service worker handlers - Inventory: maker/model/serial from the agents fill blank fields, "Refresh from agent", QR label printing and ?asset= deep links - Windows agent (v4) reports failed services, disk health, Storage Spaces pools and hardware identity; Linux agent (v5) reports hardware identity Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
5cc51c57de
commit
ec9c2f73f0
55 files changed
+12553
-65
No files matched your search
@@ -170,7 +170,7 @@ All modules from the original plan are built:
|
||||
too, which writes the table as it is on screen — times as exact timestamps,
|
||||
action buttons left out.
|
||||
- **Settings** (admin-only) — notification channels (Gotify, ntfy, SMTP,
|
||||
generic webhook) with per-channel test buttons, per-event toggles (DNS
|
||||
generic webhook, and push to phones and browsers) with per-channel test buttons, per-event toggles (DNS
|
||||
record added/updated/deleted, daily secret-expiry reminder and daily
|
||||
Tailscale key-expiry reminder — both sharing one configurable
|
||||
time/timezone), badge-color customization for both DNS
|
||||
@@ -420,6 +420,15 @@ refused. "Nothing — it runs on its own" stops the guess for a server that isn'
|
||||
guest (a physical machine that happens to share a Proxmox node's name), so its
|
||||
alerts always stand alone.
|
||||
|
||||
**Dependencies beyond servers** (Infrastructure → Dependencies). Say that Gitea needs the server it is installed on, or that a server
|
||||
needs Proxmox to answer. When what is needed is down, the alert of what needs it is folded under the first one exactly like a
|
||||
guest under its host — shown, labelled "caused by …", left out of notifications and tickets — and the root cause says what else it
|
||||
takes down. It follows chains and the "runs on" links of servers; something needing two things is explained by whichever is down;
|
||||
a loop explains nothing and one that would be made is refused. An integration is judged per kind of service (as its health is),
|
||||
so it is folded only when every enabled instance of that kind is explained. A service that starts failing while the server it needs
|
||||
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.)
|
||||
|
||||
**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
|
||||
@@ -546,6 +555,13 @@ draw, and — with a price per kWh set at the foot of the page — a rough yearl
|
||||
cost. Everyone signed in can look; operators keep it up to date; the weekly digest
|
||||
mentions a warranty ending within 60 days.
|
||||
|
||||
Entries that are a server also pick up what its agent says the machine is: when you link an entry to a server (or the
|
||||
agent reports later), a blank maker, model or serial number is filled in from the firmware — never over what a person wrote.
|
||||
When the agent says something different, the row offers **Refresh from agent**, which asks before replacing. **Print labels**
|
||||
(on the Inventory page) makes a sheet of stickers — a QR code, the name, what it is, its serial number and where it sits, in
|
||||
three sizes — and scanning a code opens that entry (`/inventory?asset=…`) for whoever is signed in. The codes are drawn in the
|
||||
browser; nothing about them leaves the page.
|
||||
|
||||
**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
|
||||
|
||||
Reference in new issue
Block a user