Modifying Alert Check Counts
Ambari enables you to set the number of alert checks to perform before dispatching a notification. If the alert state changes during a check, Ambari attempts to check the condition a specified number of times (the check count) before dispatching a notification.
Alert check counts are not applicable to AGGREATE alert types. A state change for an AGGREGATE alert results in a notification dispatch.
If your environment experiences transient issues resulting in false alerts, you can increase the check count. In this case, the alert state change is still recorded, but as a SOFT state change. If the alert condition is still triggered after the specified number of checks, the state change is then considered HARD, and notifications are sent.
You generally want to set the check count value globally for all alerts, but you can also override that value for individual alerts if a specific alert or alerts is experiencing transient issues.
To modify the global alert check count:
Steps
Browse to the Alerts section in Ambari Web.
In the Ambari Web, Actions menu, click Manage Alert Settings.
Update the Check Count value.
Click Save.
Changes made to the global alert check count might require a few seconds to appear in the Ambari UI for individual alerts.
To override the global alert check count for individual alerts:
Steps
Browse to the Alerts section in Ambari Web.
Select the alert for which you want to set a specific Check Count.
On the right, click the Edit icon next to the Check Count property.
Update the Check Count value.
Click Save.
More Information