Manage Alert Rules
Create, edit, scope, and review alert rules so users are notified when machine conditions cross important thresholds.
Goal
Keep alert logic useful, targeted, and easy to review.
Before You Begin
Administrators who maintain proactive notifications.
- Roles: Admin
- Entry points:
/alert-rules,/alert-rules/:machineId,/machines/:machineId/alert-rules
Begin on the Alert Rules page.
Preconditions
- The user has admin access.
Steps
Open the alert rules page globally or from a
Open the alert rules page globally or from a specific machine.
Review existing rules by machine group or global
Review existing rules by machine group or global scope.
Start a new rule or edit an existing one
Start a new rule or edit an existing one.
Choose the trigger condition, threshold, scope,
Choose the trigger condition, threshold, scope, recipients, and active time windows.
Save the rule and confirm it appears in the rule
Save the rule and confirm it appears in the rule list.
Expand a rule when you need to inspect past alerts
Expand a rule when you need to inspect past alerts or resolve existing alerts.
Decision Points
- Whether the rule should apply to all machines or one machine.
- Whether an alert needs to be resolved, reopened, or deleted from history.
Expected Result
The platform can notify the right people when the selected conditions happen.
Common Problems and Edge Cases
- Too many rules can generate noisy notifications.
- A rule that is too broad may affect more machines than intended.
Related Pages
Use these page links to move laterally through the platform and keep context as you go.
Last updated 2 weeks ago
Built with Documentation.AI