Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 25 Nov 2014 18:02:13 +0000 (UTC)
From: "Jonathan Hurley (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12757458.1416850700000.17774.1416938533057@Atlassian.JIRA>
In-Reply-To: <JIRA.12757458.1416850700000@Atlassian.JIRA>
References: <JIRA.12757458.1416850700000@Atlassian.JIRA>
 <JIRA.12757458.1416850700662@arcas>
Subject: [jira] [Updated] (AMBARI-8430) Current Alerts Should Be Cleaned Up
 With Ambari Cluster/Service/Component/Host Changes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-8430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Hurley updated AMBARI-8430:
------------------------------------
    Attachment:     (was: AMBARI-8430.patch)

> Current Alerts Should Be Cleaned Up With Ambari Cluster/Service/Component/Host Changes
> --------------------------------------------------------------------------------------
>
>                 Key: AMBARI-8430
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8430
>             Project: Ambari
>          Issue Type: Bug
>          Components: alerts, ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> When an active alert definition is disabled, instances of that alert definition should not show up when query the cluster/service/host for alerts. 
> STR:
> 1) Cause an alert to trigger (shut something down)
> 2) Disable the alert definition for that alert
> 3) CRITICAL alert stays in the list of current cluster alerts
> Expected: The API should prevent disabled alerts from being returned.
> Beyond this, the API should also clean up current alerts that are no longer valid. This includes:
> 1) Alerts that are for hosts which no longer exist
> 2) Alerts that are for a component that is no longer installed on a host
> 3) Alerts for services that are no longer part of the cluster (including the default group for that service)
> Alerts that are being received should also be verified for validity so that an invalid alert that was cached by the agent doesn't re-appear.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)