ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yurii Shylov" <>
Subject Re: Review Request 28644: Alerts: Nagios Target for Notifications
Date Mon, 08 Dec 2014 17:34:30 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated Дек. 8, 2014, 5:34 п.п.)

Review request for Ambari, Jonathan Hurley and Nate Cole.


Fixed script locations

Bugs: AMBARI-8165

Repository: ambari


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.

Diffs (updated)

  contrib/addons/package/deb/ a64e045 
  contrib/addons/package/rpm/ 42a2e28 
  contrib/nagios-alerts/plugins/ PRE-CREATION 
  contrib/nagios-alerts/plugins/ PRE-CREATION 



Total run:674
Total errors:0
Total failures:0


Yurii Shylov

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message