The Alerts module is listed in the left-hand menu of the Studio app.
With this feature, you can:
- Create and configure alert rules based on specific sensor conditions
- Receive notifications when alerts are triggered
- Escalate alerts automatically if issues remain unresolved
- Resolve alerts once the issue has been addressed
- Review a historical overview of resolved alerts in the Alert Log tab
When an alert is triggered, you'll be notified according to the settings in the alert rule, and the alert will appear in the Active Alerts tab until it's resolved.
Alerts Overview
All users see the same Alerts interface, which includes two views:
- Project-level Alerts (called "Alerts") - accessed from the left-hand Studio menu, showing alerts for the selected Project.
- Organization-level Alerts (called "Active Alerts") - found in the lower-left Studio menu, showing a map and a list of active alerts across multiple Projects.
What is different between users is which Projects appear in the Active Alerts view. This depends entirely on your access:
- If you have access to only one Project, you’ll see alerts and a map view for that single Project. You will not see other Projects in this view, but only the Project you have access to.
- If you have access to multiple Projects in an Organization, you’ll see a list of alerts and a map showing alerts from all Projects you have access to.
Here's a visual representation of what you would see:
Navigating Alerts module
Clicking on Alerts module opens a new view where users are presented with three tabs:
- Active Alerts tab
- Alert Log tab
- Configure tab
Active Alerts
The Active Alerts tab displays all currently active alerts that were triggered by sensor readings exceeding defined limits, changes in sensor status (online/offline), or other state changes.
As shown in the screenshot below, a notification appears on the left side indicating the number of active alerts. This number reflects how many different alerts have been triggered, and the view on the right displays all currently active alerts.
You can 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.
Alert Logs
After an alert is resolved, it is moved to the Alert Log tab. From there, you can:
- Search alerts
- Apply filters
- Export historical alert data
Filtering options include:
- Alert Type
- Alert Status
- Duration
- Acknowledgement
- Corrective Action
- Device Labels
The alert logs offer a summary view to help identify frequently triggered alerts and refine filtering options.
Configure
Use the Configure tab to set alert rules for individual devices, groups of devices with specific labels, or all devices across your Organization.
Clicking Create Alert Rule initiates a guided setup process for configuring a new alert. For detailed instructions, refer to our How to use Alerts in Studio article.