Managing Alerts

When a Rule triggers, it creates an Alert. Alerts are persistent records of rule violations that require operator attention. Unlike simple log messages, alerts have a lifecycle. For more about creating rules, see Rules Engine.

Alert Lifecycle

1. New: The rule has triggered. The alert is active and unhandled.
2. Acknowledged: An operator has marked the alert as "seen" and is investigating.
3. Resolved: The condition is no longer active, or the operator has manually closed the issue.

Managing Alerts

Navigate to Rule Management > Alerts to see the live dashboard. For information about managing devices that trigger alerts, see Add Device.

Alert Details

• Clear trigger explanation: The alert detail view now explains why the rule triggered instead of forcing you to inspect the raw record manually.
• Matched value emphasis: Device names, live values, thresholds, and previous values involved in the trigger are highlighted to make triage faster.
• Operator-friendly context: You can understand the matched condition directly from the alert message in the Alerts view.

Visual Indicators

• Criticality: Alerts are color-coded based on the rule definition.
• Duration: Shows how long the alert has been active.
• Source: Displays the specific device, gateway, and tag that triggered the alert.

Actions

Select an alert from the list to perform actions:

• Acknowledge: Stops escalation notifications (if configured) and updates the status.
• Resolve: Closes the alert. If the underlying condition (e.g., High Temp) persists, a new alert instance will be generated immediately.
• Ignore: Suppresses this specific alert instance without resolving it.

Notifications

To send alerts outside the platform (Email, SMS, Slack), you must configure Notification Channels in the Integrations section. For more information about setting up notifications, see Configure Notifications.