1 ##############################################################################
3 # NAGIOS.CFG - Sample Main Config File for Nagios
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.
9 # Last Modified: 11-23-2005
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/nagios/nagios.log
23 # OBJECT CONFIGURATION FILE(S)
24 # This is the configuration file in which you define hosts, host
25 # groups, contacts, contact groups, services, etc. I guess it would
26 # be better called an object definition file, but for historical
27 # reasons it isn't. You can split object definitions into several
28 # different config files by using multiple cfg_file statements here.
29 # Nagios will read and process all the config files you define.
30 # This can be very useful if you want to keep command definitions
31 # separate from host and contact definitions...
33 # Plugin commands (service and host check commands)
34 # Arguments are likely to change between different releases of the
35 # plugins, so you should use the same config file provided with the
36 # plugin release rather than the one provided with Nagios.
37 # merged into generic.cfg
38 #cfg_file=/etc/nagios/checkcommands.cfg
40 # Misc commands (notification and event handler commands, etc)
41 cfg_file=/etc/nagios/misccommands.cfg
43 # You can split other types of object definitions across several
44 # config files if you wish (as done here), or keep them all in a
47 # we define here the generic stuff that planetlab.cfg relies upon
48 cfg_file=/etc/nagios/generic.cfg
50 # python-generated common definitions - need to be loaded first
51 cfg_file=/etc/nagios/planetlab.cfg
53 # python-generated details
54 cfg_dir=/etc/nagios/planetlab/
59 # This option determines where object definitions are cached when
60 # Nagios starts/restarts. The CGIs read object definitions from
61 # this cache file (rather than looking at the object config files
62 # directly) in order to prevent inconsistencies that can occur
63 # when the config files are modified after Nagios starts.
65 object_cache_file=/var/log/nagios/objects.cache
69 # This is an optional resource file that contains $USERx$ macro
70 # definitions. Multiple resource files can be specified by using
71 # multiple resource_file definitions. The CGIs will not attempt to
72 # read the contents of resource files, so information that is
73 # considered to be sensitive (usernames, passwords, etc) can be
74 # defined as macros in this file and restrictive permissions (600)
75 # can be placed on this file.
77 resource_file=/etc/nagios/private/resource.cfg
82 # This is where the current status of all monitored services and
83 # hosts is stored. Its contents are read and processed by the CGIs.
84 # The contents of the status file are deleted every time Nagios
87 status_file=/var/log/nagios/status.dat
92 # This determines the effective user that Nagios should run as.
93 # You can either supply a username or a UID.
100 # This determines the effective group that Nagios should run as.
101 # You can either supply a group name or a GID.
107 # EXTERNAL COMMAND OPTION
108 # This option allows you to specify whether or not Nagios should check
109 # for external commands (in the command file defined below). By default
110 # Nagios will *not* check for external commands, just to be on the
111 # cautious side. If you want to be able to use the CGI command interface
112 # you will have to enable this. Setting this value to 0 disables command
113 # checking (the default), other values enable it.
115 check_external_commands=1
119 # EXTERNAL COMMAND CHECK INTERVAL
120 # This is the interval at which Nagios should check for external commands.
121 # This value works of the interval_length you specify later. If you leave
122 # that at its default value of 60 (seconds), a value of 1 here will cause
123 # Nagios to check for external commands every minute. If you specify a
124 # number followed by an "s" (i.e. 15s), this will be interpreted to mean
125 # actual seconds rather than a multiple of the interval_length variable.
126 # Note: In addition to reading the external command file at regularly
127 # scheduled intervals, Nagios will also check for external commands after
128 # event handlers are executed.
129 # NOTE: Setting this value to -1 causes Nagios to check the external
130 # command file as often as possible.
132 #command_check_interval=1
133 #command_check_interval=15s
134 command_check_interval=-1
138 # EXTERNAL COMMAND FILE
139 # This is the file that Nagios checks for external command requests.
140 # It is also where the command CGI will write commands that are submitted
141 # by users, so it must be writeable by the user that the web server
142 # is running as (usually 'nobody'). Permissions should be set at the
143 # directory level instead of on the file, as the file is deleted every
144 # time its contents are processed.
146 command_file=/var/spool/nagios/cmd/nagios.cmd
151 # This is the file that Nagios will use for storing host and service
154 comment_file=/var/log/nagios/comments.dat
159 # This is the file that Nagios will use for storing host and service
162 downtime_file=/var/log/nagios/downtime.dat
167 # This is the lockfile that Nagios will use to store its PID number
168 # in when it is running in daemon mode.
170 lock_file=/var/run/nagios.pid
175 # This is a temporary file that is used as scratch space when Nagios
176 # updates the status log, cleans the comment file, etc. This file
177 # is created, used, and deleted throughout the time that Nagios is
180 temp_file=/var/log/nagios/nagios.tmp
184 # EVENT BROKER OPTIONS
185 # Controls what (if any) data gets sent to the event broker.
186 # Values: 0 = Broker nothing
187 # -1 = Broker everything
188 # <other> = See documentation
190 event_broker_options=-1
194 # EVENT BROKER MODULE(S)
195 # This directive is used to specify an event broker module that should
196 # by loaded by Nagios at startup. Use multiple directives if you want
197 # to load more than one module. Arguments that should be passed to
198 # the module at startup are seperated from the module path by a space.
202 # broker_module=<modulepath> [moduleargs]
204 #broker_module=/somewhere/module1.o
205 #broker_module=/somewhere/module2.o arg1 arg2=3 debug=0
210 # LOG ROTATION METHOD
211 # This is the log rotation method that Nagios should use to rotate
212 # the main log file. Values are as follows..
213 # n = None - don't rotate the log
214 # h = Hourly rotation (top of the hour)
215 # d = Daily rotation (midnight every day)
216 # w = Weekly rotation (midnight on Saturday evening)
217 # m = Monthly rotation (midnight last day of month)
219 log_rotation_method=d
224 # This is the directory where archived (rotated) log files should be
225 # placed (assuming you've chosen to do log rotation).
227 log_archive_path=/var/log/nagios/archives
232 # If you want messages logged to the syslog facility, as well as the
233 # NetAlarm log file set this option to 1. If not, set it to 0.
239 # NOTIFICATION LOGGING OPTION
240 # If you don't want notifications to be logged, set this value to 0.
241 # If notifications should be logged, set the value to 1.
247 # SERVICE RETRY LOGGING OPTION
248 # If you don't want service check retries to be logged, set this value
249 # to 0. If retries should be logged, set the value to 1.
251 log_service_retries=1
255 # HOST RETRY LOGGING OPTION
256 # If you don't want host check retries to be logged, set this value to
257 # 0. If retries should be logged, set the value to 1.
263 # EVENT HANDLER LOGGING OPTION
264 # If you don't want host and service event handlers to be logged, set
265 # this value to 0. If event handlers should be logged, set the value
272 # INITIAL STATES LOGGING OPTION
273 # If you want Nagios to log all initial host and service states to
274 # the main log file (the first time the service or host is checked)
275 # you can enable this option by setting this value to 1. If you
276 # are not using an external application that does long term state
277 # statistics reporting, you do not need to enable this option. In
278 # this case, set the value to 0.
284 # EXTERNAL COMMANDS LOGGING OPTION
285 # If you don't want Nagios to log external commands, set this value
286 # to 0. If external commands should be logged, set this value to 1.
287 # Note: This option does not include logging of passive service
288 # checks - see the option below for controlling whether or not
289 # passive checks are logged.
291 log_external_commands=1
295 # PASSIVE CHECKS LOGGING OPTION
296 # If you don't want Nagios to log passive host and service checks, set
297 # this value to 0. If passive checks should be logged, set
304 # GLOBAL HOST AND SERVICE EVENT HANDLERS
305 # These options allow you to specify a host and service event handler
306 # command that is to be run for every host or service state change.
307 # The global event handler is executed immediately prior to the event
308 # handler that you have optionally specified in each host or
309 # service definition. The command argument is the short name of a
310 # command definition that you define in your host configuration file.
311 # Read the HTML docs for more information.
313 #global_host_event_handler=somecommand
314 #global_service_event_handler=somecommand
318 # SERVICE INTER-CHECK DELAY METHOD
319 # This is the method that Nagios should use when initially
320 # "spreading out" service checks when it starts monitoring. The
321 # default is to use smart delay calculation, which will try to
322 # space all service checks out evenly to minimize CPU load.
323 # Using the dumb setting will cause all checks to be scheduled
324 # at the same time (with no delay between them)! This is not a
325 # good thing for production, but is useful when testing the
326 # parallelization functionality.
327 # n = None - don't use any delay between checks
328 # d = Use a "dumb" delay of 1 second between checks
329 # s = Use "smart" inter-check delay calculation
330 # x.xx = Use an inter-check delay of x.xx seconds
332 service_inter_check_delay_method=s
336 # MAXIMUM SERVICE CHECK SPREAD
337 # This variable determines the timeframe (in minutes) from the
338 # program start time that an initial check of all services should
339 # be completed. Default is 30 minutes.
341 max_service_check_spread=30
345 # SERVICE CHECK INTERLEAVE FACTOR
346 # This variable determines how service checks are interleaved.
347 # Interleaving the service checks allows for a more even
348 # distribution of service checks and reduced load on remote
349 # hosts. Setting this value to 1 is equivalent to how versions
350 # of Nagios previous to 0.0.5 did service checks. Set this
351 # value to s (smart) for automatic calculation of the interleave
352 # factor unless you have a specific reason to change it.
353 # s = Use "smart" interleave factor calculation
354 # x = Use an interleave factor of x, where x is a
355 # number greater than or equal to 1.
357 service_interleave_factor=s
361 # HOST INTER-CHECK DELAY METHOD
362 # This is the method that Nagios should use when initially
363 # "spreading out" host checks when it starts monitoring. The
364 # default is to use smart delay calculation, which will try to
365 # space all host checks out evenly to minimize CPU load.
366 # Using the dumb setting will cause all checks to be scheduled
367 # at the same time (with no delay between them)!
368 # n = None - don't use any delay between checks
369 # d = Use a "dumb" delay of 1 second between checks
370 # s = Use "smart" inter-check delay calculation
371 # x.xx = Use an inter-check delay of x.xx seconds
373 host_inter_check_delay_method=s
377 # MAXIMUM HOST CHECK SPREAD
378 # This variable determines the timeframe (in minutes) from the
379 # program start time that an initial check of all hosts should
380 # be completed. Default is 30 minutes.
382 max_host_check_spread=30
386 # MAXIMUM CONCURRENT SERVICE CHECKS
387 # This option allows you to specify the maximum number of
388 # service checks that can be run in parallel at any given time.
389 # Specifying a value of 1 for this variable essentially prevents
390 # any service checks from being parallelized. A value of 0
391 # will not restrict the number of concurrent checks that are
394 max_concurrent_checks=0
398 # SERVICE CHECK REAPER FREQUENCY
399 # This is the frequency (in seconds!) that Nagios will process
400 # the results of services that have been checked.
402 service_reaper_frequency=10
407 # AUTO-RESCHEDULING OPTION
408 # This option determines whether or not Nagios will attempt to
409 # automatically reschedule active host and service checks to
410 # "smooth" them out over time. This can help balance the load on
411 # the monitoring server.
412 # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
413 # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
415 auto_reschedule_checks=0
419 # AUTO-RESCHEDULING INTERVAL
420 # This option determines how often (in seconds) Nagios will
421 # attempt to automatically reschedule checks. This option only
422 # has an effect if the auto_reschedule_checks option is enabled.
423 # Default is 30 seconds.
424 # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
425 # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
427 auto_rescheduling_interval=30
432 # AUTO-RESCHEDULING WINDOW
433 # This option determines the "window" of time (in seconds) that
434 # Nagios will look at when automatically rescheduling checks.
435 # Only host and service checks that occur in the next X seconds
436 # (determined by this variable) will be rescheduled. This option
437 # only has an effect if the auto_reschedule_checks option is
438 # enabled. Default is 180 seconds (3 minutes).
439 # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
440 # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
442 auto_rescheduling_window=180
447 # This is the number of seconds to sleep between checking for system
448 # events and service checks that need to be run.
455 # These options control how much time Nagios will allow various
456 # types of commands to execute before killing them off. Options
457 # are available for controlling maximum time allotted for
458 # service checks, host checks, event handlers, notifications, the
459 # ocsp command, and performance data commands. All values are in
462 service_check_timeout=60
463 host_check_timeout=30
464 event_handler_timeout=30
465 notification_timeout=30
471 # RETAIN STATE INFORMATION
472 # This setting determines whether or not Nagios will save state
473 # information for services and hosts before it shuts down. Upon
474 # startup Nagios will reload all saved service and host state
475 # information before starting to monitor. This is useful for
476 # maintaining long-term data on state statistics, etc, but will
477 # slow Nagios down a bit when it (re)starts. Since its only
478 # a one-time penalty, I think its well worth the additional
481 retain_state_information=1
485 # STATE RETENTION FILE
486 # This is the file that Nagios should use to store host and
487 # service state information before it shuts down. The state
488 # information in this file is also read immediately prior to
489 # starting to monitor the network when Nagios is restarted.
490 # This file is used only if the preserve_state_information
491 # variable is set to 1.
493 state_retention_file=/var/log/nagios/retention.dat
497 # RETENTION DATA UPDATE INTERVAL
498 # This setting determines how often (in minutes) that Nagios
499 # will automatically save retention data during normal operation.
500 # If you set this value to 0, Nagios will not save retention
501 # data at regular interval, but it will still save retention
502 # data before shutting down or restarting. If you have disabled
503 # state retention, this option has no effect.
505 retention_update_interval=60
509 # USE RETAINED PROGRAM STATE
510 # This setting determines whether or not Nagios will set
511 # program status variables based on the values saved in the
512 # retention file. If you want to use retained program status
513 # information, set this value to 1. If not, set this value
516 use_retained_program_state=1
520 # USE RETAINED SCHEDULING INFO
521 # This setting determines whether or not Nagios will retain
522 # the scheduling info (next check time) for hosts and services
523 # based on the values saved in the retention file. If you
524 # If you want to use retained scheduling info, set this
525 # value to 1. If not, set this value to 0.
527 use_retained_scheduling_info=0
532 # This is the seconds per unit interval as used in the
533 # host/contact/service configuration files. Setting this to 60 means
534 # that each interval is one minute long (60 seconds). Other settings
535 # have not been tested much, so your mileage is likely to vary...
541 # AGGRESSIVE HOST CHECKING OPTION
542 # If you don't want to turn on aggressive host checking features, set
543 # this value to 0 (the default). Otherwise set this value to 1 to
544 # enable the aggressive check option. Read the docs for more info
545 # on what aggressive host check is or check out the source code in
548 use_aggressive_host_checking=0
552 # SERVICE CHECK EXECUTION OPTION
553 # This determines whether or not Nagios will actively execute
554 # service checks when it initially starts. If this option is
555 # disabled, checks are not actively made, but Nagios can still
556 # receive and process passive check results that come in. Unless
557 # you're implementing redundant hosts or have a special need for
558 # disabling the execution of service checks, leave this enabled!
559 # Values: 1 = enable checks, 0 = disable checks
561 execute_service_checks=1
565 # PASSIVE SERVICE CHECK ACCEPTANCE OPTION
566 # This determines whether or not Nagios will accept passive
567 # service checks results when it initially (re)starts.
568 # Values: 1 = accept passive checks, 0 = reject passive checks
570 accept_passive_service_checks=1
574 # HOST CHECK EXECUTION OPTION
575 # This determines whether or not Nagios will actively execute
576 # host checks when it initially starts. If this option is
577 # disabled, checks are not actively made, but Nagios can still
578 # receive and process passive check results that come in. Unless
579 # you're implementing redundant hosts or have a special need for
580 # disabling the execution of host checks, leave this enabled!
581 # Values: 1 = enable checks, 0 = disable checks
583 execute_host_checks=1
587 # PASSIVE HOST CHECK ACCEPTANCE OPTION
588 # This determines whether or not Nagios will accept passive
589 # host checks results when it initially (re)starts.
590 # Values: 1 = accept passive checks, 0 = reject passive checks
592 accept_passive_host_checks=1
596 # NOTIFICATIONS OPTION
597 # This determines whether or not Nagios will sent out any host or
598 # service notifications when it is initially (re)started.
599 # Values: 1 = enable notifications, 0 = disable notifications
601 enable_notifications=1
605 # EVENT HANDLER USE OPTION
606 # This determines whether or not Nagios will run any host or
607 # service event handlers when it is initially (re)started. Unless
608 # you're implementing redundant hosts, leave this option enabled.
609 # Values: 1 = enable event handlers, 0 = disable event handlers
611 enable_event_handlers=1
615 # PROCESS PERFORMANCE DATA OPTION
616 # This determines whether or not Nagios will process performance
617 # data returned from service and host checks. If this option is
618 # enabled, host performance data will be processed using the
619 # host_perfdata_command (defined below) and service performance
620 # data will be processed using the service_perfdata_command (also
621 # defined below). Read the HTML docs for more information on
623 # Values: 1 = process performance data, 0 = do not process performance data
625 process_performance_data=0
629 # HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
630 # These commands are run after every host and service check is
631 # performed. These commands are executed only if the
632 # enable_performance_data option (above) is set to 1. The command
633 # argument is the short name of a command definition that you
634 # define in your host configuration file. Read the HTML docs for
635 # more information on performance data.
637 #host_perfdata_command=process-host-perfdata
638 #service_perfdata_command=process-service-perfdata
642 # HOST AND SERVICE PERFORMANCE DATA FILES
643 # These files are used to store host and service performance data.
644 # Performance data is only written to these files if the
645 # enable_performance_data option (above) is set to 1.
647 #host_perfdata_file=/tmp/host-perfdata
648 #service_perfdata_file=/tmp/service-perfdata
652 # HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
653 # These options determine what data is written (and how) to the
654 # performance data files. The templates may contain macros, special
655 # characters (\t for tab, \r for carriage return, \n for newline)
656 # and plain text. A newline is automatically added after each write
657 # to the performance data file. Some examples of what you can do are
660 #host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
661 #service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
666 # HOST AND SERVICE PERFORMANCE DATA FILE MODES
667 # This option determines whether or not the host and service
668 # performance data files are opened in write ("w") or append ("a")
669 # mode. Unless you are the files are named pipes, you will probably
670 # want to use the default mode of append ("a").
672 #host_perfdata_file_mode=a
673 #service_perfdata_file_mode=a
677 # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
678 # These options determine how often (in seconds) the host and service
679 # performance data files are processed using the commands defined
680 # below. A value of 0 indicates the files should not be periodically
683 #host_perfdata_file_processing_interval=0
684 #service_perfdata_file_processing_interval=0
688 # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
689 # These commands are used to periodically process the host and
690 # service performance data files. The interval at which the
691 # processing occurs is determined by the options above.
693 #host_perfdata_file_processing_command=process-host-perfdata-file
694 #service_perfdata_file_processing_command=process-service-perfdata-file
698 # OBSESS OVER SERVICE CHECKS OPTION
699 # This determines whether or not Nagios will obsess over service
700 # checks and run the ocsp_command defined below. Unless you're
701 # planning on implementing distributed monitoring, do not enable
702 # this option. Read the HTML docs for more information on
703 # implementing distributed monitoring.
704 # Values: 1 = obsess over services, 0 = do not obsess (default)
706 obsess_over_services=0
710 # OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
711 # This is the command that is run for every service check that is
712 # processed by Nagios. This command is executed only if the
713 # obsess_over_service option (above) is set to 1. The command
714 # argument is the short name of a command definition that you
715 # define in your host configuration file. Read the HTML docs for
716 # more information on implementing distributed monitoring.
718 #ocsp_command=somecommand
722 # ORPHANED SERVICE CHECK OPTION
723 # This determines whether or not Nagios will periodically
724 # check for orphaned services. Since service checks are not
725 # rescheduled until the results of their previous execution
726 # instance are processed, there exists a possibility that some
727 # checks may never get rescheduled. This seems to be a rare
728 # problem and should not happen under normal circumstances.
729 # If you have problems with service checks never getting
730 # rescheduled, you might want to try enabling this option.
731 # Values: 1 = enable checks, 0 = disable checks
733 check_for_orphaned_services=0
737 # SERVICE FRESHNESS CHECK OPTION
738 # This option determines whether or not Nagios will periodically
739 # check the "freshness" of service results. Enabling this option
740 # is useful for ensuring passive checks are received in a timely
742 # Values: 1 = enabled freshness checking, 0 = disable freshness checking
744 check_service_freshness=1
748 # SERVICE FRESHNESS CHECK INTERVAL
749 # This setting determines how often (in seconds) Nagios will
750 # check the "freshness" of service check results. If you have
751 # disabled service freshness checking, this option has no effect.
753 service_freshness_check_interval=60
757 # HOST FRESHNESS CHECK OPTION
758 # This option determines whether or not Nagios will periodically
759 # check the "freshness" of host results. Enabling this option
760 # is useful for ensuring passive checks are received in a timely
762 # Values: 1 = enabled freshness checking, 0 = disable freshness checking
764 check_host_freshness=0
768 # HOST FRESHNESS CHECK INTERVAL
769 # This setting determines how often (in seconds) Nagios will
770 # check the "freshness" of host check results. If you have
771 # disabled host freshness checking, this option has no effect.
773 host_freshness_check_interval=60
777 # AGGREGATED STATUS UPDATES
778 # This option determines whether or not Nagios will
779 # aggregate updates of host, service, and program status
780 # data. Normally, status data is updated immediately when
781 # a change occurs. This can result in high CPU loads if
782 # you are monitoring a lot of services. If you want Nagios
783 # to only refresh status data every few seconds, disable
785 # Values: 1 = enable aggregate updates, 0 = disable aggregate updates
787 aggregate_status_updates=1
791 # AGGREGATED STATUS UPDATE INTERVAL
792 # Combined with the aggregate_status_updates option,
793 # this option determines the frequency (in seconds!) that
794 # Nagios will periodically dump program, host, and
795 # service status data. If you are not using aggregated
796 # status data updates, this option has no effect.
798 status_update_interval=15
802 # FLAP DETECTION OPTION
803 # This option determines whether or not Nagios will try
804 # and detect hosts and services that are "flapping".
805 # Flapping occurs when a host or service changes between
806 # states too frequently. When Nagios detects that a
807 # host or service is flapping, it will temporarily suppress
808 # notifications for that host/service until it stops
809 # flapping. Flap detection is very experimental, so read
810 # the HTML documentation before enabling this feature!
811 # Values: 1 = enable flap detection
812 # 0 = disable flap detection (default)
814 enable_flap_detection=0
818 # FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
819 # Read the HTML documentation on flap detection for
820 # an explanation of what this option does. This option
821 # has no effect if flap detection is disabled.
823 low_service_flap_threshold=5.0
824 high_service_flap_threshold=20.0
825 low_host_flap_threshold=5.0
826 high_host_flap_threshold=20.0
831 # This option determines how short dates are displayed. Valid options
833 # us (MM-DD-YYYY HH:MM:SS)
834 # euro (DD-MM-YYYY HH:MM:SS)
835 # iso8601 (YYYY-MM-DD HH:MM:SS)
836 # strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
843 # P1.PL FILE LOCATION
844 # This value determines where the p1.pl perl script (used by the
845 # embedded Perl interpreter) is located. If you didn't compile
846 # Nagios with embedded Perl support, this option has no effect.
848 p1_file=/usr/sbin/p1.pl
852 # ILLEGAL OBJECT NAME CHARACTERS
853 # This option allows you to specify illegal characters that cannot
854 # be used in host names, service descriptions, or names of other
857 illegal_object_name_chars=`~!$%^&*|'"<>?,()=
861 # ILLEGAL MACRO OUTPUT CHARACTERS
862 # This option allows you to specify illegal characters that are
863 # stripped from macros before being used in notifications, event
864 # handlers, etc. This DOES NOT affect macros used in service or
865 # host check commands.
866 # The following macros are stripped of the characters you specify:
874 # $SERVICEACKCOMMENT$
876 illegal_macro_output_chars=`~$&|'"<>
880 # REGULAR EXPRESSION MATCHING
881 # This option controls whether or not regular expression matching
882 # takes place in the object config files. Regular expression
883 # matching is used to match host, hostgroup, service, and service
884 # group names/descriptions in some fields of various object types.
885 # Values: 1 = enable regexp matching, 0 = disable regexp matching
887 use_regexp_matching=0
891 # "TRUE" REGULAR EXPRESSION MATCHING
892 # This option controls whether or not "true" regular expression
893 # matching takes place in the object config files. This option
894 # only has an effect if regular expression matching is enabled
895 # (see above). If this option is DISABLED, regular expression
896 # matching only occurs if a string contains wildcard characters
897 # (* and ?). If the option is ENABLED, regexp matching occurs
898 # all the time (which can be annoying).
899 # Values: 1 = enable true matching, 0 = disable true matching
901 use_true_regexp_matching=0
906 # ADMINISTRATOR EMAIL ADDRESS
907 # The email address of the administrator of *this* machine (the one
908 # doing the monitoring). Nagios never uses this value itself, but
909 # you can access this value by using the $ADMINEMAIL$ macro in your
910 # notification commands.
916 # ADMINISTRATOR PAGER NUMBER/ADDRESS
917 # The pager number/address for the administrator of *this* machine.
918 # Nagios never uses this value itself, but you can access this
919 # value by using the $ADMINPAGER$ macro in your notification
922 admin_pager=pagenagios
926 # DAEMON CORE DUMP OPTION
927 # This option determines whether or not Nagios is allowed to create
928 # a core dump when it runs as a daemon. Note that it is generally
929 # considered bad form to allow this, but it may be useful for
930 # debugging purposes.
931 # Values: 1 - Allow core dumps
932 # 0 - Do not allow core dumps (default)