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
+23
-4
@@ -2,14 +2,14 @@
|
||||
|
||||
Every notification in Homelab Manager is sent through the same pipe
|
||||
(`server/src/services/notify.ts`) to whichever channels are enabled under
|
||||
**Settings → Notifications**: Gotify, ntfy, SMTP (email), and a generic
|
||||
JSON webhook. All four fire for every notification below — there's no
|
||||
**Settings → Notifications**: Gotify, ntfy, SMTP (email), a generic
|
||||
JSON webhook, and push to phones and browsers. All five fire for every notification below — there's no
|
||||
per-event channel routing, only a per-event on/off toggle and, for the
|
||||
daily ones, one shared time/timezone.
|
||||
|
||||
The settings page has three tabs, with one Save button for all of them (it
|
||||
shows "Unsaved changes" until you save, and the browser asks before the page
|
||||
is closed with changes unsaved): **Channels** (the four channels, each a row
|
||||
is closed with changes unsaved): **Channels** (the five channels, each a row
|
||||
you open to fill in and send a test), **What to send** (the event toggles
|
||||
grouped by topic, each group's thresholds beside its switches) and **When**
|
||||
(the time zone, the daily reminder time, quiet hours and the weekly digest).
|
||||
@@ -34,6 +34,25 @@ it:
|
||||
Where a trigger has a configurable threshold, that's noted in its row
|
||||
below; several are fixed and can't be changed from the UI.
|
||||
|
||||
## Push to a phone or browser
|
||||
|
||||
The fifth channel, **Phone and browser**, sends the same messages as the others to browsers that have asked for them — a phone with
|
||||
this page added to its home screen, a desktop browser — with no app, account or extra service. An administrator switches it on under
|
||||
Settings → Notifications → Channels (the optional *contact* is given to the browsers' push services, as the standard asks), and then
|
||||
each person opens the same row and presses **Notify this browser**; the browser asks permission and the row lists their browsers,
|
||||
with a button to send a test and one to remove each.
|
||||
|
||||
- **It needs https.** Browsers only allow push for pages served over https (or from `localhost`), so a copy opened over plain http
|
||||
on a LAN address shows why it can't be used instead of the button.
|
||||
- **How it travels.** The message is encrypted for each browser (RFC 8291) and signed with a key pair this server makes the first time
|
||||
it is needed (RFC 8292, "VAPID"), then handed to the browser's own push service — Google's, Mozilla's or Apple's — which delivers
|
||||
it. The push service sees that a message is being sent and its size, not what it says. The address of each browser's push
|
||||
service is checked before use: https only, and never an address on a private network.
|
||||
- **Quiet hours** hold push messages like every other channel, and each event's on/off toggle applies. A tap on a notification opens
|
||||
the Alerts page.
|
||||
- **A browser that has gone** (the site's permission was removed, the app uninstalled) is dropped automatically when its push
|
||||
service says so. If the server's key pair is ever lost (the credentials key changed), everyone has to press the button again.
|
||||
|
||||
## Daily reminders
|
||||
|
||||
These six checks share one schedule: **Settings → Notifications → Daily
|
||||
@@ -90,7 +109,7 @@ schedule.
|
||||
| DNS record added | *DNS record added* | A DNS record is created against any DNS provider through this app (manually, or via any automated action that writes one). |
|
||||
| DNS record updated | *DNS record updated* | An existing DNS record is edited. |
|
||||
| DNS record deleted | *DNS record deleted* | A DNS record is deleted. |
|
||||
| Integration/DNS provider down | *Integration/DNS provider failing repeatedly* | Any integration or DNS provider adapter's calls fail a configurable number of times **in a row**. Tracked per adapter *type* (e.g. "proxmox"), not per individual integration row — with two Proxmox integrations, a streak of failures on either one counts toward the same total. Only fires once per failure streak (not on every failure past the threshold), and is skipped entirely if that type is currently in a maintenance window. | Settings → Notifications → **Alert after** (default 3 consecutive failures) |
|
||||
| Integration/DNS provider down | *Integration/DNS provider failing repeatedly* | Any integration or DNS provider adapter's calls fail a configurable number of times **in a row**. Tracked per adapter *type* (e.g. "proxmox"), not per individual integration row — with two Proxmox integrations, a streak of failures on either one counts toward the same total. Only fires once per failure streak (not on every failure past the threshold), and is skipped entirely if that type is currently in a maintenance window, **or if it is explained by something it needs that is down** (see *Dependencies* in the README): a service that starts failing while the server it runs on is offline is not announced, and if it is still failing once that server is back, the next failed call alerts. | Settings → Notifications → **Alert after** (default 3 consecutive failures) |
|
||||
| Integration/DNS provider recovered | *(same toggle)* | The next call for that source succeeds, after a "down" alert was already sent for the current streak. |
|
||||
|
||||
## Digest
|
||||
|
||||
Reference in new issue
Block a user