Alerts turn a monitored reading into an actionable ticket. You define rules — thresholds on telemetry points — and ICP raises an alert and opens a ticket when a rule fires. This is the automated alert dispatching framework at the core of the platform: telemetry in, prioritized field work out, with no one watching a dashboard to make it happen.
Alert rules
Create a rule on an asset's telemetry point:
| Field | Options |
|---|---|
| Comparator | Greater than, ≥, less than, ≤, equal, or not-equal |
| Threshold | The numeric value to compare against |
| Priority | The priority of the ticket the rule opens |
| SLA policy | An optional SLA to attach to that ticket |
- Toggle a rule enabled / disabled to pause a noisy one without deleting it
- Edit the name, comparator, threshold, and priority in place
Alerts (the firing history)
Every time a rule fires, ICP records an alert:
- Status — active or cleared
- The trigger value and the point that breached
- Opened and cleared times, and the rule that fired
- The ticket the alert opened
When a point breaches its threshold, ICP automatically opens the alert and a prioritized, routed ticket. When the reading recovers, the alert clears.
Tip
Doing planned work that will trip alerts? Open a maintenance window to suppress alerting for a site or asset during the window, so you don't generate noise tickets.