Alert rules of your own, storage forecasts for Proxmox and Synology, and snooze
- Monitoring -> Alert rules: CPU, memory, disk use and disk temperature limits with a time, severity and scope (all, one server, a tag); try before saving; findings are ordinary health conditions - Proxmox storages and Synology volumes are written down on each health pass (hourly, 400 days) and forecast like server disks: badge and history chart on the pages, alert, digest line, /metrics gauge - Snooze an alert until a time; held back like maintenance, messages held, announced once again if still there when it ends - Docs updated Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
788b3e073c
commit
24ae8db380
38 files changed
+7847
-8
No files matched your search
@@ -177,6 +177,14 @@ A switch, access point or gateway that a UniFi controller has not seen online fo
|
||||
device holds it back; and what depends on it (or it is connected through, if that is down too) is folded under it and named in its message ("— also takes down …"). The controller is read every five minutes; if it cannot be
|
||||
read for twenty, its devices are held — neither announced nor cleared.
|
||||
|
||||
## Your own alert rules, and snoozing
|
||||
|
||||
An alert rule (Monitoring → Alert rules) that is past its limit is announced like any other health alert (*Health Alert*, with a recovery message), counted as **Monitoring** for routing with the rule's own severity, and held
|
||||
back by maintenance on the server. It is checked on the health pass, every 15 minutes.
|
||||
|
||||
An alert that is **snoozed** (Alerts page → *Snooze…*) is not announced or recovered by the health and automation checks until the snooze ends. When it ends and the alert is still there, one **"Snooze ended"** message
|
||||
(⏰) says so, through the usual routing and quiet hours; if the alert went away, nothing is sent. Event webhooks still receive every raise and recovery.
|
||||
|
||||
## 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*:
|
||||
@@ -246,6 +254,9 @@ on the settings page use the saved settings.
|
||||
|
||||
## What does *not* send a notification
|
||||
|
||||
- **Storage forecasts** (a Proxmox storage or Synology volume that will be full in a few days) are on the Alerts page, in the weekly digest and in /metrics, but are not sent as they happen — like the forecast for a
|
||||
server's disk.
|
||||
|
||||
Worth calling out explicitly, since it's easy to assume everything in
|
||||
the app alerts on something:
|
||||
|
||||
|
||||
Reference in new issue
Block a user