You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2014/09/09 00:46:29 UTC

[jira] [Updated] (AMBARI-6354) Alerts Redesign

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

Yusaku Sako updated AMBARI-6354:
--------------------------------
    Summary: Alerts Redesign  (was: Alerts Design and Implementation)

> 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
>
>
> 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)