[jira] [Commented] (AMBARI-11559) Consider Alert Definition Removals When Associated Services/Components Are Removed

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-11559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566198#comment-14566198 ] 

Hadoop QA commented on AMBARI-11559:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12736357/AMBARI-11559.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2944//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2944//console

This message is automatically generated.

> 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)