Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 26 Nov 2014 20:32:12 +0000 (UTC)
From: "Jonathan Hurley (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12758061.1417033887000.29793.1417033932491@Atlassian.JIRA>
In-Reply-To: <JIRA.12758061.1417033887000@Atlassian.JIRA>
References: <JIRA.12758061.1417033887000@Atlassian.JIRA>
 <JIRA.12758061.1417033887950@arcas>
Subject: [jira] [Created] (AMBARI-8460) Alerts: AlertDefinition and
 AlertGroup Automatic Creation On Startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Jonathan Hurley created AMBARI-8460:
---------------------------------------

             Summary: Alerts: AlertDefinition and AlertGroup Automatic Creation On Startup
                 Key: AMBARI-8460
                 URL: https://issues.apache.org/jira/browse/AMBARI-8460
             Project: Ambari
          Issue Type: Task
          Components: alerts, ambari-server
    Affects Versions: 2.0.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
             Fix For: 2.0.0


When upgrading to a version of Ambari that supports the new alert framework, the AlertDefinition and AlertGroup tables must be populated with the definitions and default groups for services that are already installed in the cluster.

Most of this is actually taken care of automatically. When Ambari 2.0.0 starts up, it will read all of the services for each cluster and then it will determine if any of the stack alert definitions for that service exist or are new. They will all be new, causing them to be created.

However, the alert groups will not be created automatically for the services. When adding alert definitions, we must ensure that a default group is already created.


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