Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 25 Aug 2014 20:28:58 +0000 (UTC)
From: "Nate Cole (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12724984.1404311302133.7228.1408998538231@arcas>
In-Reply-To: <JIRA.12724984.1404311302133@arcas>
References: <JIRA.12724984.1404311302133@arcas>
Subject: [jira] [Updated] (AMBARI-6354) Alerts Design and Implementation
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 ]

Nate Cole updated AMBARI-6354:
------------------------------

    Issue Type: Epic  (was: New Feature)

> Alerts Design and Implementation
> --------------------------------
>
>                 Key: AMBARI-6354
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6354
>             Project: Ambari
>          Issue Type: Epic
>          Components: agent, client, controller
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 1.7.0
>
>         Attachments: 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.2#6252)