Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 29 Oct 2014 18:41:33 +0000 (UTC)
From: "Jonathan Hurley (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12724984.1404311302000.365220.1414608093805@Atlassian.JIRA>
In-Reply-To: <JIRA.12724984.1404311302000@Atlassian.JIRA>
References: <JIRA.12724984.1404311302000@Atlassian.JIRA>
 <JIRA.12724984.1404311302133@arcas>
Subject: [jira] [Updated] (AMBARI-6354) Alerts Redesign
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Hurley updated AMBARI-6354:
------------------------------------
    Attachment: AlertTechDesignPublic.pdf

> Alerts Redesign
> ---------------
>
>                 Key: AMBARI-6354
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6354
>             Project: Ambari
>          Issue Type: Epic
>          Components: ambari-agent, ambari-server, ambari-web
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 2.0.0
>
>         Attachments: AlertTechDesignPublic.pdf, AlertTechDesignPublic.pdf
>
>
> The purpose of this umbrella JIRA is to track a new feature that enables Ambari to be the source of Alert data for a cluster.
> * "Black box" Nagios and not make it a hard dependency of Ambari.
> * Allow custom defined alerts and thresholds.
> * Flexibly define how alerts get published, and recipients of those alerts.
> * Use stacks to define baseline alerts for a cluster that can themselves be customized.
> (As design documents are completed, they will be attached to this JIRA)


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