ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-8460) Alerts: AlertDefinition and AlertGroup Automatic Creation On Startup
Date Thu, 27 Nov 2014 19:29:12 GMT

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

Jonathan Hurley updated AMBARI-8460:
------------------------------------
    Attachment: AMBARI-8460.patch.2

> 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
>
>         Attachments: AMBARI-8460.patch, AMBARI-8460.patch.2
>
>
> 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)

Mime
View raw message