Alarming, i.e. sending a warning of existing or approaching danger is a major issue when dealing with sensor data. Redbex uses observation monitoring for alarming. While the Send message action can be used to inform human readers about alarm conditions detected, the Create observation alarm action allows to record alarm conditions along with the affected observations over time.
The create observation alarm action can be configured to request acknowledgment for all alarms it creates. Table 1 lists the settings available for an create observation alarm action.
Every alarm that is created will be linked back to the observation monitoring definition that created the alarm. If the observation monitoring definition is deleted that link will be removed but the alarms will stay untouched.
If an observation monitoring definition that already initiated an alarm is modified the condition in that observation monitoring definition might be different than the condition that initiated the alarm.
Setting |
Description |
Severity |
Severity of the created observation alarms. Can be one of 10 predefined severity levels. |
Acknowledging user group |
The user group that has to acknowledge this alarm, can be left empty to define alarms that need no acknowledgment. Note that the acknowledgment obligation is assigned to all users that are member of that group at that point in time when the alarm was created. |
Acknowledging time span |
The maximum time span beginning from the creation of the alarm in which the alarm shall be acknowledged. Together with the automatically recorded creation time stamp this time span is used to calculate the Acknowledging deadline. Alarms that are not acknowledged in this time span are considered as overdue acknowledgments. While it is possible to acknowledge alarms with overdue acknowledgments, the Application Server remembers the fact that the acknowledgment was not given within the acknowledging time span. Setting this time span to a value of 0:0:0 will actually result in an unlimited acknowledging time span. |
Pooling interval |
This is the number of seconds in which consecutive alarms will be considered as a single alarm. |
Table 1: Settings for the create observation alarm action
