[
https://issues.apache.org/jira/browse/AMBARI-11559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566288#comment-14566288
]
Hudson commented on AMBARI-11559:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2760 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2760/])
AMBARI-11559 - Consider Alert Definition Removals When Associated
Services/Components Are Removed (jonathanhurley) (jhurley:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f6c4fd992a4532f08087c60f537e3e21ee44159b)
* ambari-server/src/test/java/org/apache/ambari/server/events/EventsTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertServiceStateListener.java
> Consider Alert Definition Removals When Associated Services/Components Are
> Removed
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-11559
> URL: https://issues.apache.org/jira/browse/AMBARI-11559
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.1.0
>
> Attachments: AMBARI-11559.patch
>
>
> AMBARI-10249 will create a permanent paper trail of alert state change events
> (essentially alert history) that is separate and not coupled to the database
> audit of alert events.
> Currently, removal of a service or a component does not remove the
> definitions associated with the component. It merely clips the tip of the
> history so that no alerts are present anymore. Based on feedback of Ambari
> 2.0.0, this Jira is to track the need to automatically delete alert
> definitions when a service or component is removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
