Return
-
Title
Brief, incorrect alarms fired from rule "DBSS - Collection Status" -
Description
Randomly the rule "DBSS - Collection Status" is firing an alarm. Few minutes later the alarm is getting cleared.
All data is being collected properly, so why is the alarm fired?
-
Cause
Network latencies or instabilities are causing some collections to fail. This happen irregular. -
Resolution
To avoid wrong alarms due to network problems, please modify the rule behaviour of the rule.
- Go to: "Administration | Rules & Notification | Manage Rules"
- Search for the rule and open it for editing
- Click on the tab "Behavior" and modify the fire action, for example tick the first one and set it to "Fire action if 2 consecutive evaluations are true" which means that the rule needs 2 negative evaluation before it will fire an alarm.