1 ##############################################################################
3 # NAGIOS.CFG - Sample Main Config File for Nagios
6 ##############################################################################
10 # This is the main log file where service and host events are logged
11 # for historical purposes. This should be the first option specified
12 # in the config file!!!
14 log_file=/var/log/nagios3/nagios.log
16 # Commands definitions
17 cfg_file=/etc/nagios3/commands.cfg
19 # Debian also defaults to using the check commands defined by the debian
20 # nagios-plugins package
21 cfg_dir=/etc/nagios-plugins/config
23 # Debian uses by default a configuration directory where nagios3-common,
24 # other packages and the local admin can dump or link configuration
26 cfg_dir=/etc/nagios3/puppetconf.d
28 # OBJECT CONFIGURATION FILE(S)
29 # These are the object configuration files in which you define hosts,
30 # host groups, contacts, contact groups, services, etc.
31 # You can split your object definitions across several config files
32 # if you wish (as shown below), or keep them all in a single config file.
34 # You can specify individual object config files as shown below:
35 #cfg_file=/etc/nagios3/objects/commands.cfg
36 #cfg_file=/etc/nagios3/objects/contacts.cfg
37 #cfg_file=/etc/nagios3/objects/timeperiods.cfg
38 #cfg_file=/etc/nagios3/objects/templates.cfg
40 # Definitions for monitoring a Windows machine
41 #cfg_file=/etc/nagios3/objects/windows.cfg
43 # Definitions for monitoring a router/switch
44 #cfg_file=/etc/nagios3/objects/switch.cfg
46 # Definitions for monitoring a network printer
47 #cfg_file=/etc/nagios3/objects/printer.cfg
50 # You can also tell Nagios to process all config files (with a .cfg
51 # extension) in a particular directory by using the cfg_dir
52 # directive as shown below:
54 #cfg_dir=/etc/nagios3/servers
55 #cfg_dir=/etc/nagios3/printers
56 #cfg_dir=/etc/nagios3/switches
57 #cfg_dir=/etc/nagios3/routers
63 # This option determines where object definitions are cached when
64 # Nagios starts/restarts. The CGIs read object definitions from
65 # this cache file (rather than looking at the object config files
66 # directly) in order to prevent inconsistencies that can occur
67 # when the config files are modified after Nagios starts.
69 object_cache_file=/var/cache/nagios3/objects.cache
73 # PRE-CACHED OBJECT FILE
74 # This options determines the location of the precached object file.
75 # If you run Nagios with the -p command line option, it will preprocess
76 # your object configuration file(s) and write the cached config to this
77 # file. You can then start Nagios with the -u option to have it read
78 # object definitions from this precached file, rather than the standard
79 # object configuration files (see the cfg_file and cfg_dir options above).
80 # Using a precached object file can speed up the time needed to (re)start
81 # the Nagios process if you've got a large and/or complex configuration.
82 # Read the documentation section on optimizing Nagios to find our more
83 # about how this feature works.
85 precached_object_file=/var/lib/nagios3/objects.precache
90 # This is an optional resource file that contains $USERx$ macro
91 # definitions. Multiple resource files can be specified by using
92 # multiple resource_file definitions. The CGIs will not attempt to
93 # read the contents of resource files, so information that is
94 # considered to be sensitive (usernames, passwords, etc) can be
95 # defined as macros in this file and restrictive permissions (600)
96 # can be placed on this file.
98 resource_file=/etc/nagios3/resource.cfg
103 # This is where the current status of all monitored services and
104 # hosts is stored. Its contents are read and processed by the CGIs.
105 # The contents of the status file are deleted every time Nagios
108 status_file=/var/cache/nagios3/status.dat
112 # STATUS FILE UPDATE INTERVAL
113 # This option determines the frequency (in seconds) that
114 # Nagios will periodically dump program, host, and
115 # service status data.
117 status_update_interval=10
122 # This determines the effective user that Nagios should run as.
123 # You can either supply a username or a UID.
130 # This determines the effective group that Nagios should run as.
131 # You can either supply a group name or a GID.
137 # EXTERNAL COMMAND OPTION
138 # This option allows you to specify whether or not Nagios should check
139 # for external commands (in the command file defined below). By default
140 # Nagios will *not* check for external commands, just to be on the
141 # cautious side. If you want to be able to use the CGI command interface
142 # you will have to enable this.
143 # Values: 0 = disable commands, 1 = enable commands
145 check_external_commands=1
149 # EXTERNAL COMMAND CHECK INTERVAL
150 # This is the interval at which Nagios should check for external commands.
151 # This value works of the interval_length you specify later. If you leave
152 # that at its default value of 60 (seconds), a value of 1 here will cause
153 # Nagios to check for external commands every minute. If you specify a
154 # number followed by an "s" (i.e. 15s), this will be interpreted to mean
155 # actual seconds rather than a multiple of the interval_length variable.
156 # Note: In addition to reading the external command file at regularly
157 # scheduled intervals, Nagios will also check for external commands after
158 # event handlers are executed.
159 # NOTE: Setting this value to -1 causes Nagios to check the external
160 # command file as often as possible.
162 #command_check_interval=15s
163 command_check_interval=-1
167 # EXTERNAL COMMAND FILE
168 # This is the file that Nagios checks for external command requests.
169 # It is also where the command CGI will write commands that are submitted
170 # by users, so it must be writeable by the user that the web server
171 # is running as (usually 'nobody'). Permissions should be set at the
172 # directory level instead of on the file, as the file is deleted every
173 # time its contents are processed.
174 # Debian Users: In case you didn't read README.Debian yet, _NOW_ is the
177 command_file=/var/lib/nagios3/rw/nagios.cmd
181 # EXTERNAL COMMAND BUFFER SLOTS
182 # This settings is used to tweak the number of items or "slots" that
183 # the Nagios daemon should allocate to the buffer that holds incoming
184 # external commands before they are processed. As external commands
185 # are processed by the daemon, they are removed from the buffer.
187 external_command_buffer_slots=4096
192 # This is the lockfile that Nagios will use to store its PID number
193 # in when it is running in daemon mode.
195 lock_file=/var/run/nagios3/nagios3.pid
200 # This is a temporary file that is used as scratch space when Nagios
201 # updates the status log, cleans the comment file, etc. This file
202 # is created, used, and deleted throughout the time that Nagios is
205 temp_file=/var/cache/nagios3/nagios.tmp
210 # This is path where Nagios can create temp files for service and
211 # host check results, etc.
217 # EVENT BROKER OPTIONS
218 # Controls what (if any) data gets sent to the event broker.
219 # Values: 0 = Broker nothing
220 # -1 = Broker everything
221 # <other> = See documentation
223 event_broker_options=-1
227 # EVENT BROKER MODULE(S)
228 # This directive is used to specify an event broker module that should
229 # by loaded by Nagios at startup. Use multiple directives if you want
230 # to load more than one module. Arguments that should be passed to
231 # the module at startup are seperated from the module path by a space.
233 #!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
234 # WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING
235 #!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
237 # Do NOT overwrite modules while they are being used by Nagios or Nagios
238 # will crash in a fiery display of SEGFAULT glory. This is a bug/limitation
239 # either in dlopen(), the kernel, and/or the filesystem. And maybe Nagios...
241 # The correct/safe way of updating a module is by using one of these methods:
242 # 1. Shutdown Nagios, replace the module file, restart Nagios
243 # 2. Delete the original module file, move the new module file into place, restart Nagios
247 # broker_module=<modulepath> [moduleargs]
249 #broker_module=/somewhere/module1.o
250 #broker_module=/somewhere/module2.o arg1 arg2=3 debug=0
254 # LOG ROTATION METHOD
255 # This is the log rotation method that Nagios should use to rotate
256 # the main log file. Values are as follows..
257 # n = None - don't rotate the log
258 # h = Hourly rotation (top of the hour)
259 # d = Daily rotation (midnight every day)
260 # w = Weekly rotation (midnight on Saturday evening)
261 # m = Monthly rotation (midnight last day of month)
263 log_rotation_method=d
268 # This is the directory where archived (rotated) log files should be
269 # placed (assuming you've chosen to do log rotation).
271 log_archive_path=/var/log/nagios3/archives
276 # If you want messages logged to the syslog facility, as well as the
277 # Nagios log file set this option to 1. If not, set it to 0.
283 # NOTIFICATION LOGGING OPTION
284 # If you don't want notifications to be logged, set this value to 0.
285 # If notifications should be logged, set the value to 1.
291 # SERVICE RETRY LOGGING OPTION
292 # If you don't want service check retries to be logged, set this value
293 # to 0. If retries should be logged, set the value to 1.
295 log_service_retries=1
299 # HOST RETRY LOGGING OPTION
300 # If you don't want host check retries to be logged, set this value to
301 # 0. If retries should be logged, set the value to 1.
307 # EVENT HANDLER LOGGING OPTION
308 # If you don't want host and service event handlers to be logged, set
309 # this value to 0. If event handlers should be logged, set the value
316 # INITIAL STATES LOGGING OPTION
317 # If you want Nagios to log all initial host and service states to
318 # the main log file (the first time the service or host is checked)
319 # you can enable this option by setting this value to 1. If you
320 # are not using an external application that does long term state
321 # statistics reporting, you do not need to enable this option. In
322 # this case, set the value to 0.
328 # EXTERNAL COMMANDS LOGGING OPTION
329 # If you don't want Nagios to log external commands, set this value
330 # to 0. If external commands should be logged, set this value to 1.
331 # Note: This option does not include logging of passive service
332 # checks - see the option below for controlling whether or not
333 # passive checks are logged.
335 log_external_commands=1
339 # PASSIVE CHECKS LOGGING OPTION
340 # If you don't want Nagios to log passive host and service checks, set
341 # this value to 0. If passive checks should be logged, set
348 # GLOBAL HOST AND SERVICE EVENT HANDLERS
349 # These options allow you to specify a host and service event handler
350 # command that is to be run for every host or service state change.
351 # The global event handler is executed immediately prior to the event
352 # handler that you have optionally specified in each host or
353 # service definition. The command argument is the short name of a
354 # command definition that you define in your host configuration file.
355 # Read the HTML docs for more information.
357 #global_host_event_handler=somecommand
358 #global_service_event_handler=somecommand
362 # SERVICE INTER-CHECK DELAY METHOD
363 # This is the method that Nagios should use when initially
364 # "spreading out" service checks when it starts monitoring. The
365 # default is to use smart delay calculation, which will try to
366 # space all service checks out evenly to minimize CPU load.
367 # Using the dumb setting will cause all checks to be scheduled
368 # at the same time (with no delay between them)! This is not a
369 # good thing for production, but is useful when testing the
370 # parallelization functionality.
371 # n = None - don't use any delay between checks
372 # d = Use a "dumb" delay of 1 second between checks
373 # s = Use "smart" inter-check delay calculation
374 # x.xx = Use an inter-check delay of x.xx seconds
376 service_inter_check_delay_method=s
380 # MAXIMUM SERVICE CHECK SPREAD
381 # This variable determines the timeframe (in minutes) from the
382 # program start time that an initial check of all services should
383 # be completed. Default is 30 minutes.
385 max_service_check_spread=30
389 # SERVICE CHECK INTERLEAVE FACTOR
390 # This variable determines how service checks are interleaved.
391 # Interleaving the service checks allows for a more even
392 # distribution of service checks and reduced load on remote
393 # hosts. Setting this value to 1 is equivalent to how versions
394 # of Nagios previous to 0.0.5 did service checks. Set this
395 # value to s (smart) for automatic calculation of the interleave
396 # factor unless you have a specific reason to change it.
397 # s = Use "smart" interleave factor calculation
398 # x = Use an interleave factor of x, where x is a
399 # number greater than or equal to 1.
401 service_interleave_factor=s
405 # HOST INTER-CHECK DELAY METHOD
406 # This is the method that Nagios should use when initially
407 # "spreading out" host checks when it starts monitoring. The
408 # default is to use smart delay calculation, which will try to
409 # space all host checks out evenly to minimize CPU load.
410 # Using the dumb setting will cause all checks to be scheduled
411 # at the same time (with no delay between them)!
412 # n = None - don't use any delay between checks
413 # d = Use a "dumb" delay of 1 second between checks
414 # s = Use "smart" inter-check delay calculation
415 # x.xx = Use an inter-check delay of x.xx seconds
417 host_inter_check_delay_method=s
421 # MAXIMUM HOST CHECK SPREAD
422 # This variable determines the timeframe (in minutes) from the
423 # program start time that an initial check of all hosts should
424 # be completed. Default is 30 minutes.
426 max_host_check_spread=30
430 # MAXIMUM CONCURRENT SERVICE CHECKS
431 # This option allows you to specify the maximum number of
432 # service checks that can be run in parallel at any given time.
433 # Specifying a value of 1 for this variable essentially prevents
434 # any service checks from being parallelized. A value of 0
435 # will not restrict the number of concurrent checks that are
438 max_concurrent_checks=0
442 # HOST AND SERVICE CHECK REAPER FREQUENCY
443 # This is the frequency (in seconds!) that Nagios will process
444 # the results of host and service checks.
446 check_result_reaper_frequency=10
451 # MAX CHECK RESULT REAPER TIME
452 # This is the max amount of time (in seconds) that a single
453 # check result reaper event will be allowed to run before
454 # returning control back to Nagios so it can perform other
457 max_check_result_reaper_time=30
463 # This is directory where Nagios stores the results of host and
464 # service checks that have not yet been processed.
466 # Note: Make sure that only one instance of Nagios has access
469 check_result_path=/var/lib/nagios3/spool/checkresults
474 # MAX CHECK RESULT FILE AGE
475 # This option determines the maximum age (in seconds) which check
476 # result files are considered to be valid. Files older than this
477 # threshold will be mercilessly deleted without further processing.
479 max_check_result_file_age=3600
484 # CACHED HOST CHECK HORIZON
485 # This option determines the maximum amount of time (in seconds)
486 # that the state of a previous host check is considered current.
487 # Cached host states (from host checks that were performed more
488 # recently that the timeframe specified by this value) can immensely
489 # improve performance in regards to the host check logic.
490 # Too high of a value for this option may result in inaccurate host
491 # states being used by Nagios, while a lower value may result in a
492 # performance hit for host checks. Use a value of 0 to disable host
495 cached_host_check_horizon=15
499 # CACHED SERVICE CHECK HORIZON
500 # This option determines the maximum amount of time (in seconds)
501 # that the state of a previous service check is considered current.
502 # Cached service states (from service checks that were performed more
503 # recently that the timeframe specified by this value) can immensely
504 # improve performance in regards to predictive dependency checks.
505 # Use a value of 0 to disable service check caching.
507 cached_service_check_horizon=15
511 # ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
512 # This option determines whether or not Nagios will attempt to execute
513 # checks of hosts when it predicts that future dependency logic test
514 # may be needed. These predictive checks can help ensure that your
515 # host dependency logic works well.
517 # 0 = Disable predictive checks
518 # 1 = Enable predictive checks (default)
520 enable_predictive_host_dependency_checks=1
524 # ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
525 # This option determines whether or not Nagios will attempt to execute
526 # checks of service when it predicts that future dependency logic test
527 # may be needed. These predictive checks can help ensure that your
528 # service dependency logic works well.
530 # 0 = Disable predictive checks
531 # 1 = Enable predictive checks (default)
533 enable_predictive_service_dependency_checks=1
537 # SOFT STATE DEPENDENCIES
538 # This option determines whether or not Nagios will use soft state
539 # information when checking host and service dependencies. Normally
540 # Nagios will only use the latest hard host or service state when
541 # checking dependencies. If you want it to use the latest state (regardless
542 # of whether its a soft or hard state type), enable this option.
544 # 0 = Don't use soft state dependencies (default)
545 # 1 = Use soft state dependencies
547 soft_state_dependencies=0
551 # TIME CHANGE ADJUSTMENT THRESHOLDS
552 # These options determine when Nagios will react to detected changes
553 # in system time (either forward or backwards).
555 #time_change_threshold=900
559 # AUTO-RESCHEDULING OPTION
560 # This option determines whether or not Nagios will attempt to
561 # automatically reschedule active host and service checks to
562 # "smooth" them out over time. This can help balance the load on
563 # the monitoring server.
564 # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
565 # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
567 auto_reschedule_checks=0
571 # AUTO-RESCHEDULING INTERVAL
572 # This option determines how often (in seconds) Nagios will
573 # attempt to automatically reschedule checks. This option only
574 # has an effect if the auto_reschedule_checks option is enabled.
575 # Default is 30 seconds.
576 # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
577 # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
579 auto_rescheduling_interval=30
583 # AUTO-RESCHEDULING WINDOW
584 # This option determines the "window" of time (in seconds) that
585 # Nagios will look at when automatically rescheduling checks.
586 # Only host and service checks that occur in the next X seconds
587 # (determined by this variable) will be rescheduled. This option
588 # only has an effect if the auto_reschedule_checks option is
589 # enabled. Default is 180 seconds (3 minutes).
590 # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
591 # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
593 auto_rescheduling_window=180
598 # This is the number of seconds to sleep between checking for system
599 # events and service checks that need to be run.
606 # These options control how much time Nagios will allow various
607 # types of commands to execute before killing them off. Options
608 # are available for controlling maximum time allotted for
609 # service checks, host checks, event handlers, notifications, the
610 # ocsp command, and performance data commands. All values are in
613 service_check_timeout=60
614 host_check_timeout=30
615 event_handler_timeout=30
616 notification_timeout=30
622 # RETAIN STATE INFORMATION
623 # This setting determines whether or not Nagios will save state
624 # information for services and hosts before it shuts down. Upon
625 # startup Nagios will reload all saved service and host state
626 # information before starting to monitor. This is useful for
627 # maintaining long-term data on state statistics, etc, but will
628 # slow Nagios down a bit when it (re)starts. Since its only
629 # a one-time penalty, I think its well worth the additional
632 retain_state_information=1
636 # STATE RETENTION FILE
637 # This is the file that Nagios should use to store host and
638 # service state information before it shuts down. The state
639 # information in this file is also read immediately prior to
640 # starting to monitor the network when Nagios is restarted.
641 # This file is used only if the preserve_state_information
642 # variable is set to 1.
644 state_retention_file=/var/lib/nagios3/retention.dat
648 # RETENTION DATA UPDATE INTERVAL
649 # This setting determines how often (in minutes) that Nagios
650 # will automatically save retention data during normal operation.
651 # If you set this value to 0, Nagios will not save retention
652 # data at regular interval, but it will still save retention
653 # data before shutting down or restarting. If you have disabled
654 # state retention, this option has no effect.
656 retention_update_interval=60
660 # USE RETAINED PROGRAM STATE
661 # This setting determines whether or not Nagios will set
662 # program status variables based on the values saved in the
663 # retention file. If you want to use retained program status
664 # information, set this value to 1. If not, set this value
667 use_retained_program_state=1
671 # USE RETAINED SCHEDULING INFO
672 # This setting determines whether or not Nagios will retain
673 # the scheduling info (next check time) for hosts and services
674 # based on the values saved in the retention file. If you
675 # If you want to use retained scheduling info, set this
676 # value to 1. If not, set this value to 0.
678 use_retained_scheduling_info=1
682 # RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
683 # The following variables are used to specify specific host and
684 # service attributes that should *not* be retained by Nagios during
687 # The values of the masks are bitwise ANDs of values specified
688 # by the "MODATTR_" definitions found in include/common.h.
689 # For example, if you do not want the current enabled/disabled state
690 # of flap detection and event handlers for hosts to be retained, you
691 # would use a value of 24 for the host attribute mask...
692 # MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24
694 # This mask determines what host attributes are not retained
695 retained_host_attribute_mask=0
697 # This mask determines what service attributes are not retained
698 retained_service_attribute_mask=0
700 # These two masks determine what process attributes are not retained.
701 # There are two masks, because some process attributes have host and service
702 # options. For example, you can disable active host checks, but leave active
703 # service checks enabled.
704 retained_process_host_attribute_mask=0
705 retained_process_service_attribute_mask=0
707 # These two masks determine what contact attributes are not retained.
708 # There are two masks, because some contact attributes have host and
709 # service options. For example, you can disable host notifications for
710 # a contact, but leave service notifications enabled for them.
711 retained_contact_host_attribute_mask=0
712 retained_contact_service_attribute_mask=0
717 # This is the seconds per unit interval as used in the
718 # host/contact/service configuration files. Setting this to 60 means
719 # that each interval is one minute long (60 seconds). Other settings
720 # have not been tested much, so your mileage is likely to vary...
726 # AGGRESSIVE HOST CHECKING OPTION
727 # If you don't want to turn on aggressive host checking features, set
728 # this value to 0 (the default). Otherwise set this value to 1 to
729 # enable the aggressive check option. Read the docs for more info
730 # on what aggressive host check is or check out the source code in
733 use_aggressive_host_checking=0
737 # SERVICE CHECK EXECUTION OPTION
738 # This determines whether or not Nagios will actively execute
739 # service checks when it initially starts. If this option is
740 # disabled, checks are not actively made, but Nagios can still
741 # receive and process passive check results that come in. Unless
742 # you're implementing redundant hosts or have a special need for
743 # disabling the execution of service checks, leave this enabled!
744 # Values: 1 = enable checks, 0 = disable checks
746 execute_service_checks=1
750 # PASSIVE SERVICE CHECK ACCEPTANCE OPTION
751 # This determines whether or not Nagios will accept passive
752 # service checks results when it initially (re)starts.
753 # Values: 1 = accept passive checks, 0 = reject passive checks
755 accept_passive_service_checks=1
759 # HOST CHECK EXECUTION OPTION
760 # This determines whether or not Nagios will actively execute
761 # host checks when it initially starts. If this option is
762 # disabled, checks are not actively made, but Nagios can still
763 # receive and process passive check results that come in. Unless
764 # you're implementing redundant hosts or have a special need for
765 # disabling the execution of host checks, leave this enabled!
766 # Values: 1 = enable checks, 0 = disable checks
768 execute_host_checks=1
772 # PASSIVE HOST CHECK ACCEPTANCE OPTION
773 # This determines whether or not Nagios will accept passive
774 # host checks results when it initially (re)starts.
775 # Values: 1 = accept passive checks, 0 = reject passive checks
777 accept_passive_host_checks=1
781 # NOTIFICATIONS OPTION
782 # This determines whether or not Nagios will sent out any host or
783 # service notifications when it is initially (re)started.
784 # Values: 1 = enable notifications, 0 = disable notifications
786 enable_notifications=1
790 # EVENT HANDLER USE OPTION
791 # This determines whether or not Nagios will run any host or
792 # service event handlers when it is initially (re)started. Unless
793 # you're implementing redundant hosts, leave this option enabled.
794 # Values: 1 = enable event handlers, 0 = disable event handlers
796 enable_event_handlers=1
800 # PROCESS PERFORMANCE DATA OPTION
801 # This determines whether or not Nagios will process performance
802 # data returned from service and host checks. If this option is
803 # enabled, host performance data will be processed using the
804 # host_perfdata_command (defined below) and service performance
805 # data will be processed using the service_perfdata_command (also
806 # defined below). Read the HTML docs for more information on
808 # Values: 1 = process performance data, 0 = do not process performance data
810 process_performance_data=0
814 # HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
815 # These commands are run after every host and service check is
816 # performed. These commands are executed only if the
817 # enable_performance_data option (above) is set to 1. The command
818 # argument is the short name of a command definition that you
819 # define in your host configuration file. Read the HTML docs for
820 # more information on performance data.
822 #host_perfdata_command=process-host-perfdata
823 #service_perfdata_command=process-service-perfdata
827 # HOST AND SERVICE PERFORMANCE DATA FILES
828 # These files are used to store host and service performance data.
829 # Performance data is only written to these files if the
830 # enable_performance_data option (above) is set to 1.
832 #host_perfdata_file=/tmp/host-perfdata
833 #service_perfdata_file=/tmp/service-perfdata
837 # HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
838 # These options determine what data is written (and how) to the
839 # performance data files. The templates may contain macros, special
840 # characters (\t for tab, \r for carriage return, \n for newline)
841 # and plain text. A newline is automatically added after each write
842 # to the performance data file. Some examples of what you can do are
845 #host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
846 #service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
850 # HOST AND SERVICE PERFORMANCE DATA FILE MODES
851 # This option determines whether or not the host and service
852 # performance data files are opened in write ("w") or append ("a")
853 # mode. If you want to use named pipes, you should use the special
854 # pipe ("p") mode which avoid blocking at startup, otherwise you will
855 # likely want the defult append ("a") mode.
857 #host_perfdata_file_mode=a
858 #service_perfdata_file_mode=a
862 # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
863 # These options determine how often (in seconds) the host and service
864 # performance data files are processed using the commands defined
865 # below. A value of 0 indicates the files should not be periodically
868 #host_perfdata_file_processing_interval=0
869 #service_perfdata_file_processing_interval=0
873 # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
874 # These commands are used to periodically process the host and
875 # service performance data files. The interval at which the
876 # processing occurs is determined by the options above.
878 #host_perfdata_file_processing_command=process-host-perfdata-file
879 #service_perfdata_file_processing_command=process-service-perfdata-file
883 # OBSESS OVER SERVICE CHECKS OPTION
884 # This determines whether or not Nagios will obsess over service
885 # checks and run the ocsp_command defined below. Unless you're
886 # planning on implementing distributed monitoring, do not enable
887 # this option. Read the HTML docs for more information on
888 # implementing distributed monitoring.
889 # Values: 1 = obsess over services, 0 = do not obsess (default)
891 obsess_over_services=0
895 # OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
896 # This is the command that is run for every service check that is
897 # processed by Nagios. This command is executed only if the
898 # obsess_over_services option (above) is set to 1. The command
899 # argument is the short name of a command definition that you
900 # define in your host configuration file. Read the HTML docs for
901 # more information on implementing distributed monitoring.
903 #ocsp_command=somecommand
907 # OBSESS OVER HOST CHECKS OPTION
908 # This determines whether or not Nagios will obsess over host
909 # checks and run the ochp_command defined below. Unless you're
910 # planning on implementing distributed monitoring, do not enable
911 # this option. Read the HTML docs for more information on
912 # implementing distributed monitoring.
913 # Values: 1 = obsess over hosts, 0 = do not obsess (default)
919 # OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
920 # This is the command that is run for every host check that is
921 # processed by Nagios. This command is executed only if the
922 # obsess_over_hosts option (above) is set to 1. The command
923 # argument is the short name of a command definition that you
924 # define in your host configuration file. Read the HTML docs for
925 # more information on implementing distributed monitoring.
927 #ochp_command=somecommand
931 # TRANSLATE PASSIVE HOST CHECKS OPTION
932 # This determines whether or not Nagios will translate
933 # DOWN/UNREACHABLE passive host check results into their proper
934 # state for this instance of Nagios. This option is useful
935 # if you have distributed or failover monitoring setup. In
936 # these cases your other Nagios servers probably have a different
937 # "view" of the network, with regards to the parent/child relationship
938 # of hosts. If a distributed monitoring server thinks a host
939 # is DOWN, it may actually be UNREACHABLE from the point of
940 # this Nagios instance. Enabling this option will tell Nagios
941 # to translate any DOWN or UNREACHABLE host states it receives
942 # passively into the correct state from the view of this server.
943 # Values: 1 = perform translation, 0 = do not translate (default)
945 translate_passive_host_checks=0
949 # PASSIVE HOST CHECKS ARE SOFT OPTION
950 # This determines whether or not Nagios will treat passive host
951 # checks as being HARD or SOFT. By default, a passive host check
952 # result will put a host into a HARD state type. This can be changed
953 # by enabling this option.
954 # Values: 0 = passive checks are HARD, 1 = passive checks are SOFT
956 passive_host_checks_are_soft=0
960 # ORPHANED HOST/SERVICE CHECK OPTIONS
961 # These options determine whether or not Nagios will periodically
962 # check for orphaned host service checks. Since service checks are
963 # not rescheduled until the results of their previous execution
964 # instance are processed, there exists a possibility that some
965 # checks may never get rescheduled. A similar situation exists for
966 # host checks, although the exact scheduling details differ a bit
967 # from service checks. Orphaned checks seem to be a rare
968 # problem and should not happen under normal circumstances.
969 # If you have problems with service checks never getting
970 # rescheduled, make sure you have orphaned service checks enabled.
971 # Values: 1 = enable checks, 0 = disable checks
973 check_for_orphaned_services=1
974 check_for_orphaned_hosts=1
978 # SERVICE FRESHNESS CHECK OPTION
979 # This option determines whether or not Nagios will periodically
980 # check the "freshness" of service results. Enabling this option
981 # is useful for ensuring passive checks are received in a timely
983 # Values: 1 = enabled freshness checking, 0 = disable freshness checking
985 check_service_freshness=1
989 # SERVICE FRESHNESS CHECK INTERVAL
990 # This setting determines how often (in seconds) Nagios will
991 # check the "freshness" of service check results. If you have
992 # disabled service freshness checking, this option has no effect.
994 service_freshness_check_interval=60
998 # HOST FRESHNESS CHECK OPTION
999 # This option determines whether or not Nagios will periodically
1000 # check the "freshness" of host results. Enabling this option
1001 # is useful for ensuring passive checks are received in a timely
1003 # Values: 1 = enabled freshness checking, 0 = disable freshness checking
1005 check_host_freshness=0
1009 # HOST FRESHNESS CHECK INTERVAL
1010 # This setting determines how often (in seconds) Nagios will
1011 # check the "freshness" of host check results. If you have
1012 # disabled host freshness checking, this option has no effect.
1014 host_freshness_check_interval=60
1019 # ADDITIONAL FRESHNESS THRESHOLD LATENCY
1020 # This setting determines the number of seconds that Nagios
1021 # will add to any host and service freshness thresholds that
1022 # it calculates (those not explicitly specified by the user).
1024 additional_freshness_latency=15
1029 # FLAP DETECTION OPTION
1030 # This option determines whether or not Nagios will try
1031 # and detect hosts and services that are "flapping".
1032 # Flapping occurs when a host or service changes between
1033 # states too frequently. When Nagios detects that a
1034 # host or service is flapping, it will temporarily suppress
1035 # notifications for that host/service until it stops
1036 # flapping. Flap detection is very experimental, so read
1037 # the HTML documentation before enabling this feature!
1038 # Values: 1 = enable flap detection
1039 # 0 = disable flap detection (default)
1041 enable_flap_detection=1
1045 # FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
1046 # Read the HTML documentation on flap detection for
1047 # an explanation of what this option does. This option
1048 # has no effect if flap detection is disabled.
1050 low_service_flap_threshold=5.0
1051 high_service_flap_threshold=20.0
1052 low_host_flap_threshold=5.0
1053 high_host_flap_threshold=20.0
1057 # DATE FORMAT OPTION
1058 # This option determines how short dates are displayed. Valid options
1060 # us (MM-DD-YYYY HH:MM:SS)
1061 # euro (DD-MM-YYYY HH:MM:SS)
1062 # iso8601 (YYYY-MM-DD HH:MM:SS)
1063 # strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
1072 # This option is used to override the default timezone that this
1073 # instance of Nagios runs in. If not specified, Nagios will use
1074 # the system configured timezone.
1076 # NOTE: In order to display the correct timezone in the CGIs, you
1077 # will also need to alter the Apache directives for the CGI path
1078 # to include your timezone. Example:
1080 # <Directory "/usr/local/nagios/sbin/">
1081 # SetEnv TZ "Australia/Brisbane"
1085 #use_timezone=US/Mountain
1086 #use_timezone=Australia/Brisbane
1091 # P1.PL FILE LOCATION
1092 # This value determines where the p1.pl perl script (used by the
1093 # embedded Perl interpreter) is located. If you didn't compile
1094 # Nagios with embedded Perl support, this option has no effect.
1096 p1_file=/usr/lib/nagios3/p1.pl
1100 # EMBEDDED PERL INTERPRETER OPTION
1101 # This option determines whether or not the embedded Perl interpreter
1102 # will be enabled during runtime. This option has no effect if Nagios
1103 # has not been compiled with support for embedded Perl.
1104 # Values: 0 = disable interpreter, 1 = enable interpreter
1106 enable_embedded_perl=1
1110 # EMBEDDED PERL USAGE OPTION
1111 # This option determines whether or not Nagios will process Perl plugins
1112 # and scripts with the embedded Perl interpreter if the plugins/scripts
1113 # do not explicitly indicate whether or not it is okay to do so. Read
1114 # the HTML documentation on the embedded Perl interpreter for more
1115 # information on how this option works.
1117 use_embedded_perl_implicitly=1
1121 # ILLEGAL OBJECT NAME CHARACTERS
1122 # This option allows you to specify illegal characters that cannot
1123 # be used in host names, service descriptions, or names of other
1126 illegal_object_name_chars=`~!$%^&*|'"<>?,()=
1130 # ILLEGAL MACRO OUTPUT CHARACTERS
1131 # This option allows you to specify illegal characters that are
1132 # stripped from macros before being used in notifications, event
1133 # handlers, etc. This DOES NOT affect macros used in service or
1134 # host check commands.
1135 # The following macros are stripped of the characters you specify:
1142 # $SERVICEACKAUTHOR$
1143 # $SERVICEACKCOMMENT$
1145 illegal_macro_output_chars=`~$&|'"<>
1149 # REGULAR EXPRESSION MATCHING
1150 # This option controls whether or not regular expression matching
1151 # takes place in the object config files. Regular expression
1152 # matching is used to match host, hostgroup, service, and service
1153 # group names/descriptions in some fields of various object types.
1154 # Values: 1 = enable regexp matching, 0 = disable regexp matching
1156 use_regexp_matching=0
1160 # "TRUE" REGULAR EXPRESSION MATCHING
1161 # This option controls whether or not "true" regular expression
1162 # matching takes place in the object config files. This option
1163 # only has an effect if regular expression matching is enabled
1164 # (see above). If this option is DISABLED, regular expression
1165 # matching only occurs if a string contains wildcard characters
1166 # (* and ?). If the option is ENABLED, regexp matching occurs
1167 # all the time (which can be annoying).
1168 # Values: 1 = enable true matching, 0 = disable true matching
1170 use_true_regexp_matching=0
1174 # ADMINISTRATOR EMAIL/PAGER ADDRESSES
1175 # The email and pager address of a global administrator (likely you).
1176 # Nagios never uses these values itself, but you can access them by
1177 # using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
1180 admin_email=root@localhost
1181 admin_pager=pageroot@localhost
1185 # DAEMON CORE DUMP OPTION
1186 # This option determines whether or not Nagios is allowed to create
1187 # a core dump when it runs as a daemon. Note that it is generally
1188 # considered bad form to allow this, but it may be useful for
1189 # debugging purposes. Enabling this option doesn't guarantee that
1190 # a core file will be produced, but that's just life...
1191 # Values: 1 - Allow core dumps
1192 # 0 - Do not allow core dumps (default)
1198 # LARGE INSTALLATION TWEAKS OPTION
1199 # This option determines whether or not Nagios will take some shortcuts
1200 # which can save on memory and CPU usage in large Nagios installations.
1201 # Read the documentation for more information on the benefits/tradeoffs
1202 # of enabling this option.
1203 # Values: 1 - Enabled tweaks
1204 # 0 - Disable tweaks (default)
1206 use_large_installation_tweaks=0
1210 # ENABLE ENVIRONMENT MACROS
1211 # This option determines whether or not Nagios will make all standard
1212 # macros available as environment variables when host/service checks
1213 # and system commands (event handlers, notifications, etc.) are
1214 # executed. Enabling this option can cause performance issues in
1215 # large installations, as it will consume a bit more memory and (more
1216 # importantly) consume more CPU.
1217 # Values: 1 - Enable environment variable macros (default)
1218 # 0 - Disable environment variable macros
1220 enable_environment_macros=1
1224 # CHILD PROCESS MEMORY OPTION
1225 # This option determines whether or not Nagios will free memory in
1226 # child processes (processed used to execute system commands and host/
1227 # service checks). If you specify a value here, it will override
1229 # Value: 1 - Free memory in child processes
1230 # 0 - Do not free memory in child processes
1232 #free_child_process_memory=1
1236 # CHILD PROCESS FORKING BEHAVIOR
1237 # This option determines how Nagios will fork child processes
1238 # (used to execute system commands and host/service checks). Normally
1239 # child processes are fork()ed twice, which provides a very high level
1240 # of isolation from problems. Fork()ing once is probably enough and will
1241 # save a great deal on CPU usage (in large installs), so you might
1242 # want to consider using this. If you specify a value here, it will
1244 # Value: 1 - Child processes fork() twice
1245 # 0 - Child processes fork() just once
1247 #child_processes_fork_twice=1
1252 # This option determines how much (if any) debugging information will
1253 # be written to the debug file. OR values together to log multiple
1254 # types of information.
1260 # 4 = Process information
1261 # 8 = Scheduled events
1262 # 16 = Host/service checks
1263 # 32 = Notifications
1265 # 128 = External commands
1267 # 512 = Scheduled downtime
1276 # This option determines how verbose the debug log out will be.
1277 # Values: 0 = Brief output
1286 # This option determines where Nagios should write debugging information.
1288 debug_file=/var/lib/nagios3/nagios.debug
1292 # MAX DEBUG FILE SIZE
1293 # This option determines the maximum size (in bytes) of the debug file. If
1294 # the file grows larger than this size, it will be renamed with a .old
1295 # extension. If a file already exists with a .old extension it will
1296 # automatically be deleted. This helps ensure your disk space usage doesn't
1297 # get out of control when debugging Nagios.
1299 max_debug_file_size=1000000