Alarms, Rules-card rules and flows tell people through Hermetry’s notification service. It decides, for each person, which channels a notification may use, and respects each person’s choices, with one exception for critical alarms. The full guide is the Notifications section.
Who decides what
| Decision | Made by | Where |
|---|---|---|
| Who is told about an alarm, from which severity, how often reminded | The alarm rule’s notify block | Alarm notifications in depth |
| Who is told by a rule | The rule’s Tell people action | Notifications from rules and flows |
| Which channels exist in your organisation | Administrators | Channels |
| Which channels a person accepts | Each person, in My Profile > Preferences | Your notification preferences |
| Storm threshold, repeat window, critical bypass | Administrators, in Alarm settings | Alarm notifications in depth |
When an alarm is told
| Alarm change | People are told |
|---|---|
| Opened | Yes, at or above the rule’s minimum severity. |
| Severity rose | Yes. |
| Severity fell | No. |
| Acknowledged | No. |
| Resolved | Yes, if its opening was told. |
| Still open and not acknowledged | A reminder, if the rule repeats. |
| Muted device or backfilled alarm | No. |
The same change of the same alarm is told at most once in a 5-minute window, and above 20 alarm notifications a minute the rest are collected into a digest. Both numbers can be changed.
Other systems
To reach other systems, use webhooks instead: every alarm change is sent, without throttling. See Webhooks.