incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaly Brodetskyi (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-3070) Add Nagios check for ambari-agent process for each host in the cluster
Date Tue, 03 Sep 2013 07:34:51 GMT

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

Vitaly Brodetskyi resolved AMBARI-3070.
---------------------------------------

    Resolution: Duplicate

Duplicate of AMBARI-1533.
                
> Add Nagios check for ambari-agent process for each host in the cluster
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-3070
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3070
>             Project: Ambari
>          Issue Type: Improvement
>          Components: agent
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>             Fix For: 1.4.1
>
>   Original Estimate: 32h
>  Remaining Estimate: 32h
>
> Each host in the cluster runs ambari-agent.
> There should be a Nagios alert to that watches the ambari-agent process. Since the system
does not allow direct communication to an ambari-agent, this check should either a) check
the process running on the host or b) ping the Ambari Server REST API to confirm agent is
still heartbeat'ing.
> This alert should be shown with each Hosts >
> {host}
> in Ambari Web.
> Service Description: Ambari Agent (ambari-agent) process down
> Service Group: AMBARI
> Check / Retry Interval: 0.25
> Note: need to add new service group AMBARI for Nagios

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