A key part of managing your Embedded network is being able to respond as soon as possible to events or anomalies requiring action. In this section, learn how to set up flexible notifications to easily manage your messages and alerts.
Notification are sent by channels (email or webhook). Those channels are bundled into topics. For example:
Staff
which comprises channels sending emails only to staff membersService
which comprises channels sending emails just to service workersTo get a notification when a defined condition is met you need to create a rule. For example:
Device is offline
and associate it with the Topic Staff
. Staff members receive an email to turn on the edge device.Temperature > 100 °C
and associate it with the Topic Service
. A service worker receives an email to check the health of the edge device.To use rules and notifications make sure Real Time Rule Engine is enabled.
Rules are limited to the following thresholds:
See:
Each time when threshold triggers, a unique Alarm with specified severity is created.
Alarm severity defines how important the alarm is. We support the following alarm severity levels: Warning, Minor, Major and Critical.
The maximum number of thresholds to be applied per Rule is four, equal to the number of severity levels.
All the open alarms are reflected in the Alarms list (Management Console > Alarms) and can be filtered by severity levels, type, creation time and so on. Thus, users can see metric or device specific alarms correspondingly in Devices and Metrics pages.
A Notification topic is a communication bridge that receives notification messages triggered by Rules and sends them to Channels which are subscribed to the Topic.
See: