Away mode, and critical alerts through quiet hours
For a one-person homelab, "on call" is when you can be reached. Settings -> Notifications -> When -> Away holds notifications while you are away (a banner on every page says so) and sends one digest when it ends, at its time or when you say you are back. Critical alerts can still come through. Quiet hours get the same "still send critical alerts" option. Escalation steps marked to send in quiet hours are sent while away too. What is held for one reason is not released while the other still holds it. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
3b31b16796
commit
16b24f5436
21 files changed
+737
-50
No files matched your search
+21
-2
@@ -23,7 +23,11 @@ it:
|
||||
instead of sent immediately, then delivered as a single digest at the
|
||||
window's end time. This matters most for the real-time alerts below —
|
||||
the daily reminders already fire once at a time you pick, usually
|
||||
outside the window anyway.
|
||||
outside the window anyway. *Still send critical alerts* (off by default)
|
||||
lets a **critical** one — a server down, a disk full, mains power lost —
|
||||
through at once, so only the warnings wait for the morning.
|
||||
- **Away** (Settings → Notifications → When, and a banner on every page while
|
||||
it is on): "I'm away until Sunday". See [Away](#away).
|
||||
- **Maintenance windows** (the Maintenance page): opening one for a
|
||||
server, integration, or DNS provider silences the alerts that target
|
||||
it specifically (offline/disk-full for a server; storage, backup, and
|
||||
@@ -59,7 +63,7 @@ and only some kinds of alert — a phone for the critical things, a desktop for
|
||||
**Escalation.** When an alert has been raised for a while and **nobody has acknowledged it**, it is told again, in up to three steps — for example *after
|
||||
30 minutes: push; after 2 hours: email the neighbour who holds the key*. Each step names its time, the least severity it applies to, the channels to use
|
||||
(chosen freely — routing rules don't apply to escalations), an optional extra email address to tell as well (sent through the email channel's server) and
|
||||
whether to send during quiet hours (otherwise it waits for them to end like any other). Every step is sent once per alert; an acknowledgement stops the
|
||||
whether to send during quiet hours and while away (otherwise it waits for them to end like any other). Every step is sent once per alert; an acknowledgement stops the
|
||||
rest, and the alert starts over if it goes away and comes back. Problems under maintenance, held back because something they depend on is down, or only
|
||||
informational never escalate. It is looked at every five minutes, so a step can arrive a few minutes after its time. Every escalation is written in the audit
|
||||
log (category *alert*, action *escalate*).
|
||||
@@ -210,6 +214,21 @@ Each link is a **signed token** for the alerts in that message only, valid for *
|
||||
notification time zone). Opening it shows a page that says what each button would do and changes nothing; only a button press does anything. What was done is in the audit log, *from a notification link*, with the address
|
||||
it came from. **Anyone who can read the notification can use it** for those 24 hours. A message held for quiet hours is sent without buttons; recovery messages never have them.
|
||||
|
||||
## Away
|
||||
|
||||
For a stretch rather than every night. **Settings → Notifications → When → Away** takes the time you will be back (with shortcuts: tomorrow evening, Sunday evening, a week, two weeks), optionally a start later than now (to plan a
|
||||
holiday ahead), a note to yourself and whether to **still send critical alerts**. While it lasts:
|
||||
|
||||
- notifications are **held** — the same queue quiet hours use — and a banner on every page says that someone is away and how many are held;
|
||||
- **critical** alerts still go out at once, if that box is ticked (it is by default); with it off, nothing does;
|
||||
- at the time you gave, or when you press **I'm back**, what was held is sent as **one digest** — "Homelab Manager — Notifications from while you were away" — to the channels each was meant for, and the away stretch is cleared. It is looked at every
|
||||
minute, and also right after the app restarts, so it ends within a minute of its time;
|
||||
- an **escalation** step that says *send even during quiet hours* is sent while away too — that is what it is for, for example an email to the neighbour who holds the key;
|
||||
- if quiet hours are on at that moment, the digest waits for them to end; if you come back in the middle of an away stretch's quiet hours nothing is lost.
|
||||
|
||||
What it does **not** do: it does not stop the alerts themselves — they are on the Alerts page, in the event webhooks and in `/metrics` as ever, so a Home Assistant or Grafana setup still sees everything; it only holds the *messages to you*. Away mode is an
|
||||
administrator's to set (it decides who is told what), everyone sees the banner, and starting, changing and ending it are in the audit log and the Change log. Times typed there are the clock of the screen they are typed on.
|
||||
|
||||
## Flapping alerts
|
||||
|
||||
A health alert that is raised, clears and is raised again is announced the first times as usual. When the same alert has been raised **three times within an hour** (Settings → Notifications → *Servers and disks*; 0 = off) it is *flapping*:
|
||||
|
||||
Reference in new issue
Block a user