[
https://issues.apache.org/jira/browse/AMBARI-10348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482435#comment-14482435
]
Hudson commented on AMBARI-10348:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2231 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2231/])
AMBARI-10348 - Alerts: Generate Server Side Alerts For Agent Health and Alert
Staleness (jonathanhurley) (jhurley:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ad8e9ea8cc85f3ccc1aca23a5935eed2939904fe)
* ambari-web/app/controllers/main/alerts/definition_configs_controller.js
*
ambari-server/src/main/java/org/apache/ambari/server/api/services/AlertGroupService.java
*
ambari-server/src/test/java/org/apache/ambari/server/alerts/AgentHeartbeatAlertRunnableTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/metadata/AgentAlertDefinitionsTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionHash.java
*
ambari-server/src/test/java/org/apache/ambari/server/events/MockEventListener.java
*
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertMaintenanceModeListener.java
*
ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/api/services/AlertDefinitionService.java
* ambari-web/app/mappers/alert_definitions_mapper.js
*
ambari-server/src/main/java/org/apache/ambari/server/metadata/AmbariServiceAlertDefinitions.java
*
ambari-server/src/main/java/org/apache/ambari/server/alerts/AgentHeartbeatAlertRunnable.java
*
ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
*
ambari-server/src/main/java/org/apache/ambari/server/api/services/AlertHistoryService.java
*
ambari-server/src/main/java/org/apache/ambari/server/metadata/AgentAlertDefinitions.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/alert/SourceType.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/services/AmbariServerAlertService.java
*
ambari-server/src/test/java/org/apache/ambari/server/alerts/StaleAlertRunnableTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertHostListener.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/alert/ServerSource.java
*
ambari-server/src/main/java/org/apache/ambari/server/api/services/AlertTargetService.java
*
ambari-server/src/main/java/org/apache/ambari/server/alerts/StaleAlertRunnable.java
*
ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertDefinitionFactory.java
* ambari-server/src/main/resources/alerts.json
*
ambari-server/src/main/java/org/apache/ambari/server/api/services/AlertService.java
*
ambari-server/src/main/java/org/apache/ambari/server/api/services/AlertNoticeService.java
* ambari-server/src/main/java/org/apache/ambari/server/orm/dao/AlertsDAO.java
> Alerts: Generate Server Side Alerts For Agent Health and Alert Staleness
> ------------------------------------------------------------------------
>
> Key: AMBARI-10348
> URL: https://issues.apache.org/jira/browse/AMBARI-10348
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-10348.patch
>
>
> Due to alerts being run on distributed platforms - we have problem wherein if
> alert is scheduled to run on a host that goes down - its not obvious to
> customer that alerts are not running and something is wrong. We need to do 2
> thigns:
> 1. Generate an alert when not heard from Ambari Agent for quite sometime
> 2. Fire alerts which havent been run for quite sometime - saying they havent
> been run due to host not responding.
> Seems like 2 new alerts are required, both of which being "Server Side"
> (which is a new concept).
> - Ambari Server will need to maintain information about the last heartbeat
> from a host and produce alerts when a heartbeat has not been received. A new
> {{@AmbariService}} can handle this.
> - Ambari Server will need to periodically check the last timestamp of all
> enabled alert instances and determine if the alert has not run within a
> certain period of time. A new {{@AmbariService}} can handle this.
> We should utilize the alerts.json defined outside the stack since this
> affects hosts and alert instants and is not bound to a cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
