Overview
An alert rule turns monitor and device state changes into notifications. Monitors detect; alert rules decide who is told, how severe it is, and whether it should escalate to a ticket or page the on-call rotation. Without a matching rule, a failing monitor is silent.
Steps
- Open Pulse → Alert rules.
- Click Add rule (the page shows "No alert rules yet" with this action when empty).
- Set the scope — which sites, devices, or monitors the rule applies to.
- Set the severity (e.g. info / warning / critical).
- Choose the notify targets — who receives the alert (email/in-app, and which channel).
- Optionally enable escalation: open a ticket and/or page on-call when the rule fires.
- Toggle Enabled and save. The rule appears in the list with its severity, scope, notify target, and enabled state.
Editing and Disabling Rules
Each rule row has Edit rule and Delete rule actions. To silence a noisy rule without losing it, edit it and toggle Enabled off, or narrow its scope.
Where Alerts Show Up
Fired alerts appear on Pulse → Alerts. From there you can acknowledge and resolve them; rules with escalation also create the ticket / on-call page you configured.
Best Practices
- Scope critical rules tightly (specific devices/monitors) so a critical page means something.
- Pause monitors (not delete rules) during planned maintenance to avoid false alerts.
- Use severity consistently across sites so the Alerts page is triageable at a glance.
Troubleshooting
A monitor is Failing but no alert fired. Confirm a rule's scope actually covers that monitor/device and that the rule is Enabled. A monitor with no matching rule never notifies.
Too many alerts from one rule. Narrow its scope, raise the monitor's failure threshold, or lower the rule severity so it stops paging.