ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <>
Subject [jira] [Commented] (AMBARI-8165) Alerts: Nagios Target for Notifications
Date Thu, 06 Nov 2014 17:20:33 GMT


Jonathan Hurley commented on AMBARI-8165:

It has been decided that option #1 is the most feasible. A "contrib" script(s) will be written
to allow users of Ambari who wish to retain Nagios the ability to pull alert data in from

> Alerts: Nagios Target for Notifications
> ---------------------------------------
>                 Key: AMBARI-8165
>                 URL:
>             Project: Ambari
>          Issue Type: Task
>          Components: contrib
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: 2.0.0
> The Ambari Server will be responsible for scheduling the dispatching of alerts that have
been received and not yet processed for outbound notification. On a schedule, Ambari will
determine the alert targets that should be receiving some sort of notification and then it
will gather all alert data for all alerts that are destined for that alert target.
> Nagios is a required notification mechanism. The Nagios server will surface the current
state of each alert defined in the system. In order to accomplish this there are two possible
methods for implementation:
> 1) Write a python script that Nagios will execute on its own schedule which can then
retrieve the current alerts from Ambari's REST APIs. The script will take a combination of
parameters (host, security, certificate, etc) in order to make the requests.
> 2) Write a dispatcher that can handle pushing data to a Nagios server. There will no
longer be an agent running on Nagios, so this method would need to work with Nagios' built-in
mechanism, if any, for publishing data into Nagios.

This message was sent by Atlassian JIRA

View raw message