incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate Cole (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-1237) Expose Nagios alerts thru API
Date Thu, 24 Jan 2013 20:47:12 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561966#comment-13561966
] 

Nate Cole commented on AMBARI-1237:
-----------------------------------

You can access the property via:
/api/v1/clusters/<name>/hosts/<host>/host_components/NAGIOS_SERVER

The resulting JSON will contain a new attribute
{noformat}
{
  "HostRoles": {
    "nagios_alerts": "<some escaped json>"
  }
}
{noformat}
                
> 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
>            Assignee: Nate Cole
>             Fix For: 1.3.0, 1.2.1
>
>         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

Mime
View raw message