Return
-
Title
Data driven rule is not firing alarms -
Description
Set up a new rule with the following settings:
The rule is designed to fire when a particular object state changes and fire the associated alarm. There is nothing wrong with the rule as the condition evaluation changes from false to true when failing however no alarms are received in the dashboard. Always schedule has been applied (rule changed to time driven) and the alarms received.
-
Cause
This issue occurs when there is no metric data in the condition of this rule, it just evaluates an statement based on the status of an object property. The condition evaluates an object property and not a metric (data itself) and so there is no data to drive the rule.
-
Resolution
Follow the steps below to solve the issue:
- Go to "Administration | Rules & Notifications | Rules"
- Select the rule that is causing the problem and click on it
- Click "View and Edit" and then on"Rule Editor" in the upcoming window
- Select the "Rule Definition" tab
- Switch the rule from "Data Drive" to "Time Driven" and tick the box "Enable Trigger without Data"
- Double check the "Behavior" tab to make sure you have not set a specific rule behavior which will avoid the alarms