ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-8084) Alerts: Convert Bigtop Stack Nagios Alerts
Date Thu, 06 Nov 2014 18:26:34 GMT


Hadoop QA commented on AMBARI-8084:

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment
  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 2 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:
Console output:

This message is automatically generated.

> Alerts: Convert Bigtop Stack Nagios Alerts
> ------------------------------------------
>                 Key: AMBARI-8084
>                 URL:
>             Project: Ambari
>          Issue Type: Task
>          Components: alerts, ambari-server
>            Reporter: Newton Alex
>            Assignee: Jonathan Hurley
>             Fix For: 2.0.0
>         Attachments: AMBARI-8084.patch
> Update the BT stack to start using the new Ambari alerting system.
> Here is the email from [~jonathan.hurley] for context:
> -----
> Hi Committers & Contributors,
> With Ambari 2.0, a new alerts framework has been implemented with the intent to replace
Nagios. If you would like to learn more about this feature, the design documents can be found
in the Jira epic at 
> The work has been completed to move the HDP 2.x stack over from Nagios to the internal
alerts framework. However, HDP 1.x and Bigtop have not yet been migrated. I would like to
propose that we move all stacks off of Nagios so that we can remove that dependency from Ambari
> This also means that upon upgrading from a prior Nagios-enabled release of Ambari, Nagios
will be removed as a dependent service. It will no longer be a part of the managed cluster.
> This will allow us to also remove any Nagios-specific areas of the codebase that would
otherwise need to remain for legacy purposes. It would also relieve the requirement on clients
to have intimate knowledge of which stack/version can be Nagios-enabled.
> ---------

This message was sent by Atlassian JIRA

View raw message