Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Wed, 23 Jan 2013 19:03:14 +0000 (UTC)
From: "Nate Cole (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12628601.1358797713334.180435.1358967794394@arcas>
In-Reply-To: <JIRA.12628601.1358797713334@arcas>
References: <JIRA.12628601.1358797713334@arcas>
Subject: [jira] [Updated] (AMBARI-1237) Expose Nagios alerts thru API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nate Cole updated AMBARI-1237:
------------------------------

    Attachment: AMBARI-1237.patch
    
> Expose Nagios alerts thru API
> -----------------------------
>
>                 Key: AMBARI-1237
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1237
>             Project: Ambari
>          Issue Type: Improvement
>          Components: controller
>    Affects Versions: 1.2.0
>            Reporter: Yusaku Sako
>             Fix For: 1.3.0
>
>         Attachments: AMBARI-1237.patch
>
>
> Currently, Ambari Web retrieves Nagios alerts directly via the HTTP port from the Nagios Server.  Nagios alerts won't show up if there is a firewall and the client machine cannot directly talk to the Nagios Server.

--
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