1 ##############################################################################
3 # NAGIOS.CFG - Sample Main Config File for Nagios 2.9
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: 12-21-2006
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...
34 cfg_file=/etc/nagios/commands.cfg
36 # Host and service definitions for monitoring this machine
37 #cfg_file=/etc/nagios/localhost.cfg
40 # You can split other types of object definitions across several
41 # config files if you wish (as done here), or keep them all in a
44 cfg_file=/etc/nagios/contactgroups.cfg
45 cfg_file=/etc/nagios/contacts.cfg
46 #cfg_file=/etc/nagios/dependencies.cfg
47 #cfg_file=/etc/nagios/escalations.cfg
48 cfg_file=/etc/nagios/hostgroups.cfg
49 cfg_file=/etc/nagios/hosts.cfg
50 cfg_file=/etc/nagios/services.cfg
51 cfg_file=/etc/nagios/timeperiods.cfg
53 # Extended host/service info definitions are now stored along with
54 # other object definitions:
55 #cfg_file=/etc/nagios/hostextinfo.cfg
56 #cfg_file=/etc/nagios/serviceextinfo.cfg
58 # You can also tell Nagios to process all config files (with a .cfg
59 # extension) in a particular directory by using the cfg_dir
60 # directive as shown below:
62 #cfg_dir=/etc/nagios/servers
63 #cfg_dir=/etc/nagios/printers
64 #cfg_dir=/etc/nagios/switches
65 #cfg_dir=/etc/nagios/routers
70 # This option determines where object definitions are cached when
71 # Nagios starts/restarts. The CGIs read object definitions from
72 # this cache file (rather than looking at the object config files
73 # directly) in order to prevent inconsistencies that can occur
74 # when the config files are modified after Nagios starts.
76 object_cache_file=/var/log/nagios/objects.cache
81 # This is an optional resource file that contains $USERx$ macro
82 # definitions. Multiple resource files can be specified by using
83 # multiple resource_file definitions. The CGIs will not attempt to
84 # read the contents of resource files, so information that is
85 # considered to be sensitive (usernames, passwords, etc) can be
86 # defined as macros in this file and restrictive permissions (600)
87 # can be placed on this file.
89 resource_file=/etc/nagios/private/resource.cfg
94 # This is where the current status of all monitored services and
95 # hosts is stored. Its contents are read and processed by the CGIs.
96 # The contents of the status file are deleted every time Nagios
99 status_file=/var/log/nagios/status.dat
104 # This determines the effective user that Nagios should run as.
105 # You can either supply a username or a UID.
112 # This determines the effective group that Nagios should run as.
113 # You can either supply a group name or a GID.
119 # EXTERNAL COMMAND OPTION
120 # This option allows you to specify whether or not Nagios should check
121 # for external commands (in the command file defined below). By default
122 # Nagios will *not* check for external commands, just to be on the
123 # cautious side. If you want to be able to use the CGI command interface
124 # you will have to enable this. Setting this value to 0 disables command
125 # checking (the default), other values enable it.
127 check_external_commands=0
131 # EXTERNAL COMMAND CHECK INTERVAL
132 # This is the interval at which Nagios should check for external commands.
133 # This value works of the interval_length you specify later. If you leave
134 # that at its default value of 60 (seconds), a value of 1 here will cause
135 # Nagios to check for external commands every minute. If you specify a
136 # number followed by an "s" (i.e. 15s), this will be interpreted to mean
137 # actual seconds rather than a multiple of the interval_length variable.
138 # Note: In addition to reading the external command file at regularly
139 # scheduled intervals, Nagios will also check for external commands after
140 # event handlers are executed.
141 # NOTE: Setting this value to -1 causes Nagios to check the external
142 # command file as often as possible.
144 #command_check_interval=15s
145 command_check_interval=-1
149 # EXTERNAL COMMAND FILE
150 # This is the file that Nagios checks for external command requests.
151 # It is also where the command CGI will write commands that are submitted
152 # by users, so it must be writeable by the user that the web server
153 # is running as (usually 'nobody'). Permissions should be set at the
154 # directory level instead of on the file, as the file is deleted every
155 # time its contents are processed.
157 command_file=/var/spool/nagios/cmd/nagios.cmd
161 # EXTERNAL COMMAND BUFFER SLOTS
162 # This settings is used to tweak the number of items or "slots" that
163 # the Nagios daemon should allocate to the buffer that holds incoming
164 # external commands before they are processed. As external commands
165 # are processed by the daemon, they are removed from the buffer.
167 external_command_buffer_slots=4096
172 # This is the file that Nagios will use for storing host and service
175 comment_file=/var/log/nagios/comments.dat
180 # This is the file that Nagios will use for storing host and service
183 downtime_file=/var/log/nagios/downtime.dat
188 # This is the lockfile that Nagios will use to store its PID number
189 # in when it is running in daemon mode.
191 lock_file=/var/run/nagios.pid
196 # This is a temporary file that is used as scratch space when Nagios
197 # updates the status log, cleans the comment file, etc. This file
198 # is created, used, and deleted throughout the time that Nagios is
201 temp_file=/var/log/nagios/nagios.tmp
205 # EVENT BROKER OPTIONS
206 # Controls what (if any) data gets sent to the event broker.
207 # Values: 0 = Broker nothing
208 # -1 = Broker everything
209 # <other> = See documentation
211 event_broker_options=-1
215 # EVENT BROKER MODULE(S)
216 # This directive is used to specify an event broker module that should
217 # by loaded by Nagios at startup. Use multiple directives if you want
218 # to load more than one module. Arguments that should be passed to
219 # the module at startup are seperated from the module path by a space.
223 # broker_module=<modulepath> [moduleargs]
225 #broker_module=/somewhere/module1.o
226 #broker_module=/somewhere/module2.o arg1 arg2=3 debug=0
231 # LOG ROTATION METHOD
232 # This is the log rotation method that Nagios should use to rotate
233 # the main log file. Values are as follows..
234 # n = None - don't rotate the log
235 # h = Hourly rotation (top of the hour)
236 # d = Daily rotation (midnight every day)
237 # w = Weekly rotation (midnight on Saturday evening)
238 # m = Monthly rotation (midnight last day of month)
240 log_rotation_method=d
245 # This is the directory where archived (rotated) log files should be
246 # placed (assuming you've chosen to do log rotation).
248 log_archive_path=/var/log/nagios/archives
253 # If you want messages logged to the syslog facility, as well as the
254 # NetAlarm log file set this option to 1. If not, set it to 0.
260 # NOTIFICATION LOGGING OPTION
261 # If you don't want notifications to be logged, set this value to 0.
262 # If notifications should be logged, set the value to 1.
268 # SERVICE RETRY LOGGING OPTION
269 # If you don't want service check retries to be logged, set this value
270 # to 0. If retries should be logged, set the value to 1.
272 log_service_retries=1
276 # HOST RETRY LOGGING OPTION
277 # If you don't want host check retries to be logged, set this value to
278 # 0. If retries should be logged, set the value to 1.
284 # EVENT HANDLER LOGGING OPTION
285 # If you don't want host and service event handlers to be logged, set
286 # this value to 0. If event handlers should be logged, set the value
293 # INITIAL STATES LOGGING OPTION
294 # If you want Nagios to log all initial host and service states to
295 # the main log file (the first time the service or host is checked)
296 # you can enable this option by setting this value to 1. If you
297 # are not using an external application that does long term state
298 # statistics reporting, you do not need to enable this option. In
299 # this case, set the value to 0.
305 # EXTERNAL COMMANDS LOGGING OPTION
306 # If you don't want Nagios to log external commands, set this value
307 # to 0. If external commands should be logged, set this value to 1.
308 # Note: This option does not include logging of passive service
309 # checks - see the option below for controlling whether or not
310 # passive checks are logged.
312 log_external_commands=1
316 # PASSIVE CHECKS LOGGING OPTION
317 # If you don't want Nagios to log passive host and service checks, set
318 # this value to 0. If passive checks should be logged, set
325 # GLOBAL HOST AND SERVICE EVENT HANDLERS
326 # These options allow you to specify a host and service event handler
327 # command that is to be run for every host or service state change.
328 # The global event handler is executed immediately prior to the event
329 # handler that you have optionally specified in each host or
330 # service definition. The command argument is the short name of a
331 # command definition that you define in your host configuration file.
332 # Read the HTML docs for more information.
334 #global_host_event_handler=somecommand
335 #global_service_event_handler=somecommand
339 # SERVICE INTER-CHECK DELAY METHOD
340 # This is the method that Nagios should use when initially
341 # "spreading out" service checks when it starts monitoring. The
342 # default is to use smart delay calculation, which will try to
343 # space all service checks out evenly to minimize CPU load.
344 # Using the dumb setting will cause all checks to be scheduled
345 # at the same time (with no delay between them)! This is not a
346 # good thing for production, but is useful when testing the
347 # parallelization functionality.
348 # n = None - don't use any delay between checks
349 # d = Use a "dumb" delay of 1 second between checks
350 # s = Use "smart" inter-check delay calculation
351 # x.xx = Use an inter-check delay of x.xx seconds
353 service_inter_check_delay_method=s
357 # MAXIMUM SERVICE CHECK SPREAD
358 # This variable determines the timeframe (in minutes) from the
359 # program start time that an initial check of all services should
360 # be completed. Default is 30 minutes.
362 max_service_check_spread=30
366 # SERVICE CHECK INTERLEAVE FACTOR
367 # This variable determines how service checks are interleaved.
368 # Interleaving the service checks allows for a more even
369 # distribution of service checks and reduced load on remote
370 # hosts. Setting this value to 1 is equivalent to how versions
371 # of Nagios previous to 0.0.5 did service checks. Set this
372 # value to s (smart) for automatic calculation of the interleave
373 # factor unless you have a specific reason to change it.
374 # s = Use "smart" interleave factor calculation
375 # x = Use an interleave factor of x, where x is a
376 # number greater than or equal to 1.
378 service_interleave_factor=s
382 # HOST INTER-CHECK DELAY METHOD
383 # This is the method that Nagios should use when initially
384 # "spreading out" host checks when it starts monitoring. The
385 # default is to use smart delay calculation, which will try to
386 # space all host checks out evenly to minimize CPU load.
387 # Using the dumb setting will cause all checks to be scheduled
388 # at the same time (with no delay between them)!
389 # n = None - don't use any delay between checks
390 # d = Use a "dumb" delay of 1 second between checks
391 # s = Use "smart" inter-check delay calculation
392 # x.xx = Use an inter-check delay of x.xx seconds
394 host_inter_check_delay_method=s
398 # MAXIMUM HOST CHECK SPREAD
399 # This variable determines the timeframe (in minutes) from the
400 # program start time that an initial check of all hosts should
401 # be completed. Default is 30 minutes.
403 max_host_check_spread=30
407 # MAXIMUM CONCURRENT SERVICE CHECKS
408 # This option allows you to specify the maximum number of
409 # service checks that can be run in parallel at any given time.
410 # Specifying a value of 1 for this variable essentially prevents
411 # any service checks from being parallelized. A value of 0
412 # will not restrict the number of concurrent checks that are
415 max_concurrent_checks=0
419 # SERVICE CHECK REAPER FREQUENCY
420 # This is the frequency (in seconds!) that Nagios will process
421 # the results of services that have been checked.
423 service_reaper_frequency=10
427 # CHECK RESULT BUFFER SLOTS
428 # This settings is used to tweak the number of items or "slots" that
429 # the Nagios daemon should allocate to the buffer that holds
430 # service check results before they are processed. As check results
431 # are processed by the daemon, they are removed from the buffer.
433 check_result_buffer_slots=4096
437 # AUTO-RESCHEDULING OPTION
438 # This option determines whether or not Nagios will attempt to
439 # automatically reschedule active host and service checks to
440 # "smooth" them out over time. This can help balance the load on
441 # the monitoring server.
442 # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
443 # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
445 auto_reschedule_checks=0
449 # AUTO-RESCHEDULING INTERVAL
450 # This option determines how often (in seconds) Nagios will
451 # attempt to automatically reschedule checks. This option only
452 # has an effect if the auto_reschedule_checks option is enabled.
453 # Default is 30 seconds.
454 # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
455 # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
457 auto_rescheduling_interval=30
462 # AUTO-RESCHEDULING WINDOW
463 # This option determines the "window" of time (in seconds) that
464 # Nagios will look at when automatically rescheduling checks.
465 # Only host and service checks that occur in the next X seconds
466 # (determined by this variable) will be rescheduled. This option
467 # only has an effect if the auto_reschedule_checks option is
468 # enabled. Default is 180 seconds (3 minutes).
469 # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
470 # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
472 auto_rescheduling_window=180
477 # This is the number of seconds to sleep between checking for system
478 # events and service checks that need to be run.
485 # These options control how much time Nagios will allow various
486 # types of commands to execute before killing them off. Options
487 # are available for controlling maximum time allotted for
488 # service checks, host checks, event handlers, notifications, the
489 # ocsp command, and performance data commands. All values are in
492 service_check_timeout=60
493 host_check_timeout=30
494 event_handler_timeout=30
495 notification_timeout=30
501 # RETAIN STATE INFORMATION
502 # This setting determines whether or not Nagios will save state
503 # information for services and hosts before it shuts down. Upon
504 # startup Nagios will reload all saved service and host state
505 # information before starting to monitor. This is useful for
506 # maintaining long-term data on state statistics, etc, but will
507 # slow Nagios down a bit when it (re)starts. Since its only
508 # a one-time penalty, I think its well worth the additional
511 retain_state_information=1
515 # STATE RETENTION FILE
516 # This is the file that Nagios should use to store host and
517 # service state information before it shuts down. The state
518 # information in this file is also read immediately prior to
519 # starting to monitor the network when Nagios is restarted.
520 # This file is used only if the preserve_state_information
521 # variable is set to 1.
523 state_retention_file=/var/log/nagios/retention.dat
527 # RETENTION DATA UPDATE INTERVAL
528 # This setting determines how often (in minutes) that Nagios
529 # will automatically save retention data during normal operation.
530 # If you set this value to 0, Nagios will not save retention
531 # data at regular interval, but it will still save retention
532 # data before shutting down or restarting. If you have disabled
533 # state retention, this option has no effect.
535 retention_update_interval=60
539 # USE RETAINED PROGRAM STATE
540 # This setting determines whether or not Nagios will set
541 # program status variables based on the values saved in the
542 # retention file. If you want to use retained program status
543 # information, set this value to 1. If not, set this value
546 use_retained_program_state=1
550 # USE RETAINED SCHEDULING INFO
551 # This setting determines whether or not Nagios will retain
552 # the scheduling info (next check time) for hosts and services
553 # based on the values saved in the retention file. If you
554 # If you want to use retained scheduling info, set this
555 # value to 1. If not, set this value to 0.
557 use_retained_scheduling_info=0
562 # This is the seconds per unit interval as used in the
563 # host/contact/service configuration files. Setting this to 60 means
564 # that each interval is one minute long (60 seconds). Other settings
565 # have not been tested much, so your mileage is likely to vary...
571 # AGGRESSIVE HOST CHECKING OPTION
572 # If you don't want to turn on aggressive host checking features, set
573 # this value to 0 (the default). Otherwise set this value to 1 to
574 # enable the aggressive check option. Read the docs for more info
575 # on what aggressive host check is or check out the source code in
578 use_aggressive_host_checking=0
582 # SERVICE CHECK EXECUTION OPTION
583 # This determines whether or not Nagios will actively execute
584 # service checks when it initially starts. If this option is
585 # disabled, checks are not actively made, but Nagios can still
586 # receive and process passive check results that come in. Unless
587 # you're implementing redundant hosts or have a special need for
588 # disabling the execution of service checks, leave this enabled!
589 # Values: 1 = enable checks, 0 = disable checks
591 execute_service_checks=1
595 # PASSIVE SERVICE CHECK ACCEPTANCE OPTION
596 # This determines whether or not Nagios will accept passive
597 # service checks results when it initially (re)starts.
598 # Values: 1 = accept passive checks, 0 = reject passive checks
600 accept_passive_service_checks=1
604 # HOST CHECK EXECUTION OPTION
605 # This determines whether or not Nagios will actively execute
606 # host checks when it initially starts. If this option is
607 # disabled, checks are not actively made, but Nagios can still
608 # receive and process passive check results that come in. Unless
609 # you're implementing redundant hosts or have a special need for
610 # disabling the execution of host checks, leave this enabled!
611 # Values: 1 = enable checks, 0 = disable checks
613 execute_host_checks=1
617 # PASSIVE HOST CHECK ACCEPTANCE OPTION
618 # This determines whether or not Nagios will accept passive
619 # host checks results when it initially (re)starts.
620 # Values: 1 = accept passive checks, 0 = reject passive checks
622 accept_passive_host_checks=1
626 # NOTIFICATIONS OPTION
627 # This determines whether or not Nagios will sent out any host or
628 # service notifications when it is initially (re)started.
629 # Values: 1 = enable notifications, 0 = disable notifications
631 enable_notifications=1
635 # EVENT HANDLER USE OPTION
636 # This determines whether or not Nagios will run any host or
637 # service event handlers when it is initially (re)started. Unless
638 # you're implementing redundant hosts, leave this option enabled.
639 # Values: 1 = enable event handlers, 0 = disable event handlers
641 enable_event_handlers=1
645 # PROCESS PERFORMANCE DATA OPTION
646 # This determines whether or not Nagios will process performance
647 # data returned from service and host checks. If this option is
648 # enabled, host performance data will be processed using the
649 # host_perfdata_command (defined below) and service performance
650 # data will be processed using the service_perfdata_command (also
651 # defined below). Read the HTML docs for more information on
653 # Values: 1 = process performance data, 0 = do not process performance data
655 process_performance_data=0
659 # HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
660 # These commands are run after every host and service check is
661 # performed. These commands are executed only if the
662 # enable_performance_data option (above) is set to 1. The command
663 # argument is the short name of a command definition that you
664 # define in your host configuration file. Read the HTML docs for
665 # more information on performance data.
667 #host_perfdata_command=process-host-perfdata
668 #service_perfdata_command=process-service-perfdata
672 # HOST AND SERVICE PERFORMANCE DATA FILES
673 # These files are used to store host and service performance data.
674 # Performance data is only written to these files if the
675 # enable_performance_data option (above) is set to 1.
677 #host_perfdata_file=/tmp/host-perfdata
678 #service_perfdata_file=/tmp/service-perfdata
682 # HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
683 # These options determine what data is written (and how) to the
684 # performance data files. The templates may contain macros, special
685 # characters (\t for tab, \r for carriage return, \n for newline)
686 # and plain text. A newline is automatically added after each write
687 # to the performance data file. Some examples of what you can do are
690 #host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
691 #service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
696 # HOST AND SERVICE PERFORMANCE DATA FILE MODES
697 # This option determines whether or not the host and service
698 # performance data files are opened in write ("w") or append ("a")
699 # mode. Unless you are the files are named pipes, you will probably
700 # want to use the default mode of append ("a").
702 #host_perfdata_file_mode=a
703 #service_perfdata_file_mode=a
707 # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
708 # These options determine how often (in seconds) the host and service
709 # performance data files are processed using the commands defined
710 # below. A value of 0 indicates the files should not be periodically
713 #host_perfdata_file_processing_interval=0
714 #service_perfdata_file_processing_interval=0
718 # HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
719 # These commands are used to periodically process the host and
720 # service performance data files. The interval at which the
721 # processing occurs is determined by the options above.
723 #host_perfdata_file_processing_command=process-host-perfdata-file
724 #service_perfdata_file_processing_command=process-service-perfdata-file
728 # OBSESS OVER SERVICE CHECKS OPTION
729 # This determines whether or not Nagios will obsess over service
730 # checks and run the ocsp_command defined below. Unless you're
731 # planning on implementing distributed monitoring, do not enable
732 # this option. Read the HTML docs for more information on
733 # implementing distributed monitoring.
734 # Values: 1 = obsess over services, 0 = do not obsess (default)
736 obsess_over_services=0
740 # OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
741 # This is the command that is run for every service check that is
742 # processed by Nagios. This command is executed only if the
743 # obsess_over_service option (above) is set to 1. The command
744 # argument is the short name of a command definition that you
745 # define in your host configuration file. Read the HTML docs for
746 # more information on implementing distributed monitoring.
748 #ocsp_command=somecommand
752 # ORPHANED SERVICE CHECK OPTION
753 # This determines whether or not Nagios will periodically
754 # check for orphaned services. Since service checks are not
755 # rescheduled until the results of their previous execution
756 # instance are processed, there exists a possibility that some
757 # checks may never get rescheduled. This seems to be a rare
758 # problem and should not happen under normal circumstances.
759 # If you have problems with service checks never getting
760 # rescheduled, you might want to try enabling this option.
761 # Values: 1 = enable checks, 0 = disable checks
763 check_for_orphaned_services=1
767 # SERVICE FRESHNESS CHECK OPTION
768 # This option determines whether or not Nagios will periodically
769 # check the "freshness" of service results. Enabling this option
770 # is useful for ensuring passive checks are received in a timely
772 # Values: 1 = enabled freshness checking, 0 = disable freshness checking
774 check_service_freshness=1
778 # SERVICE FRESHNESS CHECK INTERVAL
779 # This setting determines how often (in seconds) Nagios will
780 # check the "freshness" of service check results. If you have
781 # disabled service freshness checking, this option has no effect.
783 service_freshness_check_interval=60
787 # HOST FRESHNESS CHECK OPTION
788 # This option determines whether or not Nagios will periodically
789 # check the "freshness" of host results. Enabling this option
790 # is useful for ensuring passive checks are received in a timely
792 # Values: 1 = enabled freshness checking, 0 = disable freshness checking
794 check_host_freshness=0
798 # HOST FRESHNESS CHECK INTERVAL
799 # This setting determines how often (in seconds) Nagios will
800 # check the "freshness" of host check results. If you have
801 # disabled host freshness checking, this option has no effect.
803 host_freshness_check_interval=60
807 # AGGREGATED STATUS UPDATES
808 # This option determines whether or not Nagios will
809 # aggregate updates of host, service, and program status
810 # data. Normally, status data is updated immediately when
811 # a change occurs. This can result in high CPU loads if
812 # you are monitoring a lot of services. If you want Nagios
813 # to only refresh status data every few seconds, disable
815 # Values: 1 = enable aggregate updates, 0 = disable aggregate updates
817 aggregate_status_updates=1
821 # AGGREGATED STATUS UPDATE INTERVAL
822 # Combined with the aggregate_status_updates option,
823 # this option determines the frequency (in seconds!) that
824 # Nagios will periodically dump program, host, and
825 # service status data. If you are not using aggregated
826 # status data updates, this option has no effect.
828 status_update_interval=15
832 # FLAP DETECTION OPTION
833 # This option determines whether or not Nagios will try
834 # and detect hosts and services that are "flapping".
835 # Flapping occurs when a host or service changes between
836 # states too frequently. When Nagios detects that a
837 # host or service is flapping, it will temporarily suppress
838 # notifications for that host/service until it stops
839 # flapping. Flap detection is very experimental, so read
840 # the HTML documentation before enabling this feature!
841 # Values: 1 = enable flap detection
842 # 0 = disable flap detection (default)
844 enable_flap_detection=0
848 # FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
849 # Read the HTML documentation on flap detection for
850 # an explanation of what this option does. This option
851 # has no effect if flap detection is disabled.
853 low_service_flap_threshold=5.0
854 high_service_flap_threshold=20.0
855 low_host_flap_threshold=5.0
856 high_host_flap_threshold=20.0
861 # This option determines how short dates are displayed. Valid options
863 # us (MM-DD-YYYY HH:MM:SS)
864 # euro (DD-MM-YYYY HH:MM:SS)
865 # iso8601 (YYYY-MM-DD HH:MM:SS)
866 # strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
873 # P1.PL FILE LOCATION
874 # This value determines where the p1.pl perl script (used by the
875 # embedded Perl interpreter) is located. If you didn't compile
876 # Nagios with embedded Perl support, this option has no effect.
878 p1_file=/usr/sbin/p1.pl
882 # ILLEGAL OBJECT NAME CHARACTERS
883 # This option allows you to specify illegal characters that cannot
884 # be used in host names, service descriptions, or names of other
887 illegal_object_name_chars=`~!$%^&*|'"<>?,()=
891 # ILLEGAL MACRO OUTPUT CHARACTERS
892 # This option allows you to specify illegal characters that are
893 # stripped from macros before being used in notifications, event
894 # handlers, etc. This DOES NOT affect macros used in service or
895 # host check commands.
896 # The following macros are stripped of the characters you specify:
904 # $SERVICEACKCOMMENT$
906 illegal_macro_output_chars=`~$&|'"<>
910 # REGULAR EXPRESSION MATCHING
911 # This option controls whether or not regular expression matching
912 # takes place in the object config files. Regular expression
913 # matching is used to match host, hostgroup, service, and service
914 # group names/descriptions in some fields of various object types.
915 # Values: 1 = enable regexp matching, 0 = disable regexp matching
917 use_regexp_matching=0
921 # "TRUE" REGULAR EXPRESSION MATCHING
922 # This option controls whether or not "true" regular expression
923 # matching takes place in the object config files. This option
924 # only has an effect if regular expression matching is enabled
925 # (see above). If this option is DISABLED, regular expression
926 # matching only occurs if a string contains wildcard characters
927 # (* and ?). If the option is ENABLED, regexp matching occurs
928 # all the time (which can be annoying).
929 # Values: 1 = enable true matching, 0 = disable true matching
931 use_true_regexp_matching=0
936 # ADMINISTRATOR EMAIL ADDRESS
937 # The email address of the administrator of *this* machine (the one
938 # doing the monitoring). Nagios never uses this value itself, but
939 # you can access this value by using the $ADMINEMAIL$ macro in your
940 # notification commands.
942 admin_email=moahmed-amine.chaoui@sophia.inria.fr
946 # ADMINISTRATOR PAGER NUMBER/ADDRESS
947 # The pager number/address for the administrator of *this* machine.
948 # Nagios never uses this value itself, but you can access this
949 # value by using the $ADMINPAGER$ macro in your notification
952 admin_pager=pagenagios
956 # DAEMON CORE DUMP OPTION
957 # This option determines whether or not Nagios is allowed to create
958 # a core dump when it runs as a daemon. Note that it is generally
959 # considered bad form to allow this, but it may be useful for
960 # debugging purposes.
961 # Values: 1 - Allow core dumps
962 # 0 - Do not allow core dumps (default)