Skip to content

Commit e8f63cc

Browse files
committed
Add reviewer's changes and minor copy edits: apache-ambari-troubleshoot-stale-alerts
1 parent 0fdc535 commit e8f63cc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/hdinsight/hadoop/apache-ambari-troubleshoot-stale-alerts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ In the Apache Ambari UI, you might see an alert like this:
2121

2222
## Cause
2323

24-
Ambari agents continuously monitor the health of many resources. Each health check, or *alert*, is configured to run at predefined time intervals. After each alert runs, Ambari agents report the status back to the Ambari server. An alert that doesn't run on time generates a *stale alert*. If the Ambari server detects any stale alerts, it triggers an "Ambari Server Alerts" alert.
24+
Ambari agents continuously monitor the health of many resources. *Alerts* can be configured to notify you whether specific cluster properties are within predetermined thresholds. After each resource check runs, if the alert condition is met, Ambari agents report the status back to the Ambari server and trigger an alert. If an alert isn't checked according to the interval in its Alert Profile, the server triggers an *Ambari Server Stale Alerts* alert.
2525

2626
There are various reasons why a health check might not run at its defined interval:
2727

0 commit comments

Comments
 (0)