You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2014/06/24 15:46:25 UTC

[jira] [Resolved] (AMBARI-6253) Disable check_service_freshness at our Nagios config

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

Dmitry Lysnichenko resolved AMBARI-6253.
----------------------------------------

    Resolution: Fixed

committed to trunk

> Disable check_service_freshness at our Nagios config
> ----------------------------------------------------
>
>                 Key: AMBARI-6253
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6253
>             Project: Ambari
>          Issue Type: Task
>          Components: controller
>    Affects Versions: 1.7.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 1.7.0
>
>
> We have check_service_freshness=1 setting in our Nagios configs. But we don't use SERVICE FRESHNESS CHECK functionality. It is used only for service checks triggered outside of Nagios http://nagios.manubulon.com/traduction/docs14en/passivechecks.html



--
This message was sent by Atlassian JIRA
(v6.2#6252)