[
https://issues.apache.org/jira/browse/AMBARI-6354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110055#comment-14110055
]
Nate Cole commented on AMBARI-6354:
-----------------------------------
The facility already exists to use any infrastructure they want - see
individual stack components for NAGIOS service definitions. As for the
refactor, we still want Ambari to do all the collection such that you could
still get information about the health of your cluster without any such
dependencies. Making it pluggable is certainly possible, but the initial goal
is to remove the dependency of Nagios at this time.
> 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)
