From 1159ad485709f760f94eae832f4071d65d41bdf9 Mon Sep 17 00:00:00 2001 From: Tim Abbott Date: Sun, 31 Jul 2016 00:11:51 -0700 Subject: [PATCH] puppet: Upgrade nagios.cfg with modern defaults. --- puppet/zulip_ops/files/nagios3/nagios.cfg | 29 +++++++++++++++++++++++ 1 file changed, 29 insertions(+) diff --git a/puppet/zulip_ops/files/nagios3/nagios.cfg b/puppet/zulip_ops/files/nagios3/nagios.cfg index 4fc28c1b12..59560260c8 100644 --- a/puppet/zulip_ops/files/nagios3/nagios.cfg +++ b/puppet/zulip_ops/files/nagios3/nagios.cfg @@ -905,6 +905,19 @@ process_performance_data=0 +# HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS +# THese options determine wether the core will process empty perfdata +# results or not. This is needed for distributed monitoring, and intentionally +# turned on by default. +# If you don't require empty perfdata - saving some cpu cycles +# on unwanted macro calculation - you can turn that off. Be careful! +# Values: 1 = enable, 0 = disable + +#host_perfdata_process_empty_results=1 +#service_perfdata_process_empty_results=1 + + + # OBSESS OVER SERVICE CHECKS OPTION # This determines whether or not Nagios will obsess over service # checks and run the ocsp_command defined below. Unless you're @@ -1020,6 +1033,22 @@ service_freshness_check_interval=60 +# SERVICE CHECK TIMEOUT STATE +# This setting determines the state Nagios will report when a +# service check times out - that is does not respond within +# service_check_timeout seconds. This can be useful if a +# machine is running at too high a load and you do not want +# to consider a failed service check to be critical (the default). +# Valid settings are: +# c - Critical (default) +# u - Unknown +# w - Warning +# o - OK + +service_check_timeout_state=c + + + # HOST FRESHNESS CHECK OPTION # This option determines whether or not Nagios will periodically # check the "freshness" of host results. Enabling this option