Close an alert: dealt with or accepted, hidden until it gets worse
Close... on the Alerts page hides an alert with no end, with an optional reason that is also written on its incident. It opens again only if it gets more serious than when it was closed (said once) or the problem has been gone for half an hour; Open again brings it back at once. Built on the snooze table (kind, severity and note columns), so everything that holds back snoozed alerts holds back closed ones. Audit log, change log and /api/v1 alerts carry it. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
4ff0b44943
commit
a94899865e
24 files changed
+7982
-24
No files matched your search
+4
-1
@@ -37,7 +37,7 @@ This page explains what Homelab Manager watches, how often, how a problem become
|
||||
|
||||
```
|
||||
agents ─────────┐
|
||||
integrations ───┤ ┌──► Alerts page ──► acknowledge · snooze · silence
|
||||
integrations ───┤ ┌──► Alerts page ──► acknowledge · snooze · close · silence
|
||||
endpoint checks ┼─► checks ─► conditions ─┼──► notifications ─► Gotify · ntfy · email · webhook · push
|
||||
heartbeats ─────┤ (rules) "a problem" ├──► event webhooks (machines)
|
||||
your own rules ─┘ ├──► incidents (the record) and history
|
||||
@@ -428,6 +428,7 @@ Several things can quiet an alert. They are different, and it matters which you
|
||||
|---|---|---|---|---|
|
||||
| **Acknowledge** ("I'm on it") | No — it says someone has seen it, why, who has it | No: still listed, still counted in `/metrics`; leaves the *needs attention* count | Stops [escalation](#escalation) | When you choose (an hour … 30 days), or when the alert has been gone half an hour |
|
||||
| **Snooze** ("remind me tomorrow 09:00") | No | Yes, held back like maintenance | Raise/clear messages held; **one reminder** at the end if it is still there | At the time you set (up to 90 days), or earlier with *Wake now* |
|
||||
| **Close** ("dealt with, or accepted") | Yes — with who and why, and the reason is written on the incident | Yes, held back like a snooze | Raise/clear messages held; **one message** only if it **gets worse** | Never by time: when it gets more serious than it was, when it has been gone half an hour, or with *Open again* |
|
||||
| **Maintenance window** | Yes — "I'm working on this" (5 minutes to a week) | Yes, marked *silenced* | Held for the server, integration, DNS provider or device | At its end; what is still there is then announced as **new** |
|
||||
| **Folded under a host** | — automatic | Nested under its cause | Not announced on its own | When the cause ends |
|
||||
| **Flapping** | — automatic | No | Raise and clear messages held; one "flapping" message, one "settled" message | After an hour of calm |
|
||||
@@ -525,6 +526,8 @@ For your own rules, raise the limit or lengthen the time.
|
||||
|
||||
**I want to be reminded about something later, not silence it.** Snooze it.
|
||||
|
||||
**I have dealt with it, or I accept it, and I do not want to be reminded.** Close it (*Close…* on the Alerts page, with a reason). It stays closed until it gets worse than it was, or the problem goes away for half an hour and returns.
|
||||
|
||||
**I do not want to be woken for warnings.** Add a routing rule: kind or severity → the channels you want (a rule with no channels tells nobody; the Alerts page still shows it), and set quiet hours.
|
||||
|
||||
**A job on a server has to run every night.** Make a heartbeat for it and call it from the end of the script.
|
||||
|
||||
Reference in new issue
Block a user