[
https://issues.apache.org/jira/browse/AMBARI-6354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110839#comment-14110839
]
vitthal (Suhas) Gogate commented on AMBARI-6354:
------------------------------------------------
I think by design it would be good to have Ambari collection of alerts be
default but optional i.e. if I choose to go with Nagios, I may not want
Ambari's default alert monitoring. i.e. Ambari's inbuilt alert monitoring can
be treated as optional pluggable service. Is this achievable after refactor
work?
Again current refactor work to remove Nagios dependency is good but at the same
time I wanted to see how can we make it pluggable design and wanted to help out
along those lines.
I am reviewing the design and code and will propose some specific changes w/
minimal disruption to exiting work as possible..
> 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)
