1.2. Alert Check Counts

Ambari allows you to set the number of alert checks to perform before dispatching a notification. If the alert state changes during a check, Ambari will attempt to check the condition again a number of times (i.e. the “check count”) before dispatching a notification. Increase this number if your environment experiences transient issues resulting in false alerts. The alert state change is still recorded in the /var/log/ambari-server/ambari-alerts.log as a “SOFT” state change. If after a number of checks the alert condition is still triggered, the state change will be considered “HARD” and notifications will be sent.

You can set the check count value globally for all alerts, or override for individual alerts. Use the override for individual alerts in case you have a specific alert (or alerts) that are experiencing transient issues.

Modifying the Global Alert Check Count

Browse to the Alerts section in Ambari Web.
Under the Actions menu, click Manage Alert Settings.
Update the Check Count value.
Click Save.

Modifying the Alert Check Count for Individual Alerts

Browse to the Alerts section in Ambari Web.
Select the alert that 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.

	Note
	Alert check counts are not applicable to AGGREATE alert types. A state change for an AGGREGATE alert will result in a notification dispatch.

	Note
	Changes made using the Ambari UI to the Global alert check count may require a few seconds to appear in the Ambari UI for individual alerts.

​1.2. Alert Check Counts

1.2. Alert Check Counts