Notification Profile Actions
The table below outlines the available notification actions triggered based on specific conditions, such as elapsed time since a new alarm was raised when an alarm has stayed in the same severity for a set duration, or when an alarm was cleared. These conditions can be configured in a single or different notification profiles as needed.
The types of Notification Profile Actions that can be configured are provided below.
Type
| Description
|
Notification Action
| The actions configured in this profile is executed when the configured alarms are created/updated and matches the conditions, and filters configured(if any)
|
Escalation Action
| The actions configured in this profile is executed when the configured alarms are not cleared within the given time period.
|
Clear Action
| The actions configured in this profile is executed when the configured alarms are cleared, and matches filters configured(if any).
|
How is Notification Profiles different from Alarm Rules
Alarm Rules actions are triggered when new
alarms are created with a specific severity or state of an alarm. Notification actions are triggered when new alarms are created and specific conditions that are checked with the managed entity's property are satisfied.
Alarm Rule:
When: Used to trigger actions immediately based on the severity or state of the alarm when the alarm is created. This is useful for direct and immediate responses to specific alarm conditions.
How: Actions can be directly configured within the Alarm Rule. When an alarm is created with a defined state (e.g., warning, critical), the corresponding actions are executed.
Example: If the temperature of a device exceeds a critical threshold, the Alarm Rule can be set to trigger an immediate shutdown of the device to prevent damage.
Notification Profile:
When: Used to trigger actions whenever a new alarm is created, with actions performed when specific conditions of the managed entity property are met. This allows for more flexible and conditional notifications based on criteria.
How: Actions are configured using Notification Profiles. These profiles define how and when notifications should be sent out when specific conditions related to the alarm and the properties of the managed entity are met.
Sending email notification, executing custom functions, and executing webhooks are the actions that can be performed under Notification, Escalation, and Clear actions of the Notification Profile.
Example: When a fuel level alarm is generated for a generator, a Notification Profile can be set to send an escalation email to the maintenance team if the fuel level below 20% alert has stayed for the last two hours.
How is Workflow different from Alarm Rule and Notification Profile
Workflows, alarm rules, and notification profiles are all used for automating actions in the application, but they serve different purposes and operate in distinct ways.
A workflow in an IoT system is a sequence of automated actions or tasks that are performed based on specific conditions or triggers. Workflow actions do not depend on alarms. For example, you can send notification emails to a supervisor whenever an asset is updated in the application. Alarm rule actions are user-defined actions triggered by specific conditions defined in the State of an alarm. For example, you can trigger an email when an alarm with critical severity is created.
Notification profiles are configurations used to define how and when notification actions should be performed in response to alarms or specific conditions.