Set thresholds on any register, and let every user choose how and when they are notified. No noise, no missed faults.
Cooldown per rule, quiet hours per user, and digest options stop a single hysteretic sensor from ruining your evening.
One colleague wants an instant push on a critical fault, another a daily digest by email. One rule set, different preferences per user.
Every alert has a full timeline. Who saw it when, who acknowledged, how long resolution took. Audit ready.
How a value above threshold reaches the right person, and how that person closes the alarm.
Pick a register, an operator (greater than, less than, equal to), and a threshold. Or choose 'offline longer than N minutes'.
Info, warning, or critical. Determines color and routing.
Add people. They decide per severity which channel they want to use.
Acknowledge in one click. Once the value returns to normal, the alarm closes itself.
Six mechanisms that keep you from muting alarms on your phone.
Thresholds on register values and on the absence of communication.
Info never pages, critical always emails. No manual routing.
Between 22:00 and 07:00 only critical alerts, the rest bundled in the morning.
Instant, hourly or daily digest, configurable per channel.
Prevents one twitchy sensor from generating hundreds of notifications.
Triggered, acknowledged, resolved, closed. Every step logged with time and user.
4 alarm states for full traceability
Personal preferences per user
Audit log on every acknowledgment
Move to alerts that deserve attention. Fewer notifications, more relevance.
