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
- Required access: Admin or Page Access
alert_rules; never Operator. - Entry points:
/alert-rules,/alert-rules/:machineId,/machines/:machineId/alert-rules
Begin on the Alert Rules page.
Preconditions
- Admin or Page Access
alert_rules; never Operator.
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.
Review Channel Costs and Data Prerequisites
Before choosing SMS, review the €0.10 per message per user cost and explicit-consent requirement. One message to three users costs €0.30. With no recipients, alerts are still recorded at no cost. Webhooks can use Basic, Bearer, or custom-header authentication.
Sensor-based rules do not trigger for work centers. Read active-shift limitations shown by the rule. Use Automator for its separate admin-only conditions, timing, escalation, and event workflow.
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.