Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 03170175B8 for ; Wed, 5 Nov 2014 18:53:36 +0000 (UTC) Received: (qmail 73561 invoked by uid 500); 5 Nov 2014 18:53:35 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 73531 invoked by uid 500); 5 Nov 2014 18:53:35 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 73516 invoked by uid 99); 5 Nov 2014 18:53:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Nov 2014 18:53:35 +0000 Date: Wed, 5 Nov 2014 18:53:35 +0000 (UTC) From: "Jonathan Hurley (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-8165) Alerts: Nagios Target for Notifications MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jonathan Hurley created AMBARI-8165: --------------------------------------- Summary: Alerts: Nagios Target for Notifications Key: AMBARI-8165 URL: https://issues.apache.org/jira/browse/AMBARI-8165 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 (v6.3.4#6332)