Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8A8AE10663 for ; Tue, 3 Sep 2013 16:36:53 +0000 (UTC) Received: (qmail 72329 invoked by uid 500); 3 Sep 2013 16:36:53 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 72307 invoked by uid 500); 3 Sep 2013 16:36:53 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 72294 invoked by uid 99); 3 Sep 2013 16:36:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 16:36:52 +0000 Date: Tue, 3 Sep 2013 16:36:52 +0000 (UTC) From: "Dmitry Lysnichenko (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBARI-1534) Add Nagios check for ambari-server process MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko resolved AMBARI-1534. ---------------------------------------- Resolution: Fixed committed to trunk > Add Nagios check for ambari-server process > ------------------------------------------ > > Key: AMBARI-1534 > URL: https://issues.apache.org/jira/browse/AMBARI-1534 > Project: Ambari > Issue Type: Improvement > Reporter: Jeff Sposetti > Assignee: Vitaly Brodetskyi > Attachments: AMBARI-1534.patch > > > There should be a Nagios alert to that watches the ambari-server process. This check should either a) check the process running on the host or b) ping the Ambari Server REST API for status. > Service Description: Ambari Server (ambari-server) process down > Service Group: AMBARI > Check / Retry Interval: 0.25 > Note: need to add new service group AMBARI for Nagios > Question: Should this alert be shown in Ambari Web, since if this alert goes crit, ambari web is down? I think so and this host check should display with the host that is Ambari Server (Hosts > host) so people can see the check is occurring properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira