1 ##############################################################################
3 # naemon.cfg - Sample Main Config File for Naemon 1.0.7
5 # Read the documentation for more information on this configuration
6 # file. I've provided some comments here, but things may not be so
7 # clear without further explanation.
10 ##############################################################################
14 # This is the main log file where service and host events are logged
15 # for historical purposes. This should be the first option specified
16 # in the config file!!!
18 log_file=/var/log/naemon/naemon.log
22 # OBJECT CONFIGURATION FILE(S)
23 # These are the object configuration files in which you define hosts,
24 # host groups, contacts, contact groups, services, etc.
25 # You can split your object definitions across several config files
26 # if you wish (as shown below), or keep them all in a single config file.
28 # You can specify individual object config files as shown below:
29 cfg_file=<%= @objects %>
30 #cfg_file=/etc/naemon/objects/commands.cfg
31 #cfg_file=/etc/naemon/objects/contacts.cfg
32 #cfg_file=/etc/naemon/objects/timeperiods.cfg
33 #cfg_file=/etc/naemon/objects/templates.cfg
36 # You can also tell naemon to process all config files (with a .cfg
37 # extension) in a particular directory by using the cfg_dir
38 # directive as shown below:
39 #cfg_dir=/etc/naemon/conf.d
45 # This option determines where object definitions are cached when
46 # naemon starts/restarts. The CGIs read object definitions from
47 # this cache file (rather than looking at the object config files
48 # directly) in order to prevent inconsistencies that can occur
49 # when the config files are modified after naemon starts.
51 object_cache_file=/var/lib/naemon/objects.cache
55 # PRE-CACHED OBJECT FILE
56 # This options determines the location of the precached object file.
57 # If you run naemon with the -p command line option, it will preprocess
58 # your object configuration file(s) and write the cached config to this
59 # file. You can then start naemon with the -u option to have it read
60 # object definitions from this precached file, rather than the standard
61 # object configuration files (see the cfg_file and cfg_dir options above).
62 # Using a precached object file can speed up the time needed to (re)start
63 # the naemon process if you've got a large and/or complex configuration.
64 # Read the documentation section on optimizing naemon to find our more
65 # about how this feature works.
67 precached_object_file=/var/lib/naemon/objects.precache
72 # This is an optional resource file that contains $USERx$ macro
73 # definitions. Multiple resource files can be specified by using
74 # multiple resource_file definitions. The CGIs will not attempt to
75 # read the contents of resource files, so information that is
76 # considered to be sensitive (usernames, passwords, etc) can be
77 # defined as macros in this file and restrictive permissions (600)
78 # can be placed on this file.
80 resource_file=/etc/naemon/resource.cfg
85 # This is where the current status of all monitored services and
86 # hosts is stored. Its contents are read and processed by the CGIs.
87 # The contents of the status file are deleted every time naemon
90 status_file=/var/lib/naemon/status.dat
94 # STATUS FILE UPDATE INTERVAL
95 # This option determines the frequency (in seconds) that
96 # naemon will periodically dump program, host, and
97 # service status data. Set it to 0 to disable updates.
99 status_update_interval=10
103 # EXTERNAL COMMAND OPTION
104 # This option allows you to specify whether or not Naemon should check
105 # for external commands (in the command file defined below). By default
106 # Naemon will *not* check for external commands, just to be on the
107 # cautious side. If you want to be able to use the CGI command interface
108 # you will have to enable this.
109 # Values: 0 = disable commands, 1 = enable commands
111 check_external_commands=1
115 # EXTERNAL COMMAND FILE
116 # This is the file that Naemon checks for external command requests.
117 # It is also where the command CGI will write commands that are submitted
118 # by users, so it must be writeable by the user that the web server
119 # is running as (usually 'nobody'). Permissions should be set at the
120 # directory level instead of on the file, as the file is deleted every
121 # time its contents are processed.
123 command_file=/var/lib/naemon/naemon.cmd
127 # QUERY HANDLER INTERFACE
128 # This is the socket that is created for the Query Handler interface
130 #query_socket=/var/lib/naemon/naemon.qh
135 # This is the lockfile that Naemon will use to store its PID number
136 # in when it is running in daemon mode.
138 lock_file=/run/naemon/naemon.pid
143 # This is a temporary file that is used as scratch space when Naemon
144 # updates the status log, cleans the comment file, etc. This file
145 # is created, used, and deleted throughout the time that Naemon is
148 temp_file=/var/lib/naemon/naemon.tmp
153 # This is path where Naemon can create temp files for service and
154 # host check results, etc.
156 temp_path=/var/cache/naemon
160 # EVENT BROKER OPTIONS
161 # Controls what (if any) data gets sent to the event broker.
162 # Values: 0 = Broker nothing
163 # -1 = Broker everything
164 # <other> = See documentation
166 event_broker_options=-1
170 # EVENT BROKER MODULE(S)
171 # This directive is used to specify an event broker module that should
172 # be loaded by Naemon at startup. Use multiple directives if you want
173 # to load more than one module. Arguments that should be passed to
174 # the module at startup are seperated from the module path by a space.
178 # broker_module=<modulepath> [moduleargs]
180 #broker_module=/usr/lib/naemon/naemon-livestatus/livestatus.so /var/cache/naemon/live
181 #broker_module=/somewhere/module1.o
182 #broker_module=/somewhere/module2.o arg1 arg2=3 debug=0
184 # In order to provide drop-in support for new modules, you can also make use of
185 # the include_dir directive. The include_dir directive causes Naemon to parse
186 # any configuration (not just object configuration, as with cfg_dir) as if the
187 # contents of the files in the pointed-to directory was included on this line.
188 # The path to the directory is relative to the path of the main naemon.cfg
190 # include_dir=module-conf.d
193 # This is the directory where archived (rotated) log files are placed by the
194 # logrotate daemon. It is used by out of core add-ons to discover the logfiles.
196 log_archive_path=/var/log/naemon/archives
201 # If you want messages logged to the syslog facility, as well as the
202 # Naemon log file set this option to 1. If not, set it to 0.
206 # NOTIFICATION LOGGING OPTION
207 # If you don't want notifications to be logged, set this value to 0.
208 # If notifications should be logged, set the value to 1.
212 # Notification suppression reason (NSR) logging causes the reason for a
213 # notification suppression to be logged, when it occurs. This can potentially
214 # add some noise to your log file, but is highly useful when troubleshooting
215 # missing notifications.
217 enable_notification_suppression_reason_logging=1
220 # SERVICE RETRY LOGGING OPTION
221 # If you don't want service check retries to be logged, set this value
222 # to 0. If retries should be logged, set the value to 1.
224 log_service_retries=1
228 # HOST RETRY LOGGING OPTION
229 # If you don't want host check retries to be logged, set this value to
230 # 0. If retries should be logged, set the value to 1.
236 # EVENT HANDLER LOGGING OPTION
237 # If you don't want host and service event handlers to be logged, set
238 # this value to 0. If event handlers should be logged, set the value
245 # INITIAL STATES LOGGING OPTION
246 # If you want Naemon to log all initial host and service states to
247 # the main log file (the first time the service or host is checked)
248 # you can enable this option by setting this value to 1. If you
249 # are not using an external application that does long term state
250 # statistics reporting, you do not need to enable this option. In
251 # this case, set the value to 0.
257 # CURRENT STATES LOGGING OPTION
258 # If you don't want Naemon to log all current host and service states
259 # after log has been rotated to the main log file, you can disable this
260 # option by setting this value to 0. Default value is 1.
266 # EXTERNAL COMMANDS LOGGING OPTION
267 # If you don't want Naemon to log external commands, set this value
268 # to 0. If external commands should be logged, set this value to 1.
269 # Note: This option does not include logging of passive service
270 # checks - see the option below for controlling whether or not
271 # passive checks are logged.
273 log_external_commands=1
277 # PASSIVE CHECKS LOGGING OPTION
278 # If you don't want Naemon to log passive host and service checks, set
279 # this value to 0. If passive checks should be logged, set
286 # GLOBAL HOST AND SERVICE EVENT HANDLERS
287 # These options allow you to specify a host and service event handler
288 # command that is to be run for every host or service state change.
289 # The global event handler is executed immediately prior to the event
290 # handler that you have optionally specified in each host or
291 # service definition. The command argument is the short name of a
292 # command definition that you define in your host configuration file.
293 # Read the HTML docs for more information.
295 #global_host_event_handler=somecommand
296 #global_service_event_handler=somecommand
300 # MAXIMUM CONCURRENT SERVICE CHECKS
301 # This option allows you to specify the maximum number of
302 # service checks that can be run in parallel at any given time.
303 # Specifying a value of 1 for this variable essentially prevents
304 # any service checks from being parallelized. A value of 0
305 # will not restrict the number of concurrent checks that are
308 max_concurrent_checks=0
312 # This is directory where Naemon reads check results of host and
313 # service checks to further process them.
315 # Note: Naemon does not require this folder internally but it still
316 # can be used to pass check results to Naemon.
318 check_result_path=/var/cache/naemon/checkresults
321 # CACHED HOST CHECK HORIZON
322 # This option determines the maximum amount of time (in seconds)
323 # that the state of a previous host check is considered current.
324 # Cached host states (from host checks that were performed more
325 # recently that the timeframe specified by this value) can immensely
326 # improve performance in regards to the host check logic.
327 # Too high of a value for this option may result in inaccurate host
328 # states being used by Naemon, while a lower value may result in a
329 # performance hit for host checks. Use a value of 0 to disable host
332 cached_host_check_horizon=15
336 # CACHED SERVICE CHECK HORIZON
337 # This option determines the maximum amount of time (in seconds)
338 # that the state of a previous service check is considered current.
339 # Cached service states (from service checks that were performed more
340 # recently that the timeframe specified by this value) can immensely
341 # improve performance in regards to predictive dependency checks.
342 # Use a value of 0 to disable service check caching.
344 cached_service_check_horizon=15
348 # ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
349 # This option determines whether or not Naemon will attempt to execute
350 # checks of hosts when it predicts that future dependency logic test
351 # may be needed. These predictive checks can help ensure that your
352 # host dependency logic works well.
354 # 0 = Disable predictive checks
355 # 1 = Enable predictive checks (default)
357 enable_predictive_host_dependency_checks=1
361 # ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
362 # This option determines whether or not Naemon will attempt to execute
363 # checks of service when it predicts that future dependency logic test
364 # may be needed. These predictive checks can help ensure that your
365 # service dependency logic works well.
367 # 0 = Disable predictive checks
368 # 1 = Enable predictive checks (default)
370 enable_predictive_service_dependency_checks=1
374 # SOFT STATE DEPENDENCIES
375 # This option determines whether or not Naemon will use soft state
376 # information when checking host and service dependencies. Normally
377 # Naemon will only use the latest hard host or service state when
378 # checking dependencies. If you want it to use the latest state (regardless
379 # of whether its a soft or hard state type), enable this option.
381 # 0 = Don't use soft state dependencies (default)
382 # 1 = Use soft state dependencies
384 soft_state_dependencies=0
388 # TIME CHANGE ADJUSTMENT THRESHOLDS
389 # These options determine when Naemon will react to detected changes
390 # in system time (either forward or backwards).
392 #time_change_threshold=900
397 # These options control how much time Naemon will allow various
398 # types of commands to execute before killing them off. Options
399 # are available for controlling maximum time allotted for
400 # service checks, host checks, event handlers, notifications, the
401 # ocsp command, and performance data commands. All values are in
404 service_check_timeout=75
405 host_check_timeout=30
406 event_handler_timeout=30
407 notification_timeout=30
413 # RETAIN STATE INFORMATION
414 # This setting determines whether or not Naemon will save state
415 # information for services and hosts before it shuts down. Upon
416 # startup Naemon will reload all saved service and host state
417 # information before starting to monitor. This is useful for
418 # maintaining long-term data on state statistics, etc, but will
419 # slow Naemon down a bit when it (re)starts. Since its only
420 # a one-time penalty, I think its well worth the additional
423 retain_state_information=1
427 # STATE RETENTION FILE
428 # This is the file that Naemon should use to store host and
429 # service state information before it shuts down. The state
430 # information in this file is also read immediately prior to
431 # starting to monitor the network when Naemon is restarted.
432 # This file is used only if the retain_state_information
433 # variable is set to 1.
435 state_retention_file=/var/lib/naemon/retention.dat
439 # RETENTION DATA UPDATE INTERVAL
440 # This setting determines how often (in minutes) that Naemon
441 # will automatically save retention data during normal operation.
442 # If you set this value to 0, Naemon will not save retention
443 # data at regular interval, but it will still save retention
444 # data before shutting down or restarting. If you have disabled
445 # state retention, this option has no effect.
447 retention_update_interval=60
451 # USE RETAINED PROGRAM STATE
452 # This setting determines whether or not Naemon will set
453 # program status variables based on the values saved in the
454 # retention file. If you want to use retained program status
455 # information, set this value to 1. If not, set this value
458 use_retained_program_state=1
462 # USE RETAINED SCHEDULING INFO
463 # This setting determines whether or not Naemon will retain
464 # the scheduling info (next check time) for hosts and services
465 # based on the values saved in the retention file. If you
466 # If you want to use retained scheduling info, set this
467 # value to 1. If not, set this value to 0.
469 use_retained_scheduling_info=1
473 # RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
474 # The following variables are used to specify specific host and
475 # service attributes that should *not* be retained by Naemon during
478 # The values of the masks are bitwise ANDs of values specified
479 # by the "MODATTR_" definitions found in include/common.h.
480 # For example, if you do not want the current enabled/disabled state
481 # of flap detection and event handlers for hosts to be retained, you
482 # would use a value of 24 for the host attribute mask...
483 # MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24
485 # This mask determines what host attributes are not retained
486 retained_host_attribute_mask=0
488 # This mask determines what service attributes are not retained
489 retained_service_attribute_mask=0
491 # These two masks determine what process attributes are not retained.
492 # There are two masks, because some process attributes have host and service
493 # options. For example, you can disable active host checks, but leave active
494 # service checks enabled.
495 retained_process_host_attribute_mask=0
496 retained_process_service_attribute_mask=0
498 # These two masks determine what contact attributes are not retained.
499 # There are two masks, because some contact attributes have host and
500 # service options. For example, you can disable host notifications for
501 # a contact, but leave service notifications enabled for them.
502 retained_contact_host_attribute_mask=0
503 retained_contact_service_attribute_mask=0
508 # This is the seconds per unit interval as used in the
509 # host/contact/service configuration files. Setting this to 60 means
510 # that each interval is one minute long (60 seconds). Other settings
511 # have not been tested much, so your mileage is likely to vary...
517 # AGGRESSIVE HOST CHECKING OPTION
518 # If you don't want to turn on aggressive host checking features, set
519 # this value to 0 (the default). Otherwise set this value to 1 to
520 # enable the aggressive check option. Read the docs for more info
521 # on what aggressive host check is or check out the source code in
524 use_aggressive_host_checking=0
528 # SERVICE CHECK EXECUTION OPTION
529 # This determines whether or not Naemon will actively execute
530 # service checks when it initially starts. If this option is
531 # disabled, checks are not actively made, but Naemon can still
532 # receive and process passive check results that come in. Unless
533 # you're implementing redundant hosts or have a special need for
534 # disabling the execution of service checks, leave this enabled!
535 # Values: 1 = enable checks, 0 = disable checks
537 execute_service_checks=1
541 # PASSIVE SERVICE CHECK ACCEPTANCE OPTION
542 # This determines whether or not Naemon will accept passive
543 # service checks results when it initially (re)starts.
544 # Values: 1 = accept passive checks, 0 = reject passive checks
546 accept_passive_service_checks=1
550 # HOST CHECK EXECUTION OPTION
551 # This determines whether or not Naemon will actively execute
552 # host checks when it initially starts. If this option is
553 # disabled, checks are not actively made, but Naemon can still
554 # receive and process passive check results that come in. Unless
555 # you're implementing redundant hosts or have a special need for
556 # disabling the execution of host checks, leave this enabled!
557 # Values: 1 = enable checks, 0 = disable checks
559 execute_host_checks=1
563 # PASSIVE HOST CHECK ACCEPTANCE OPTION
564 # This determines whether or not Naemon will accept passive
565 # host checks results when it initially (re)starts.
566 # Values: 1 = accept passive checks, 0 = reject passive checks
568 accept_passive_host_checks=1
572 # NOTIFICATIONS OPTION
573 # This determines whether or not Naemon will sent out any host or
574 # service notifications when it is initially (re)started.
575 # Values: 1 = enable notifications, 0 = disable notifications
577 enable_notifications=1
581 # EVENT HANDLER USE OPTION
582 # This determines whether or not Naemon will run any host or
583 # service event handlers when it is initially (re)started. Unless
584 # you're implementing redundant hosts, leave this option enabled.
585 # Values: 1 = enable event handlers, 0 = disable event handlers
587 enable_event_handlers=1
591 # PROCESS PERFORMANCE DATA OPTION
592 # This determines whether or not Naemon will process performance
593 # data returned from service and host checks. If this option is
594 # enabled, host performance data will be processed using the
595 # host_perfdata_command (defined below) and service performance
596 # data will be processed using the service_perfdata_command (also
597 # defined below). Read the HTML docs for more information on
599 # Values: 1 = process performance data, 0 = do not process performance data
601 process_performance_data=0
605 # HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
606 # These commands are run after every host and service check is
607 # performed. These commands are executed only if the
608 # enable_performance_data option (above) is set to 1. The command
609 # argument is the short name of a command definition that you
610 # define in your host configuration file. Read the HTML docs for
611 # more information on performance data.
613 #host_perfdata_command=process-host-perfdata
614 #service_perfdata_command=process-service-perfdata
618 # HOST AND SERVICE PERFORMANCE DATA FILES
619 # These files are used to store host and service performance data.
620 # Performance data is only written to these files if the
621 # enable_performance_data option (above) is set to 1.
623 #host_perfdata_file=/var/lib/naemon/host-perfdata
624 #service_perfdata_file=/var/lib/naemon/service-perfdata
628 # HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
629 # These options determine what data is written (and how) to the
630 # performance data files. The templates may contain macros, special
631 # characters (\t for tab, \r for carriage return, \n for newline)
632 # and plain text. A newline is automatically added after each write
633 # to the performance data file. Some examples of what you can do are
636 #host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
637 #service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
641 # HOST AND SERVICE PERFORMANCE DATA FILE MODES
642 # This option determines whether or not the host and service
643 # performance data files are opened in write ("w") or append ("a")
644 # mode. If you want to use named pipes, you should use the special
645 # pipe ("p") mode which avoid blocking at startup, otherwise you will
646 # likely want the defult append ("a") mode.
648 #host_perfdata_file_mode=a
649 #service_perfdata_file_mode=a
653 # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
654 # These options determine how often (in seconds) the host and service
655 # performance data files are processed using the commands defined
656 # below. A value of 0 indicates the files should not be periodically
659 #host_perfdata_file_processing_interval=0
660 #service_perfdata_file_processing_interval=0
664 # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
665 # These commands are used to periodically process the host and
666 # service performance data files. The interval at which the
667 # processing occurs is determined by the options above.
669 #host_perfdata_file_processing_command=process-host-perfdata-file
670 #service_perfdata_file_processing_command=process-service-perfdata-file
674 # HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS
675 # These options determine wether the core will process empty perfdata
676 # results or not. This is needed for distributed monitoring, and intentionally
677 # turned on by default.
678 # If you don't require empty perfdata - saving some cpu cycles
679 # on unwanted macro calculation - you can turn that off. Be careful!
680 # Values: 1 = enable, 0 = disable
682 #host_perfdata_process_empty_results=1
683 #service_perfdata_process_empty_results=1
686 # OBSESS OVER SERVICE CHECKS OPTION
687 # This determines whether or not Naemon will obsess over service
688 # checks and run the ocsp_command defined below. Unless you're
689 # planning on implementing distributed monitoring, do not enable
690 # this option. Read the HTML docs for more information on
691 # implementing distributed monitoring.
692 # Values: 1 = obsess over services, 0 = do not obsess (default)
694 obsess_over_services=<%= @naemon_url.nil? ? 0 : 1 %>
698 # OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
699 # This is the command that is run for every service check that is
700 # processed by Naemon. This command is executed only if the
701 # obsess_over_services option (above) is set to 1. The command
702 # argument is the short name of a command definition that you
703 # define in your host configuration file. Read the HTML docs for
704 # more information on implementing distributed monitoring.
706 <% if !@naemon_url.nil? %>
707 ocsp_command=notify-master
712 # OBSESS OVER HOST CHECKS OPTION
713 # This determines whether or not Naemon will obsess over host
714 # checks and run the ochp_command defined below. Unless you're
715 # planning on implementing distributed monitoring, do not enable
716 # this option. Read the HTML docs for more information on
717 # implementing distributed monitoring.
718 # Values: 1 = obsess over hosts, 0 = do not obsess (default)
724 # OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
725 # This is the command that is run for every host check that is
726 # processed by Naemon. This command is executed only if the
727 # obsess_over_hosts option (above) is set to 1. The command
728 # argument is the short name of a command definition that you
729 # define in your host configuration file. Read the HTML docs for
730 # more information on implementing distributed monitoring.
732 #ochp_command=somecommand
736 # TRANSLATE PASSIVE HOST CHECKS OPTION
737 # This determines whether or not Naemon will translate
738 # DOWN/UNREACHABLE passive host check results into their proper
739 # state for this instance of Naemon. This option is useful
740 # if you have distributed or failover monitoring setup. In
741 # these cases your other Naemon servers probably have a different
742 # "view" of the network, with regards to the parent/child relationship
743 # of hosts. If a distributed monitoring server thinks a host
744 # is DOWN, it may actually be UNREACHABLE from the point of
745 # this Naemon instance. Enabling this option will tell Naemon
746 # to translate any DOWN or UNREACHABLE host states it receives
747 # passively into the correct state from the view of this server.
748 # Values: 1 = perform translation, 0 = do not translate (default)
750 translate_passive_host_checks=0
754 # PASSIVE HOST CHECKS ARE SOFT OPTION
755 # This determines whether or not Naemon will treat passive host
756 # checks as being HARD or SOFT. By default, a passive host check
757 # result will put a host into a HARD state type. This can be changed
758 # by enabling this option.
759 # Values: 0 = passive checks are HARD, 1 = passive checks are SOFT
761 passive_host_checks_are_soft=0
765 # ORPHANED HOST/SERVICE CHECK OPTIONS
766 # These options determine whether or not Naemon will periodically
767 # check for orphaned host service checks. Since service checks are
768 # not rescheduled until the results of their previous execution
769 # instance are processed, there exists a possibility that some
770 # checks may never get rescheduled. A similar situation exists for
771 # host checks, although the exact scheduling details differ a bit
772 # from service checks. Orphaned checks seem to be a rare
773 # problem and should not happen under normal circumstances.
774 # If you have problems with service checks never getting
775 # rescheduled, make sure you have orphaned service checks enabled.
776 # Values: 1 = enable checks, 0 = disable checks
778 check_for_orphaned_services=1
779 check_for_orphaned_hosts=1
783 # SERVICE FRESHNESS CHECK OPTION
784 # This option determines whether or not Naemon will periodically
785 # check the "freshness" of service results. Enabling this option
786 # is useful for ensuring passive checks are received in a timely
788 # Values: 1 = enabled freshness checking, 0 = disable freshness checking
790 check_service_freshness=1
794 # SERVICE FRESHNESS CHECK INTERVAL
795 # This setting determines how often (in seconds) Naemon will
796 # check the "freshness" of service check results. If you have
797 # disabled service freshness checking, this option has no effect.
799 service_freshness_check_interval=60
803 # SERVICE CHECK TIMEOUT STATE
804 # This setting determines the state Naemon will report when a
805 # service check times out - that is does not respond within
806 # service_check_timeout seconds. This can be useful if a
807 # machine is running at too high a load and you do not want
808 # to consider a failed service check to be critical (the default).
809 # Valid settings are:
810 # c - Critical (default)
815 service_check_timeout_state=c
819 # HOST FRESHNESS CHECK OPTION
820 # This option determines whether or not Naemon will periodically
821 # check the "freshness" of host results. Enabling this option
822 # is useful for ensuring passive checks are received in a timely
824 # Values: 1 = enabled freshness checking, 0 = disable freshness checking
826 check_host_freshness=0
830 # HOST FRESHNESS CHECK INTERVAL
831 # This setting determines how often (in seconds) Naemon will
832 # check the "freshness" of host check results. If you have
833 # disabled host freshness checking, this option has no effect.
835 host_freshness_check_interval=60
840 # ADDITIONAL FRESHNESS THRESHOLD LATENCY
841 # This setting determines the number of seconds that Naemon
842 # will add to any host and service freshness thresholds that
843 # it calculates (those not explicitly specified by the user).
845 additional_freshness_latency=15
850 # FLAP DETECTION OPTION
851 # This option determines whether or not Naemon will try
852 # and detect hosts and services that are "flapping".
853 # Flapping occurs when a host or service changes between
854 # states too frequently. When Naemon detects that a
855 # host or service is flapping, it will temporarily suppress
856 # notifications for that host/service until it stops
857 # flapping. Flap detection is very experimental, so read
858 # the HTML documentation before enabling this feature!
859 # Values: 1 = enable flap detection
860 # 0 = disable flap detection (default)
862 enable_flap_detection=1
866 # FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
867 # Read the HTML documentation on flap detection for
868 # an explanation of what this option does. This option
869 # has no effect if flap detection is disabled.
871 low_service_flap_threshold=5.0
872 high_service_flap_threshold=20.0
873 low_host_flap_threshold=5.0
874 high_host_flap_threshold=20.0
879 # This option determines how short dates are displayed. Valid options
881 # us (MM-DD-YYYY HH:MM:SS)
882 # euro (DD-MM-YYYY HH:MM:SS)
883 # iso8601 (YYYY-MM-DD HH:MM:SS)
884 # strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
893 # This option is used to override the default timezone that this
894 # instance of Naemon runs in. If not specified, Naemon will use
895 # the system configured timezone.
897 #use_timezone=US/Mountain
898 #use_timezone=Australia/Brisbane
902 # ILLEGAL OBJECT NAME CHARACTERS
903 # This option allows you to specify illegal characters that cannot
904 # be used in host names, service descriptions, or names of other
907 illegal_object_name_chars=`~!$%^&*|'"<>?,()=
911 # ILLEGAL MACRO OUTPUT CHARACTERS
912 # This option allows you to specify illegal characters that are
913 # stripped from macros before being used in notifications, event
914 # handlers, etc. This DOES NOT affect macros used in service or
915 # host check commands.
916 # The following macros are stripped of the characters you specify:
924 # $SERVICEACKCOMMENT$
926 illegal_macro_output_chars=`~$&|'"<>
930 # REGULAR EXPRESSION MATCHING
931 # This option controls whether or not regular expression matching
932 # takes place in the object config files. Regular expression
933 # matching is used to match host, hostgroup, service, and service
934 # group names/descriptions in some fields of various object types.
935 # Values: 1 = enable regexp matching, 0 = disable regexp matching
937 use_regexp_matching=0
941 # "TRUE" REGULAR EXPRESSION MATCHING
942 # This option controls whether or not "true" regular expression
943 # matching takes place in the object config files. This option
944 # only has an effect if regular expression matching is enabled
945 # (see above). If this option is DISABLED, regular expression
946 # matching only occurs if a string contains wildcard characters
947 # (* and ?). If the option is ENABLED, regexp matching occurs
948 # all the time (which can be annoying).
949 # Values: 1 = enable true matching, 0 = disable true matching
951 use_true_regexp_matching=0
955 # ADMINISTRATOR EMAIL/PAGER ADDRESSES
956 # The email and pager address of a global administrator (likely you).
957 # Naemon never uses these values itself, but you can access them by
958 # using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
961 admin_email=naemon@localhost
962 admin_pager=pagenaemon@localhost
967 # This option determines how much (if any) debugging information will
968 # be written to the debug file. OR values together to log multiple
969 # types of information.
975 # 4 = Process information
976 # 8 = Scheduled events
977 # 16 = Host/service checks
980 # 128 = External commands
982 # 512 = Scheduled downtime
991 # This option determines how verbose the debug log out will be.
992 # Values: 0 = Brief output
1001 # This option determines where Naemon should write debugging information.
1003 debug_file=/var/lib/naemon/naemon.debug
1007 # MAX DEBUG FILE SIZE
1008 # This option determines the maximum size (in bytes) of the debug file. If
1009 # the file grows larger than this size, it will be renamed with a .old
1010 # extension. If a file already exists with a .old extension it will
1011 # automatically be deleted. This helps ensure your disk space usage doesn't
1012 # get out of control when debugging Naemon.
1014 max_debug_file_size=1000000
1018 # Should we allow hostgroups to have no hosts, we default this to off since
1019 # that was the old behavior
1021 allow_empty_hostgroup_assignment=0
1025 # Normally worker count is dynamically allocated based on 1.5 * number of cpu's
1026 # with a minimum of 4 workers. This value will override the defaults
1030 # CIRCULAR DEPENDENCIES (EXPERIMENTAL)
1031 # Allow for circular dependencies in naemon's host graph.
1032 # Enabaling this will cause propagation the following to stop working:
1033 # * scheduling downtime
1034 # * enabling notification
1035 # * disabling notification
1036 # This feature is experimental and bugs might occur.
1038 allow_circular_dependencies=0