In this article, you will learn how to manage and interact with alerts by acknowledging them, adding comments, and assigning corrective actions - all of which are recorded in the alert timeline. Every alert follows a lifecycle, which looks like this:
-
Open: Alert is triggered when sensor readings are outside the defined limits.
-
Acknowledged: (Optional) A user acknowledges the alert, taking responsibility.
-
Corrective Action: (Optional) A user adds a description of corrective steps taken.
-
Monitoring: Status set to monitor the effectiveness of the corrective action.
-
Resolved: The alert is resolved automatically when sensor data returns to normal.
This article assumes you have already set up the alert rule. If you haven’t done so yet, please refer to our guide on How to create Alerts.
Acknowledging the alert
When an alert is triggered, you’ll receive a notification based on the configured alert rules.
The Active Alerts tab shows all alerts that are currently active. These may be triggered by sensor readings exceeding predefined thresholds, changes in sensor connection status (such as going online or offline), or other significant state changes.
A notification icon on the left indicates the total number of active alerts. This count represents how many unique alerts have been triggered, while the right-hand view displays the full list of active alerts.
To acknowledge the alert, simply click on Acknowledge, write an optional comment, and submit the acknowledgment by clicking Confirm. This means that a user took responsibility for the alert and will follow up with action to resolve it.
The default duration of the Acknowledgment is 4 hours, but it can be customised from the Alert Rule - "Advanced Options" dropdown.
Corrective action
Next, the user who acknowledged the alert can provide a description of the corrective actions taken. Once submitted, the alert enters the Monitoring phase, which continues until the sensor returns to its set threshold.
Escalating the alert
If the alert remains unacknowledged, unaddressed, or unresolved, you can escalate it to notify another user via email for follow-up. For details, refer to How to create Alerts.
Resolving the alert
When the device returns to its defined threshold, the alert automatically resolves and is removed from the Active Alerts view. It will still be accessible in the Alert Log for reference.