1 #############################################################################
2 ## THIS FILE IS COPIED TO THE FINAL LOCATION USING PUPPET
3 ## ITS AUTHORITATIVE HOME IS THE DSA-NAGIOS CONFIGURATION GIT
4 #############################################################################
6 ##############################################################################
8 # NAGIOS.CFG - Sample Main Config File for Nagios
11 ##############################################################################
15 # This is the main log file where service and host events are logged
16 # for historical purposes. This should be the first option specified
17 # in the config file!!!
19 log_file=/var/log/nagios3/nagios.log
21 # Commands definitions
22 cfg_file=/etc/nagios3/commands.cfg
24 # Debian also defaults to using the check commands defined by the debian
25 # nagios-plugins package
26 cfg_dir=/etc/nagios-plugins/config
28 # Debian uses by default a configuration directory where nagios3-common,
29 # other packages and the local admin can dump or link configuration
31 cfg_dir=/etc/nagios3/puppetconf.d
33 # OBJECT CONFIGURATION FILE(S)
34 # These are the object configuration files in which you define hosts,
35 # host groups, contacts, contact groups, services, etc.
36 # You can split your object definitions across several config files
37 # if you wish (as shown below), or keep them all in a single config file.
39 # You can specify individual object config files as shown below:
40 #cfg_file=/etc/nagios3/objects/commands.cfg
41 #cfg_file=/etc/nagios3/objects/contacts.cfg
42 #cfg_file=/etc/nagios3/objects/timeperiods.cfg
43 #cfg_file=/etc/nagios3/objects/templates.cfg
45 # Definitions for monitoring a Windows machine
46 #cfg_file=/etc/nagios3/objects/windows.cfg
48 # Definitions for monitoring a router/switch
49 #cfg_file=/etc/nagios3/objects/switch.cfg
51 # Definitions for monitoring a network printer
52 #cfg_file=/etc/nagios3/objects/printer.cfg
55 # You can also tell Nagios to process all config files (with a .cfg
56 # extension) in a particular directory by using the cfg_dir
57 # directive as shown below:
59 #cfg_dir=/etc/nagios3/servers
60 #cfg_dir=/etc/nagios3/printers
61 #cfg_dir=/etc/nagios3/switches
62 #cfg_dir=/etc/nagios3/routers
68 # This option determines where object definitions are cached when
69 # Nagios starts/restarts. The CGIs read object definitions from
70 # this cache file (rather than looking at the object config files
71 # directly) in order to prevent inconsistencies that can occur
72 # when the config files are modified after Nagios starts.
74 object_cache_file=/var/cache/nagios3/objects.cache
78 # PRE-CACHED OBJECT FILE
79 # This options determines the location of the precached object file.
80 # If you run Nagios with the -p command line option, it will preprocess
81 # your object configuration file(s) and write the cached config to this
82 # file. You can then start Nagios with the -u option to have it read
83 # object definitions from this precached file, rather than the standard
84 # object configuration files (see the cfg_file and cfg_dir options above).
85 # Using a precached object file can speed up the time needed to (re)start
86 # the Nagios process if you've got a large and/or complex configuration.
87 # Read the documentation section on optimizing Nagios to find our more
88 # about how this feature works.
90 precached_object_file=/var/lib/nagios3/objects.precache
95 # This is an optional resource file that contains $USERx$ macro
96 # definitions. Multiple resource files can be specified by using
97 # multiple resource_file definitions. The CGIs will not attempt to
98 # read the contents of resource files, so information that is
99 # considered to be sensitive (usernames, passwords, etc) can be
100 # defined as macros in this file and restrictive permissions (600)
101 # can be placed on this file.
103 resource_file=/etc/nagios3/resource.cfg
108 # This is where the current status of all monitored services and
109 # hosts is stored. Its contents are read and processed by the CGIs.
110 # The contents of the status file are deleted every time Nagios
113 status_file=/var/cache/nagios3/status.dat
117 # STATUS FILE UPDATE INTERVAL
118 # This option determines the frequency (in seconds) that
119 # Nagios will periodically dump program, host, and
120 # service status data.
122 status_update_interval=10
127 # This determines the effective user that Nagios should run as.
128 # You can either supply a username or a UID.
135 # This determines the effective group that Nagios should run as.
136 # You can either supply a group name or a GID.
142 # EXTERNAL COMMAND OPTION
143 # This option allows you to specify whether or not Nagios should check
144 # for external commands (in the command file defined below). By default
145 # Nagios will *not* check for external commands, just to be on the
146 # cautious side. If you want to be able to use the CGI command interface
147 # you will have to enable this.
148 # Values: 0 = disable commands, 1 = enable commands
150 check_external_commands=1
154 # EXTERNAL COMMAND CHECK INTERVAL
155 # This is the interval at which Nagios should check for external commands.
156 # This value works of the interval_length you specify later. If you leave
157 # that at its default value of 60 (seconds), a value of 1 here will cause
158 # Nagios to check for external commands every minute. If you specify a
159 # number followed by an "s" (i.e. 15s), this will be interpreted to mean
160 # actual seconds rather than a multiple of the interval_length variable.
161 # Note: In addition to reading the external command file at regularly
162 # scheduled intervals, Nagios will also check for external commands after
163 # event handlers are executed.
164 # NOTE: Setting this value to -1 causes Nagios to check the external
165 # command file as often as possible.
167 #command_check_interval=15s
168 command_check_interval=-1
172 # EXTERNAL COMMAND FILE
173 # This is the file that Nagios checks for external command requests.
174 # It is also where the command CGI will write commands that are submitted
175 # by users, so it must be writeable by the user that the web server
176 # is running as (usually 'nobody'). Permissions should be set at the
177 # directory level instead of on the file, as the file is deleted every
178 # time its contents are processed.
179 # Debian Users: In case you didn't read README.Debian yet, _NOW_ is the
182 command_file=/var/lib/nagios3/rw/nagios.cmd
186 # EXTERNAL COMMAND BUFFER SLOTS
187 # This settings is used to tweak the number of items or "slots" that
188 # the Nagios daemon should allocate to the buffer that holds incoming
189 # external commands before they are processed. As external commands
190 # are processed by the daemon, they are removed from the buffer.
192 external_command_buffer_slots=4096
197 # This is the lockfile that Nagios will use to store its PID number
198 # in when it is running in daemon mode.
200 lock_file=/var/run/nagios3/nagios3.pid
205 # This is a temporary file that is used as scratch space when Nagios
206 # updates the status log, cleans the comment file, etc. This file
207 # is created, used, and deleted throughout the time that Nagios is
210 temp_file=/var/cache/nagios3/nagios.tmp
215 # This is path where Nagios can create temp files for service and
216 # host check results, etc.
222 # EVENT BROKER OPTIONS
223 # Controls what (if any) data gets sent to the event broker.
224 # Values: 0 = Broker nothing
225 # -1 = Broker everything
226 # <other> = See documentation
228 event_broker_options=-1
232 # EVENT BROKER MODULE(S)
233 # This directive is used to specify an event broker module that should
234 # by loaded by Nagios at startup. Use multiple directives if you want
235 # to load more than one module. Arguments that should be passed to
236 # the module at startup are seperated from the module path by a space.
238 #!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
239 # WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING
240 #!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
242 # Do NOT overwrite modules while they are being used by Nagios or Nagios
243 # will crash in a fiery display of SEGFAULT glory. This is a bug/limitation
244 # either in dlopen(), the kernel, and/or the filesystem. And maybe Nagios...
246 # The correct/safe way of updating a module is by using one of these methods:
247 # 1. Shutdown Nagios, replace the module file, restart Nagios
248 # 2. Delete the original module file, move the new module file into place, restart Nagios
252 # broker_module=<modulepath> [moduleargs]
254 #broker_module=/somewhere/module1.o
255 #broker_module=/somewhere/module2.o arg1 arg2=3 debug=0
259 # LOG ROTATION METHOD
260 # This is the log rotation method that Nagios should use to rotate
261 # the main log file. Values are as follows..
262 # n = None - don't rotate the log
263 # h = Hourly rotation (top of the hour)
264 # d = Daily rotation (midnight every day)
265 # w = Weekly rotation (midnight on Saturday evening)
266 # m = Monthly rotation (midnight last day of month)
268 log_rotation_method=d
273 # This is the directory where archived (rotated) log files should be
274 # placed (assuming you've chosen to do log rotation).
276 log_archive_path=/var/log/nagios3/archives
281 # If you want messages logged to the syslog facility, as well as the
282 # Nagios log file set this option to 1. If not, set it to 0.
288 # NOTIFICATION LOGGING OPTION
289 # If you don't want notifications to be logged, set this value to 0.
290 # If notifications should be logged, set the value to 1.
296 # SERVICE RETRY LOGGING OPTION
297 # If you don't want service check retries to be logged, set this value
298 # to 0. If retries should be logged, set the value to 1.
300 log_service_retries=1
304 # HOST RETRY LOGGING OPTION
305 # If you don't want host check retries to be logged, set this value to
306 # 0. If retries should be logged, set the value to 1.
312 # EVENT HANDLER LOGGING OPTION
313 # If you don't want host and service event handlers to be logged, set
314 # this value to 0. If event handlers should be logged, set the value
321 # INITIAL STATES LOGGING OPTION
322 # If you want Nagios to log all initial host and service states to
323 # the main log file (the first time the service or host is checked)
324 # you can enable this option by setting this value to 1. If you
325 # are not using an external application that does long term state
326 # statistics reporting, you do not need to enable this option. In
327 # this case, set the value to 0.
333 # EXTERNAL COMMANDS LOGGING OPTION
334 # If you don't want Nagios to log external commands, set this value
335 # to 0. If external commands should be logged, set this value to 1.
336 # Note: This option does not include logging of passive service
337 # checks - see the option below for controlling whether or not
338 # passive checks are logged.
340 log_external_commands=1
344 # PASSIVE CHECKS LOGGING OPTION
345 # If you don't want Nagios to log passive host and service checks, set
346 # this value to 0. If passive checks should be logged, set
353 # GLOBAL HOST AND SERVICE EVENT HANDLERS
354 # These options allow you to specify a host and service event handler
355 # command that is to be run for every host or service state change.
356 # The global event handler is executed immediately prior to the event
357 # handler that you have optionally specified in each host or
358 # service definition. The command argument is the short name of a
359 # command definition that you define in your host configuration file.
360 # Read the HTML docs for more information.
362 #global_host_event_handler=somecommand
363 #global_service_event_handler=somecommand
367 # SERVICE INTER-CHECK DELAY METHOD
368 # This is the method that Nagios should use when initially
369 # "spreading out" service checks when it starts monitoring. The
370 # default is to use smart delay calculation, which will try to
371 # space all service checks out evenly to minimize CPU load.
372 # Using the dumb setting will cause all checks to be scheduled
373 # at the same time (with no delay between them)! This is not a
374 # good thing for production, but is useful when testing the
375 # parallelization functionality.
376 # n = None - don't use any delay between checks
377 # d = Use a "dumb" delay of 1 second between checks
378 # s = Use "smart" inter-check delay calculation
379 # x.xx = Use an inter-check delay of x.xx seconds
381 service_inter_check_delay_method=s
385 # MAXIMUM SERVICE CHECK SPREAD
386 # This variable determines the timeframe (in minutes) from the
387 # program start time that an initial check of all services should
388 # be completed. Default is 30 minutes.
390 max_service_check_spread=30
394 # SERVICE CHECK INTERLEAVE FACTOR
395 # This variable determines how service checks are interleaved.
396 # Interleaving the service checks allows for a more even
397 # distribution of service checks and reduced load on remote
398 # hosts. Setting this value to 1 is equivalent to how versions
399 # of Nagios previous to 0.0.5 did service checks. Set this
400 # value to s (smart) for automatic calculation of the interleave
401 # factor unless you have a specific reason to change it.
402 # s = Use "smart" interleave factor calculation
403 # x = Use an interleave factor of x, where x is a
404 # number greater than or equal to 1.
406 service_interleave_factor=s
410 # HOST INTER-CHECK DELAY METHOD
411 # This is the method that Nagios should use when initially
412 # "spreading out" host checks when it starts monitoring. The
413 # default is to use smart delay calculation, which will try to
414 # space all host checks out evenly to minimize CPU load.
415 # Using the dumb setting will cause all checks to be scheduled
416 # at the same time (with no delay between them)!
417 # n = None - don't use any delay between checks
418 # d = Use a "dumb" delay of 1 second between checks
419 # s = Use "smart" inter-check delay calculation
420 # x.xx = Use an inter-check delay of x.xx seconds
422 host_inter_check_delay_method=s
426 # MAXIMUM HOST CHECK SPREAD
427 # This variable determines the timeframe (in minutes) from the
428 # program start time that an initial check of all hosts should
429 # be completed. Default is 30 minutes.
431 max_host_check_spread=30
435 # MAXIMUM CONCURRENT SERVICE CHECKS
436 # This option allows you to specify the maximum number of
437 # service checks that can be run in parallel at any given time.
438 # Specifying a value of 1 for this variable essentially prevents
439 # any service checks from being parallelized. A value of 0
440 # will not restrict the number of concurrent checks that are
443 max_concurrent_checks=0
447 # HOST AND SERVICE CHECK REAPER FREQUENCY
448 # This is the frequency (in seconds!) that Nagios will process
449 # the results of host and service checks.
451 check_result_reaper_frequency=10
456 # MAX CHECK RESULT REAPER TIME
457 # This is the max amount of time (in seconds) that a single
458 # check result reaper event will be allowed to run before
459 # returning control back to Nagios so it can perform other
462 max_check_result_reaper_time=30
468 # This is directory where Nagios stores the results of host and
469 # service checks that have not yet been processed.
471 # Note: Make sure that only one instance of Nagios has access
474 check_result_path=/var/lib/nagios3/spool/checkresults
479 # MAX CHECK RESULT FILE AGE
480 # This option determines the maximum age (in seconds) which check
481 # result files are considered to be valid. Files older than this
482 # threshold will be mercilessly deleted without further processing.
484 max_check_result_file_age=3600
489 # CACHED HOST CHECK HORIZON
490 # This option determines the maximum amount of time (in seconds)
491 # that the state of a previous host check is considered current.
492 # Cached host states (from host checks that were performed more
493 # recently that the timeframe specified by this value) can immensely
494 # improve performance in regards to the host check logic.
495 # Too high of a value for this option may result in inaccurate host
496 # states being used by Nagios, while a lower value may result in a
497 # performance hit for host checks. Use a value of 0 to disable host
500 cached_host_check_horizon=15
504 # CACHED SERVICE CHECK HORIZON
505 # This option determines the maximum amount of time (in seconds)
506 # that the state of a previous service check is considered current.
507 # Cached service states (from service checks that were performed more
508 # recently that the timeframe specified by this value) can immensely
509 # improve performance in regards to predictive dependency checks.
510 # Use a value of 0 to disable service check caching.
512 cached_service_check_horizon=15
516 # ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
517 # This option determines whether or not Nagios will attempt to execute
518 # checks of hosts when it predicts that future dependency logic test
519 # may be needed. These predictive checks can help ensure that your
520 # host dependency logic works well.
522 # 0 = Disable predictive checks
523 # 1 = Enable predictive checks (default)
525 enable_predictive_host_dependency_checks=1
529 # ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
530 # This option determines whether or not Nagios will attempt to execute
531 # checks of service when it predicts that future dependency logic test
532 # may be needed. These predictive checks can help ensure that your
533 # service dependency logic works well.
535 # 0 = Disable predictive checks
536 # 1 = Enable predictive checks (default)
538 enable_predictive_service_dependency_checks=1
542 # SOFT STATE DEPENDENCIES
543 # This option determines whether or not Nagios will use soft state
544 # information when checking host and service dependencies. Normally
545 # Nagios will only use the latest hard host or service state when
546 # checking dependencies. If you want it to use the latest state (regardless
547 # of whether its a soft or hard state type), enable this option.
549 # 0 = Don't use soft state dependencies (default)
550 # 1 = Use soft state dependencies
552 soft_state_dependencies=0
556 # TIME CHANGE ADJUSTMENT THRESHOLDS
557 # These options determine when Nagios will react to detected changes
558 # in system time (either forward or backwards).
560 #time_change_threshold=900
564 # AUTO-RESCHEDULING OPTION
565 # This option determines whether or not Nagios will attempt to
566 # automatically reschedule active host and service checks to
567 # "smooth" them out over time. This can help balance the load on
568 # the monitoring server.
569 # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
570 # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
572 auto_reschedule_checks=0
576 # AUTO-RESCHEDULING INTERVAL
577 # This option determines how often (in seconds) Nagios will
578 # attempt to automatically reschedule checks. This option only
579 # has an effect if the auto_reschedule_checks option is enabled.
580 # Default is 30 seconds.
581 # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
582 # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
584 auto_rescheduling_interval=30
588 # AUTO-RESCHEDULING WINDOW
589 # This option determines the "window" of time (in seconds) that
590 # Nagios will look at when automatically rescheduling checks.
591 # Only host and service checks that occur in the next X seconds
592 # (determined by this variable) will be rescheduled. This option
593 # only has an effect if the auto_reschedule_checks option is
594 # enabled. Default is 180 seconds (3 minutes).
595 # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
596 # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
598 auto_rescheduling_window=180
603 # This is the number of seconds to sleep between checking for system
604 # events and service checks that need to be run.
611 # These options control how much time Nagios will allow various
612 # types of commands to execute before killing them off. Options
613 # are available for controlling maximum time allotted for
614 # service checks, host checks, event handlers, notifications, the
615 # ocsp command, and performance data commands. All values are in
618 service_check_timeout=60
619 host_check_timeout=30
620 event_handler_timeout=30
621 notification_timeout=30
627 # RETAIN STATE INFORMATION
628 # This setting determines whether or not Nagios will save state
629 # information for services and hosts before it shuts down. Upon
630 # startup Nagios will reload all saved service and host state
631 # information before starting to monitor. This is useful for
632 # maintaining long-term data on state statistics, etc, but will
633 # slow Nagios down a bit when it (re)starts. Since its only
634 # a one-time penalty, I think its well worth the additional
637 retain_state_information=1
641 # STATE RETENTION FILE
642 # This is the file that Nagios should use to store host and
643 # service state information before it shuts down. The state
644 # information in this file is also read immediately prior to
645 # starting to monitor the network when Nagios is restarted.
646 # This file is used only if the preserve_state_information
647 # variable is set to 1.
649 state_retention_file=/var/lib/nagios3/retention.dat
653 # RETENTION DATA UPDATE INTERVAL
654 # This setting determines how often (in minutes) that Nagios
655 # will automatically save retention data during normal operation.
656 # If you set this value to 0, Nagios will not save retention
657 # data at regular interval, but it will still save retention
658 # data before shutting down or restarting. If you have disabled
659 # state retention, this option has no effect.
661 retention_update_interval=60
665 # USE RETAINED PROGRAM STATE
666 # This setting determines whether or not Nagios will set
667 # program status variables based on the values saved in the
668 # retention file. If you want to use retained program status
669 # information, set this value to 1. If not, set this value
672 use_retained_program_state=1
676 # USE RETAINED SCHEDULING INFO
677 # This setting determines whether or not Nagios will retain
678 # the scheduling info (next check time) for hosts and services
679 # based on the values saved in the retention file. If you
680 # If you want to use retained scheduling info, set this
681 # value to 1. If not, set this value to 0.
683 use_retained_scheduling_info=1
687 # RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
688 # The following variables are used to specify specific host and
689 # service attributes that should *not* be retained by Nagios during
692 # The values of the masks are bitwise ANDs of values specified
693 # by the "MODATTR_" definitions found in include/common.h.
694 # For example, if you do not want the current enabled/disabled state
695 # of flap detection and event handlers for hosts to be retained, you
696 # would use a value of 24 for the host attribute mask...
697 # MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24
699 # This mask determines what host attributes are not retained
700 retained_host_attribute_mask=0
702 # This mask determines what service attributes are not retained
703 retained_service_attribute_mask=0
705 # These two masks determine what process attributes are not retained.
706 # There are two masks, because some process attributes have host and service
707 # options. For example, you can disable active host checks, but leave active
708 # service checks enabled.
709 retained_process_host_attribute_mask=0
710 retained_process_service_attribute_mask=0
712 # These two masks determine what contact attributes are not retained.
713 # There are two masks, because some contact attributes have host and
714 # service options. For example, you can disable host notifications for
715 # a contact, but leave service notifications enabled for them.
716 retained_contact_host_attribute_mask=0
717 retained_contact_service_attribute_mask=0
722 # This is the seconds per unit interval as used in the
723 # host/contact/service configuration files. Setting this to 60 means
724 # that each interval is one minute long (60 seconds). Other settings
725 # have not been tested much, so your mileage is likely to vary...
731 # AGGRESSIVE HOST CHECKING OPTION
732 # If you don't want to turn on aggressive host checking features, set
733 # this value to 0 (the default). Otherwise set this value to 1 to
734 # enable the aggressive check option. Read the docs for more info
735 # on what aggressive host check is or check out the source code in
738 use_aggressive_host_checking=0
742 # SERVICE CHECK EXECUTION OPTION
743 # This determines whether or not Nagios will actively execute
744 # service checks when it initially starts. If this option is
745 # disabled, checks are not actively made, but Nagios can still
746 # receive and process passive check results that come in. Unless
747 # you're implementing redundant hosts or have a special need for
748 # disabling the execution of service checks, leave this enabled!
749 # Values: 1 = enable checks, 0 = disable checks
751 execute_service_checks=1
755 # PASSIVE SERVICE CHECK ACCEPTANCE OPTION
756 # This determines whether or not Nagios will accept passive
757 # service checks results when it initially (re)starts.
758 # Values: 1 = accept passive checks, 0 = reject passive checks
760 accept_passive_service_checks=1
764 # HOST CHECK EXECUTION OPTION
765 # This determines whether or not Nagios will actively execute
766 # host checks when it initially starts. If this option is
767 # disabled, checks are not actively made, but Nagios can still
768 # receive and process passive check results that come in. Unless
769 # you're implementing redundant hosts or have a special need for
770 # disabling the execution of host checks, leave this enabled!
771 # Values: 1 = enable checks, 0 = disable checks
773 execute_host_checks=1
777 # PASSIVE HOST CHECK ACCEPTANCE OPTION
778 # This determines whether or not Nagios will accept passive
779 # host checks results when it initially (re)starts.
780 # Values: 1 = accept passive checks, 0 = reject passive checks
782 accept_passive_host_checks=1
786 # NOTIFICATIONS OPTION
787 # This determines whether or not Nagios will sent out any host or
788 # service notifications when it is initially (re)started.
789 # Values: 1 = enable notifications, 0 = disable notifications
791 enable_notifications=1
795 # EVENT HANDLER USE OPTION
796 # This determines whether or not Nagios will run any host or
797 # service event handlers when it is initially (re)started. Unless
798 # you're implementing redundant hosts, leave this option enabled.
799 # Values: 1 = enable event handlers, 0 = disable event handlers
801 enable_event_handlers=1
805 # PROCESS PERFORMANCE DATA OPTION
806 # This determines whether or not Nagios will process performance
807 # data returned from service and host checks. If this option is
808 # enabled, host performance data will be processed using the
809 # host_perfdata_command (defined below) and service performance
810 # data will be processed using the service_perfdata_command (also
811 # defined below). Read the HTML docs for more information on
813 # Values: 1 = process performance data, 0 = do not process performance data
815 process_performance_data=0
819 # HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
820 # These commands are run after every host and service check is
821 # performed. These commands are executed only if the
822 # enable_performance_data option (above) is set to 1. The command
823 # argument is the short name of a command definition that you
824 # define in your host configuration file. Read the HTML docs for
825 # more information on performance data.
827 #host_perfdata_command=process-host-perfdata
828 #service_perfdata_command=process-service-perfdata
832 # HOST AND SERVICE PERFORMANCE DATA FILES
833 # These files are used to store host and service performance data.
834 # Performance data is only written to these files if the
835 # enable_performance_data option (above) is set to 1.
837 #host_perfdata_file=/tmp/host-perfdata
838 #service_perfdata_file=/tmp/service-perfdata
842 # HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
843 # These options determine what data is written (and how) to the
844 # performance data files. The templates may contain macros, special
845 # characters (\t for tab, \r for carriage return, \n for newline)
846 # and plain text. A newline is automatically added after each write
847 # to the performance data file. Some examples of what you can do are
850 #host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
851 #service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
855 # HOST AND SERVICE PERFORMANCE DATA FILE MODES
856 # This option determines whether or not the host and service
857 # performance data files are opened in write ("w") or append ("a")
858 # mode. If you want to use named pipes, you should use the special
859 # pipe ("p") mode which avoid blocking at startup, otherwise you will
860 # likely want the defult append ("a") mode.
862 #host_perfdata_file_mode=a
863 #service_perfdata_file_mode=a
867 # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
868 # These options determine how often (in seconds) the host and service
869 # performance data files are processed using the commands defined
870 # below. A value of 0 indicates the files should not be periodically
873 #host_perfdata_file_processing_interval=0
874 #service_perfdata_file_processing_interval=0
878 # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
879 # These commands are used to periodically process the host and
880 # service performance data files. The interval at which the
881 # processing occurs is determined by the options above.
883 #host_perfdata_file_processing_command=process-host-perfdata-file
884 #service_perfdata_file_processing_command=process-service-perfdata-file
888 # OBSESS OVER SERVICE CHECKS OPTION
889 # This determines whether or not Nagios will obsess over service
890 # checks and run the ocsp_command defined below. Unless you're
891 # planning on implementing distributed monitoring, do not enable
892 # this option. Read the HTML docs for more information on
893 # implementing distributed monitoring.
894 # Values: 1 = obsess over services, 0 = do not obsess (default)
896 obsess_over_services=0
900 # OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
901 # This is the command that is run for every service check that is
902 # processed by Nagios. This command is executed only if the
903 # obsess_over_services option (above) is set to 1. The command
904 # argument is the short name of a command definition that you
905 # define in your host configuration file. Read the HTML docs for
906 # more information on implementing distributed monitoring.
908 #ocsp_command=somecommand
912 # OBSESS OVER HOST CHECKS OPTION
913 # This determines whether or not Nagios will obsess over host
914 # checks and run the ochp_command defined below. Unless you're
915 # planning on implementing distributed monitoring, do not enable
916 # this option. Read the HTML docs for more information on
917 # implementing distributed monitoring.
918 # Values: 1 = obsess over hosts, 0 = do not obsess (default)
924 # OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
925 # This is the command that is run for every host check that is
926 # processed by Nagios. This command is executed only if the
927 # obsess_over_hosts option (above) is set to 1. The command
928 # argument is the short name of a command definition that you
929 # define in your host configuration file. Read the HTML docs for
930 # more information on implementing distributed monitoring.
932 #ochp_command=somecommand
936 # TRANSLATE PASSIVE HOST CHECKS OPTION
937 # This determines whether or not Nagios will translate
938 # DOWN/UNREACHABLE passive host check results into their proper
939 # state for this instance of Nagios. This option is useful
940 # if you have distributed or failover monitoring setup. In
941 # these cases your other Nagios servers probably have a different
942 # "view" of the network, with regards to the parent/child relationship
943 # of hosts. If a distributed monitoring server thinks a host
944 # is DOWN, it may actually be UNREACHABLE from the point of
945 # this Nagios instance. Enabling this option will tell Nagios
946 # to translate any DOWN or UNREACHABLE host states it receives
947 # passively into the correct state from the view of this server.
948 # Values: 1 = perform translation, 0 = do not translate (default)
950 translate_passive_host_checks=0
954 # PASSIVE HOST CHECKS ARE SOFT OPTION
955 # This determines whether or not Nagios will treat passive host
956 # checks as being HARD or SOFT. By default, a passive host check
957 # result will put a host into a HARD state type. This can be changed
958 # by enabling this option.
959 # Values: 0 = passive checks are HARD, 1 = passive checks are SOFT
961 passive_host_checks_are_soft=0
965 # ORPHANED HOST/SERVICE CHECK OPTIONS
966 # These options determine whether or not Nagios will periodically
967 # check for orphaned host service checks. Since service checks are
968 # not rescheduled until the results of their previous execution
969 # instance are processed, there exists a possibility that some
970 # checks may never get rescheduled. A similar situation exists for
971 # host checks, although the exact scheduling details differ a bit
972 # from service checks. Orphaned checks seem to be a rare
973 # problem and should not happen under normal circumstances.
974 # If you have problems with service checks never getting
975 # rescheduled, make sure you have orphaned service checks enabled.
976 # Values: 1 = enable checks, 0 = disable checks
978 check_for_orphaned_services=1
979 check_for_orphaned_hosts=1
983 # SERVICE FRESHNESS CHECK OPTION
984 # This option determines whether or not Nagios will periodically
985 # check the "freshness" of service results. Enabling this option
986 # is useful for ensuring passive checks are received in a timely
988 # Values: 1 = enabled freshness checking, 0 = disable freshness checking
990 check_service_freshness=1
994 # SERVICE FRESHNESS CHECK INTERVAL
995 # This setting determines how often (in seconds) Nagios will
996 # check the "freshness" of service check results. If you have
997 # disabled service freshness checking, this option has no effect.
999 service_freshness_check_interval=60
1003 # HOST FRESHNESS CHECK OPTION
1004 # This option determines whether or not Nagios will periodically
1005 # check the "freshness" of host results. Enabling this option
1006 # is useful for ensuring passive checks are received in a timely
1008 # Values: 1 = enabled freshness checking, 0 = disable freshness checking
1010 check_host_freshness=0
1014 # HOST FRESHNESS CHECK INTERVAL
1015 # This setting determines how often (in seconds) Nagios will
1016 # check the "freshness" of host check results. If you have
1017 # disabled host freshness checking, this option has no effect.
1019 host_freshness_check_interval=60
1024 # ADDITIONAL FRESHNESS THRESHOLD LATENCY
1025 # This setting determines the number of seconds that Nagios
1026 # will add to any host and service freshness thresholds that
1027 # it calculates (those not explicitly specified by the user).
1029 additional_freshness_latency=15
1034 # FLAP DETECTION OPTION
1035 # This option determines whether or not Nagios will try
1036 # and detect hosts and services that are "flapping".
1037 # Flapping occurs when a host or service changes between
1038 # states too frequently. When Nagios detects that a
1039 # host or service is flapping, it will temporarily suppress
1040 # notifications for that host/service until it stops
1041 # flapping. Flap detection is very experimental, so read
1042 # the HTML documentation before enabling this feature!
1043 # Values: 1 = enable flap detection
1044 # 0 = disable flap detection (default)
1046 enable_flap_detection=1
1050 # FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
1051 # Read the HTML documentation on flap detection for
1052 # an explanation of what this option does. This option
1053 # has no effect if flap detection is disabled.
1055 low_service_flap_threshold=5.0
1056 high_service_flap_threshold=20.0
1057 low_host_flap_threshold=5.0
1058 high_host_flap_threshold=20.0
1062 # DATE FORMAT OPTION
1063 # This option determines how short dates are displayed. Valid options
1065 # us (MM-DD-YYYY HH:MM:SS)
1066 # euro (DD-MM-YYYY HH:MM:SS)
1067 # iso8601 (YYYY-MM-DD HH:MM:SS)
1068 # strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
1077 # This option is used to override the default timezone that this
1078 # instance of Nagios runs in. If not specified, Nagios will use
1079 # the system configured timezone.
1081 # NOTE: In order to display the correct timezone in the CGIs, you
1082 # will also need to alter the Apache directives for the CGI path
1083 # to include your timezone. Example:
1085 # <Directory "/usr/local/nagios/sbin/">
1086 # SetEnv TZ "Australia/Brisbane"
1090 #use_timezone=US/Mountain
1091 #use_timezone=Australia/Brisbane
1096 # P1.PL FILE LOCATION
1097 # This value determines where the p1.pl perl script (used by the
1098 # embedded Perl interpreter) is located. If you didn't compile
1099 # Nagios with embedded Perl support, this option has no effect.
1101 p1_file=/usr/lib/nagios3/p1.pl
1105 # EMBEDDED PERL INTERPRETER OPTION
1106 # This option determines whether or not the embedded Perl interpreter
1107 # will be enabled during runtime. This option has no effect if Nagios
1108 # has not been compiled with support for embedded Perl.
1109 # Values: 0 = disable interpreter, 1 = enable interpreter
1111 enable_embedded_perl=1
1115 # EMBEDDED PERL USAGE OPTION
1116 # This option determines whether or not Nagios will process Perl plugins
1117 # and scripts with the embedded Perl interpreter if the plugins/scripts
1118 # do not explicitly indicate whether or not it is okay to do so. Read
1119 # the HTML documentation on the embedded Perl interpreter for more
1120 # information on how this option works.
1122 use_embedded_perl_implicitly=1
1126 # ILLEGAL OBJECT NAME CHARACTERS
1127 # This option allows you to specify illegal characters that cannot
1128 # be used in host names, service descriptions, or names of other
1131 illegal_object_name_chars=`~!$%^&*|'"<>?,()=
1135 # ILLEGAL MACRO OUTPUT CHARACTERS
1136 # This option allows you to specify illegal characters that are
1137 # stripped from macros before being used in notifications, event
1138 # handlers, etc. This DOES NOT affect macros used in service or
1139 # host check commands.
1140 # The following macros are stripped of the characters you specify:
1147 # $SERVICEACKAUTHOR$
1148 # $SERVICEACKCOMMENT$
1150 illegal_macro_output_chars=`~$&|'"<>
1154 # REGULAR EXPRESSION MATCHING
1155 # This option controls whether or not regular expression matching
1156 # takes place in the object config files. Regular expression
1157 # matching is used to match host, hostgroup, service, and service
1158 # group names/descriptions in some fields of various object types.
1159 # Values: 1 = enable regexp matching, 0 = disable regexp matching
1161 use_regexp_matching=0
1165 # "TRUE" REGULAR EXPRESSION MATCHING
1166 # This option controls whether or not "true" regular expression
1167 # matching takes place in the object config files. This option
1168 # only has an effect if regular expression matching is enabled
1169 # (see above). If this option is DISABLED, regular expression
1170 # matching only occurs if a string contains wildcard characters
1171 # (* and ?). If the option is ENABLED, regexp matching occurs
1172 # all the time (which can be annoying).
1173 # Values: 1 = enable true matching, 0 = disable true matching
1175 use_true_regexp_matching=0
1179 # ADMINISTRATOR EMAIL/PAGER ADDRESSES
1180 # The email and pager address of a global administrator (likely you).
1181 # Nagios never uses these values itself, but you can access them by
1182 # using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
1185 admin_email=root@localhost
1186 admin_pager=pageroot@localhost
1190 # DAEMON CORE DUMP OPTION
1191 # This option determines whether or not Nagios is allowed to create
1192 # a core dump when it runs as a daemon. Note that it is generally
1193 # considered bad form to allow this, but it may be useful for
1194 # debugging purposes. Enabling this option doesn't guarantee that
1195 # a core file will be produced, but that's just life...
1196 # Values: 1 - Allow core dumps
1197 # 0 - Do not allow core dumps (default)
1203 # LARGE INSTALLATION TWEAKS OPTION
1204 # This option determines whether or not Nagios will take some shortcuts
1205 # which can save on memory and CPU usage in large Nagios installations.
1206 # Read the documentation for more information on the benefits/tradeoffs
1207 # of enabling this option.
1208 # Values: 1 - Enabled tweaks
1209 # 0 - Disable tweaks (default)
1211 use_large_installation_tweaks=1
1215 # ENABLE ENVIRONMENT MACROS
1216 # This option determines whether or not Nagios will make all standard
1217 # macros available as environment variables when host/service checks
1218 # and system commands (event handlers, notifications, etc.) are
1219 # executed. Enabling this option can cause performance issues in
1220 # large installations, as it will consume a bit more memory and (more
1221 # importantly) consume more CPU.
1222 # Values: 1 - Enable environment variable macros (default)
1223 # 0 - Disable environment variable macros
1225 enable_environment_macros=1
1229 # CHILD PROCESS MEMORY OPTION
1230 # This option determines whether or not Nagios will free memory in
1231 # child processes (processed used to execute system commands and host/
1232 # service checks). If you specify a value here, it will override
1234 # Value: 1 - Free memory in child processes
1235 # 0 - Do not free memory in child processes
1237 #free_child_process_memory=1
1241 # CHILD PROCESS FORKING BEHAVIOR
1242 # This option determines how Nagios will fork child processes
1243 # (used to execute system commands and host/service checks). Normally
1244 # child processes are fork()ed twice, which provides a very high level
1245 # of isolation from problems. Fork()ing once is probably enough and will
1246 # save a great deal on CPU usage (in large installs), so you might
1247 # want to consider using this. If you specify a value here, it will
1249 # Value: 1 - Child processes fork() twice
1250 # 0 - Child processes fork() just once
1252 child_processes_fork_twice=0
1257 # This option determines how much (if any) debugging information will
1258 # be written to the debug file. OR values together to log multiple
1259 # types of information.
1265 # 4 = Process information
1266 # 8 = Scheduled events
1267 # 16 = Host/service checks
1268 # 32 = Notifications
1270 # 128 = External commands
1272 # 512 = Scheduled downtime
1281 # This option determines how verbose the debug log out will be.
1282 # Values: 0 = Brief output
1291 # This option determines where Nagios should write debugging information.
1293 debug_file=/var/lib/nagios3/nagios.debug
1297 # MAX DEBUG FILE SIZE
1298 # This option determines the maximum size (in bytes) of the debug file. If
1299 # the file grows larger than this size, it will be renamed with a .old
1300 # extension. If a file already exists with a .old extension it will
1301 # automatically be deleted. This helps ensure your disk space usage doesn't
1302 # get out of control when debugging Nagios.
1304 max_debug_file_size=1000000