AlphaX allows you to set up various alert conditions to monitor sensor events and trigger alerts based on predefined criteria. This guide explains how to configure these alert conditions.
By following these guidelines, you can effectively monitor and manage Alerts in AlphaX, ensuring timely notifications and responses to critical situations.
Alert Condition View
Understanding Condition Modes
-
First Mode
-
This mode matches the first condition that is true from the top of the list.
-
Once a condition is matched, it stops processing further conditions.
-
Useful when you want the system to trigger an alert immediately upon meeting the first criterion.
-
-
All Mode
-
This mode evaluates all the conditions in the list.
-
Useful when you need all specified conditions to be evaluated and potentially trigger multiple alerts.
-
Types of Conditions
AlphaX Alerts support three types of conditions:
-
Value-Based Conditions
-
Options: Above, Equal, Below
-
Use this type to trigger alerts based on numerical values.
-
Example: Trigger an alert if a temperature sensor reads below 70 degrees.
-
-
Status-Based Conditions
-
Options: Payload Received, Device Offline, Error Code
-
Use this type to monitor specific statuses of devices or systems.
-
Example: Trigger an alert when a device goes offline or an error code is received.
-
-
AI-Based Conditions
-
Option: Anomaly Detected
-
Use this type to leverage AI to detect unusual patterns or behaviors.
-
Example: Trigger an alert when the system detects an anomaly in data patterns.
-
Configuring Alert Conditions
-
Adding a Condition
-
Click the + Add New Condition button.
-
Enter a Condition Label to describe the condition.
-
Set the Limit value if applicable (e.g., 70 for Below 70% Capacity).
-
Choose an Alert Condition from the dropdown (e.g., Payload Received, Error Code).
-
-
Deleting a Condition
-
Click the trash can icon to the right of the condition you wish to delete.
-
Example Setup
Condition 1: Data Sent
-
Condition Label: Data Sent
-
Limit: 0
-
Alert Condition: Payload Received
Condition 2: Below 70% Capacity
-
Condition Label: Below 70% Capacity
-
Limit: 70
-
Alert Condition: Value goes below limit
Condition 3: Error Received
-
Condition Label: Error Received
-
Limit: 434
-
Alert Condition: Error Code
Tips for Effective Alert Management
-
Prioritise Conditions: When using First Mode, arrange conditions by priority to ensure the most critical alerts are processed first.
-
Monitor Critical Systems: Use status-based conditions to keep an eye on vital system statuses like device connectivity and error codes.
-
Leverage AI: Incorporate AI-based conditions to detect and respond to unusual patterns that might not be immediately obvious through value-based conditions.