source: noc/nagios/nagios.cfg @ 1061

Last change on this file since 1061 was 1061, checked in by quentin, 13 years ago
Forgot a couple config files
File size: 41.1 KB
Line 
1##############################################################################
2#
3# NAGIOS.CFG - Sample Main Config File for Nagios
4#
5#
6##############################################################################
7
8
9# LOG FILE
10# This is the main log file where service and host events are logged
11# for historical purposes.  This should be the first option specified
12# in the config file!!!
13
14log_file=/var/log/nagios3/nagios.log
15
16# Debian also defaults to using the check commands defined by the debian
17# nagios-plugins package
18cfg_dir=/etc/nagios-plugins/config
19
20# OBJECT CONFIGURATION FILE(S)
21# These are the object configuration files in which you define hosts,
22# host groups, contacts, contact groups, services, etc.
23# You can split your object definitions across several config files
24# if you wish (as shown below), or keep them all in a single config file.
25
26# You can specify individual object config files as shown below:
27cfg_file=/etc/nagios3/checkcommands.cfg
28cfg_file=/etc/nagios3/misccommands.cfg
29cfg_file=/etc/nagios3/base.cfg
30cfg_file=/etc/nagios3/contacts.cfg
31cfg_file=/etc/nagios3/hostgroups.cfg
32cfg_file=/etc/nagios3/hosts.cfg
33cfg_file=/etc/nagios3/services.cfg
34
35cfg_file=/etc/nagios3/xvm.cfg
36
37
38# OBJECT CACHE FILE
39# This option determines where object definitions are cached when
40# Nagios starts/restarts.  The CGIs read object definitions from
41# this cache file (rather than looking at the object config files
42# directly) in order to prevent inconsistencies that can occur
43# when the config files are modified after Nagios starts.
44
45object_cache_file=/var/cache/nagios3/objects.cache
46
47
48
49# PRE-CACHED OBJECT FILE
50# This options determines the location of the precached object file.
51# If you run Nagios with the -p command line option, it will preprocess
52# your object configuration file(s) and write the cached config to this
53# file.  You can then start Nagios with the -u option to have it read
54# object definitions from this precached file, rather than the standard
55# object configuration files (see the cfg_file and cfg_dir options above).
56# Using a precached object file can speed up the time needed to (re)start
57# the Nagios process if you've got a large and/or complex configuration.
58# Read the documentation section on optimizing Nagios to find our more
59# about how this feature works.
60
61precached_object_file=/var/lib/nagios3/objects.precache
62
63
64
65# RESOURCE FILE
66# This is an optional resource file that contains $USERx$ macro
67# definitions. Multiple resource files can be specified by using
68# multiple resource_file definitions.  The CGIs will not attempt to
69# read the contents of resource files, so information that is
70# considered to be sensitive (usernames, passwords, etc) can be
71# defined as macros in this file and restrictive permissions (600)
72# can be placed on this file.
73
74resource_file=/etc/nagios3/private/resource.cfg
75
76
77
78# STATUS FILE
79# This is where the current status of all monitored services and
80# hosts is stored.  Its contents are read and processed by the CGIs.
81# The contents of the status file are deleted every time Nagios
82#  restarts.
83
84status_file=/var/cache/nagios3/status.dat
85
86
87
88# STATUS FILE UPDATE INTERVAL
89# This option determines the frequency (in seconds) that
90# Nagios will periodically dump program, host, and
91# service status data.
92
93status_update_interval=10
94
95
96
97# NAGIOS USER
98# This determines the effective user that Nagios should run as. 
99# You can either supply a username or a UID.
100
101nagios_user=nagios
102
103
104
105# NAGIOS GROUP
106# This determines the effective group that Nagios should run as. 
107# You can either supply a group name or a GID.
108
109nagios_group=nagios
110
111
112
113# EXTERNAL COMMAND OPTION
114# This option allows you to specify whether or not Nagios should check
115# for external commands (in the command file defined below).  By default
116# Nagios will *not* check for external commands, just to be on the
117# cautious side.  If you want to be able to use the CGI command interface
118# you will have to enable this.
119# Values: 0 = disable commands, 1 = enable commands
120
121check_external_commands=1
122
123
124
125# EXTERNAL COMMAND CHECK INTERVAL
126# This is the interval at which Nagios should check for external commands.
127# This value works of the interval_length you specify later.  If you leave
128# that at its default value of 60 (seconds), a value of 1 here will cause
129# Nagios to check for external commands every minute.  If you specify a
130# number followed by an "s" (i.e. 15s), this will be interpreted to mean
131# actual seconds rather than a multiple of the interval_length variable.
132# Note: In addition to reading the external command file at regularly
133# scheduled intervals, Nagios will also check for external commands after
134# event handlers are executed.
135# NOTE: Setting this value to -1 causes Nagios to check the external
136# command file as often as possible.
137
138#command_check_interval=15s
139command_check_interval=-1
140
141
142
143# EXTERNAL COMMAND FILE
144# This is the file that Nagios checks for external command requests.
145# It is also where the command CGI will write commands that are submitted
146# by users, so it must be writeable by the user that the web server
147# is running as (usually 'nobody').  Permissions should be set at the
148# directory level instead of on the file, as the file is deleted every
149# time its contents are processed.
150# Debian Users: In case you didn't read README.Debian yet, _NOW_ is the
151# time to do it.
152
153command_file=/var/lib/nagios3/rw/nagios.cmd
154
155
156
157# EXTERNAL COMMAND BUFFER SLOTS
158# This settings is used to tweak the number of items or "slots" that
159# the Nagios daemon should allocate to the buffer that holds incoming
160# external commands before they are processed.  As external commands
161# are processed by the daemon, they are removed from the buffer. 
162
163external_command_buffer_slots=4096
164
165
166
167# LOCK FILE
168# This is the lockfile that Nagios will use to store its PID number
169# in when it is running in daemon mode.
170
171lock_file=/var/run/nagios3/nagios3.pid
172
173
174
175# TEMP FILE
176# This is a temporary file that is used as scratch space when Nagios
177# updates the status log, cleans the comment file, etc.  This file
178# is created, used, and deleted throughout the time that Nagios is
179# running.
180
181temp_file=/var/cache/nagios3/nagios.tmp
182
183
184
185# TEMP PATH
186# This is path where Nagios can create temp files for service and
187# host check results, etc.
188
189temp_path=/tmp
190
191
192
193# EVENT BROKER OPTIONS
194# Controls what (if any) data gets sent to the event broker.
195# Values:  0      = Broker nothing
196#         -1      = Broker everything
197#         <other> = See documentation
198
199event_broker_options=-1
200
201
202
203# EVENT BROKER MODULE(S)
204# This directive is used to specify an event broker module that should
205# by loaded by Nagios at startup.  Use multiple directives if you want
206# to load more than one module.  Arguments that should be passed to
207# the module at startup are seperated from the module path by a space.
208#
209#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
210# WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING
211#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
212#
213# Do NOT overwrite modules while they are being used by Nagios or Nagios
214# will crash in a fiery display of SEGFAULT glory.  This is a bug/limitation
215# either in dlopen(), the kernel, and/or the filesystem.  And maybe Nagios...
216#
217# The correct/safe way of updating a module is by using one of these methods:
218#    1. Shutdown Nagios, replace the module file, restart Nagios
219#    2. Delete the original module file, move the new module file into place, restart Nagios
220#
221# Example:
222#
223#   broker_module=<modulepath> [moduleargs]
224
225#broker_module=/somewhere/module1.o
226#broker_module=/somewhere/module2.o arg1 arg2=3 debug=0
227
228
229
230# LOG ROTATION METHOD
231# This is the log rotation method that Nagios should use to rotate
232# the main log file. Values are as follows..
233#       n       = None - don't rotate the log
234#       h       = Hourly rotation (top of the hour)
235#       d       = Daily rotation (midnight every day)
236#       w       = Weekly rotation (midnight on Saturday evening)
237#       m       = Monthly rotation (midnight last day of month)
238
239log_rotation_method=d
240
241
242
243# LOG ARCHIVE PATH
244# This is the directory where archived (rotated) log files should be
245# placed (assuming you've chosen to do log rotation).
246
247log_archive_path=/var/log/nagios3/archives
248
249
250
251# LOGGING OPTIONS
252# If you want messages logged to the syslog facility, as well as the
253# Nagios log file set this option to 1.  If not, set it to 0.
254
255use_syslog=0
256
257
258
259# NOTIFICATION LOGGING OPTION
260# If you don't want notifications to be logged, set this value to 0.
261# If notifications should be logged, set the value to 1.
262
263log_notifications=1
264
265
266
267# SERVICE RETRY LOGGING OPTION
268# If you don't want service check retries to be logged, set this value
269# to 0.  If retries should be logged, set the value to 1.
270
271log_service_retries=1
272
273
274
275# HOST RETRY LOGGING OPTION
276# If you don't want host check retries to be logged, set this value to
277# 0.  If retries should be logged, set the value to 1.
278
279log_host_retries=1
280
281
282
283# EVENT HANDLER LOGGING OPTION
284# If you don't want host and service event handlers to be logged, set
285# this value to 0.  If event handlers should be logged, set the value
286# to 1.
287
288log_event_handlers=1
289
290
291
292# INITIAL STATES LOGGING OPTION
293# If you want Nagios to log all initial host and service states to
294# the main log file (the first time the service or host is checked)
295# you can enable this option by setting this value to 1.  If you
296# are not using an external application that does long term state
297# statistics reporting, you do not need to enable this option.  In
298# this case, set the value to 0.
299
300log_initial_states=0
301
302
303
304# EXTERNAL COMMANDS LOGGING OPTION
305# If you don't want Nagios to log external commands, set this value
306# to 0.  If external commands should be logged, set this value to 1.
307# Note: This option does not include logging of passive service
308# checks - see the option below for controlling whether or not
309# passive checks are logged.
310
311log_external_commands=1
312
313
314
315# PASSIVE CHECKS LOGGING OPTION
316# If you don't want Nagios to log passive host and service checks, set
317# this value to 0.  If passive checks should be logged, set
318# this value to 1.
319
320log_passive_checks=1
321
322
323
324# GLOBAL HOST AND SERVICE EVENT HANDLERS
325# These options allow you to specify a host and service event handler
326# command that is to be run for every host or service state change.
327# The global event handler is executed immediately prior to the event
328# handler that you have optionally specified in each host or
329# service definition. The command argument is the short name of a
330# command definition that you define in your host configuration file.
331# Read the HTML docs for more information.
332
333#global_host_event_handler=somecommand
334#global_service_event_handler=somecommand
335
336
337
338# SERVICE INTER-CHECK DELAY METHOD
339# This is the method that Nagios should use when initially
340# "spreading out" service checks when it starts monitoring.  The
341# default is to use smart delay calculation, which will try to
342# space all service checks out evenly to minimize CPU load.
343# Using the dumb setting will cause all checks to be scheduled
344# at the same time (with no delay between them)!  This is not a
345# good thing for production, but is useful when testing the
346# parallelization functionality.
347#       n       = None - don't use any delay between checks
348#       d       = Use a "dumb" delay of 1 second between checks
349#       s       = Use "smart" inter-check delay calculation
350#       x.xx    = Use an inter-check delay of x.xx seconds
351
352service_inter_check_delay_method=s
353
354
355
356# MAXIMUM SERVICE CHECK SPREAD
357# This variable determines the timeframe (in minutes) from the
358# program start time that an initial check of all services should
359# be completed.  Default is 30 minutes.
360
361max_service_check_spread=30
362
363
364
365# SERVICE CHECK INTERLEAVE FACTOR
366# This variable determines how service checks are interleaved.
367# Interleaving the service checks allows for a more even
368# distribution of service checks and reduced load on remote
369# hosts.  Setting this value to 1 is equivalent to how versions
370# of Nagios previous to 0.0.5 did service checks.  Set this
371# value to s (smart) for automatic calculation of the interleave
372# factor unless you have a specific reason to change it.
373#       s       = Use "smart" interleave factor calculation
374#       x       = Use an interleave factor of x, where x is a
375#                 number greater than or equal to 1.
376
377service_interleave_factor=s
378
379
380
381# HOST INTER-CHECK DELAY METHOD
382# This is the method that Nagios should use when initially
383# "spreading out" host checks when it starts monitoring.  The
384# default is to use smart delay calculation, which will try to
385# space all host checks out evenly to minimize CPU load.
386# Using the dumb setting will cause all checks to be scheduled
387# at the same time (with no delay between them)!
388#       n       = None - don't use any delay between checks
389#       d       = Use a "dumb" delay of 1 second between checks
390#       s       = Use "smart" inter-check delay calculation
391#       x.xx    = Use an inter-check delay of x.xx seconds
392
393host_inter_check_delay_method=s
394
395
396
397# MAXIMUM HOST CHECK SPREAD
398# This variable determines the timeframe (in minutes) from the
399# program start time that an initial check of all hosts should
400# be completed.  Default is 30 minutes.
401
402max_host_check_spread=30
403
404
405
406# MAXIMUM CONCURRENT SERVICE CHECKS
407# This option allows you to specify the maximum number of
408# service checks that can be run in parallel at any given time.
409# Specifying a value of 1 for this variable essentially prevents
410# any service checks from being parallelized.  A value of 0
411# will not restrict the number of concurrent checks that are
412# being executed.
413
414max_concurrent_checks=0
415
416
417
418# HOST AND SERVICE CHECK REAPER FREQUENCY
419# This is the frequency (in seconds!) that Nagios will process
420# the results of host and service checks.
421
422check_result_reaper_frequency=10
423
424
425
426
427# MAX CHECK RESULT REAPER TIME
428# This is the max amount of time (in seconds) that  a single
429# check result reaper event will be allowed to run before
430# returning control back to Nagios so it can perform other
431# duties.
432
433max_check_result_reaper_time=30
434
435
436
437
438# CHECK RESULT PATH
439# This is directory where Nagios stores the results of host and
440# service checks that have not yet been processed.
441#
442# Note: Make sure that only one instance of Nagios has access
443# to this directory! 
444
445check_result_path=/var/lib/nagios3/spool/checkresults
446
447
448
449
450# MAX CHECK RESULT FILE AGE
451# This option determines the maximum age (in seconds) which check
452# result files are considered to be valid.  Files older than this
453# threshold will be mercilessly deleted without further processing.
454
455max_check_result_file_age=3600
456
457
458
459
460# CACHED HOST CHECK HORIZON
461# This option determines the maximum amount of time (in seconds)
462# that the state of a previous host check is considered current.
463# Cached host states (from host checks that were performed more
464# recently that the timeframe specified by this value) can immensely
465# improve performance in regards to the host check logic.
466# Too high of a value for this option may result in inaccurate host
467# states being used by Nagios, while a lower value may result in a
468# performance hit for host checks.  Use a value of 0 to disable host
469# check caching.
470
471cached_host_check_horizon=15
472
473
474
475# CACHED SERVICE CHECK HORIZON
476# This option determines the maximum amount of time (in seconds)
477# that the state of a previous service check is considered current.
478# Cached service states (from service checks that were performed more
479# recently that the timeframe specified by this value) can immensely
480# improve performance in regards to predictive dependency checks.
481# Use a value of 0 to disable service check caching.
482
483cached_service_check_horizon=15
484
485
486
487# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
488# This option determines whether or not Nagios will attempt to execute
489# checks of hosts when it predicts that future dependency logic test
490# may be needed.  These predictive checks can help ensure that your
491# host dependency logic works well.
492# Values:
493#  0 = Disable predictive checks
494#  1 = Enable predictive checks (default)
495
496enable_predictive_host_dependency_checks=1
497
498
499
500# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
501# This option determines whether or not Nagios will attempt to execute
502# checks of service when it predicts that future dependency logic test
503# may be needed.  These predictive checks can help ensure that your
504# service dependency logic works well.
505# Values:
506#  0 = Disable predictive checks
507#  1 = Enable predictive checks (default)
508
509enable_predictive_service_dependency_checks=1
510
511
512
513# SOFT STATE DEPENDENCIES
514# This option determines whether or not Nagios will use soft state
515# information when checking host and service dependencies. Normally
516# Nagios will only use the latest hard host or service state when
517# checking dependencies. If you want it to use the latest state (regardless
518# of whether its a soft or hard state type), enable this option.
519# Values:
520#  0 = Don't use soft state dependencies (default)
521#  1 = Use soft state dependencies
522
523soft_state_dependencies=0
524
525
526
527# TIME CHANGE ADJUSTMENT THRESHOLDS
528# These options determine when Nagios will react to detected changes
529# in system time (either forward or backwards).
530
531#time_change_threshold=900
532
533
534
535# AUTO-RESCHEDULING OPTION
536# This option determines whether or not Nagios will attempt to
537# automatically reschedule active host and service checks to
538# "smooth" them out over time.  This can help balance the load on
539# the monitoring server. 
540# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
541# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
542
543auto_reschedule_checks=0
544
545
546
547# AUTO-RESCHEDULING INTERVAL
548# This option determines how often (in seconds) Nagios will
549# attempt to automatically reschedule checks.  This option only
550# has an effect if the auto_reschedule_checks option is enabled.
551# Default is 30 seconds.
552# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
553# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
554
555auto_rescheduling_interval=30
556
557
558
559# AUTO-RESCHEDULING WINDOW
560# This option determines the "window" of time (in seconds) that
561# Nagios will look at when automatically rescheduling checks.
562# Only host and service checks that occur in the next X seconds
563# (determined by this variable) will be rescheduled. This option
564# only has an effect if the auto_reschedule_checks option is
565# enabled.  Default is 180 seconds (3 minutes).
566# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
567# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
568
569auto_rescheduling_window=180
570
571
572
573# SLEEP TIME
574# This is the number of seconds to sleep between checking for system
575# events and service checks that need to be run.
576
577sleep_time=0.25
578
579
580
581# TIMEOUT VALUES
582# These options control how much time Nagios will allow various
583# types of commands to execute before killing them off.  Options
584# are available for controlling maximum time allotted for
585# service checks, host checks, event handlers, notifications, the
586# ocsp command, and performance data commands.  All values are in
587# seconds.
588
589service_check_timeout=60
590host_check_timeout=30
591event_handler_timeout=30
592notification_timeout=30
593ocsp_timeout=5
594perfdata_timeout=5
595
596
597
598# RETAIN STATE INFORMATION
599# This setting determines whether or not Nagios will save state
600# information for services and hosts before it shuts down.  Upon
601# startup Nagios will reload all saved service and host state
602# information before starting to monitor.  This is useful for
603# maintaining long-term data on state statistics, etc, but will
604# slow Nagios down a bit when it (re)starts.  Since its only
605# a one-time penalty, I think its well worth the additional
606# startup delay.
607
608retain_state_information=1
609
610
611
612# STATE RETENTION FILE
613# This is the file that Nagios should use to store host and
614# service state information before it shuts down.  The state
615# information in this file is also read immediately prior to
616# starting to monitor the network when Nagios is restarted.
617# This file is used only if the preserve_state_information
618# variable is set to 1.
619
620state_retention_file=/var/lib/nagios3/retention.dat
621
622
623
624# RETENTION DATA UPDATE INTERVAL
625# This setting determines how often (in minutes) that Nagios
626# will automatically save retention data during normal operation.
627# If you set this value to 0, Nagios will not save retention
628# data at regular interval, but it will still save retention
629# data before shutting down or restarting.  If you have disabled
630# state retention, this option has no effect.
631
632retention_update_interval=60
633
634
635
636# USE RETAINED PROGRAM STATE
637# This setting determines whether or not Nagios will set
638# program status variables based on the values saved in the
639# retention file.  If you want to use retained program status
640# information, set this value to 1.  If not, set this value
641# to 0.
642
643use_retained_program_state=1
644
645
646
647# USE RETAINED SCHEDULING INFO
648# This setting determines whether or not Nagios will retain
649# the scheduling info (next check time) for hosts and services
650# based on the values saved in the retention file.  If you
651# If you want to use retained scheduling info, set this
652# value to 1.  If not, set this value to 0.
653
654use_retained_scheduling_info=1
655
656
657
658# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
659# The following variables are used to specify specific host and
660# service attributes that should *not* be retained by Nagios during
661# program restarts.
662#
663# The values of the masks are bitwise ANDs of values specified
664# by the "MODATTR_" definitions found in include/common.h. 
665# For example, if you do not want the current enabled/disabled state
666# of flap detection and event handlers for hosts to be retained, you
667# would use a value of 24 for the host attribute mask...
668# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24
669
670# This mask determines what host attributes are not retained
671retained_host_attribute_mask=0
672
673# This mask determines what service attributes are not retained
674retained_service_attribute_mask=0
675
676# These two masks determine what process attributes are not retained.
677# There are two masks, because some process attributes have host and service
678# options.  For example, you can disable active host checks, but leave active
679# service checks enabled.
680retained_process_host_attribute_mask=0
681retained_process_service_attribute_mask=0
682
683# These two masks determine what contact attributes are not retained.
684# There are two masks, because some contact attributes have host and
685# service options.  For example, you can disable host notifications for
686# a contact, but leave service notifications enabled for them.
687retained_contact_host_attribute_mask=0
688retained_contact_service_attribute_mask=0
689
690
691
692# INTERVAL LENGTH
693# This is the seconds per unit interval as used in the
694# host/contact/service configuration files.  Setting this to 60 means
695# that each interval is one minute long (60 seconds).  Other settings
696# have not been tested much, so your mileage is likely to vary...
697
698interval_length=30
699
700
701
702# AGGRESSIVE HOST CHECKING OPTION
703# If you don't want to turn on aggressive host checking features, set
704# this value to 0 (the default).  Otherwise set this value to 1 to
705# enable the aggressive check option.  Read the docs for more info
706# on what aggressive host check is or check out the source code in
707# base/checks.c
708
709use_aggressive_host_checking=0
710
711
712
713# SERVICE CHECK EXECUTION OPTION
714# This determines whether or not Nagios will actively execute
715# service checks when it initially starts.  If this option is
716# disabled, checks are not actively made, but Nagios can still
717# receive and process passive check results that come in.  Unless
718# you're implementing redundant hosts or have a special need for
719# disabling the execution of service checks, leave this enabled!
720# Values: 1 = enable checks, 0 = disable checks
721
722execute_service_checks=1
723
724
725
726# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
727# This determines whether or not Nagios will accept passive
728# service checks results when it initially (re)starts.
729# Values: 1 = accept passive checks, 0 = reject passive checks
730
731accept_passive_service_checks=1
732
733
734
735# HOST CHECK EXECUTION OPTION
736# This determines whether or not Nagios will actively execute
737# host checks when it initially starts.  If this option is
738# disabled, checks are not actively made, but Nagios can still
739# receive and process passive check results that come in.  Unless
740# you're implementing redundant hosts or have a special need for
741# disabling the execution of host checks, leave this enabled!
742# Values: 1 = enable checks, 0 = disable checks
743
744execute_host_checks=1
745
746
747
748# PASSIVE HOST CHECK ACCEPTANCE OPTION
749# This determines whether or not Nagios will accept passive
750# host checks results when it initially (re)starts.
751# Values: 1 = accept passive checks, 0 = reject passive checks
752
753accept_passive_host_checks=1
754
755
756
757# NOTIFICATIONS OPTION
758# This determines whether or not Nagios will sent out any host or
759# service notifications when it is initially (re)started.
760# Values: 1 = enable notifications, 0 = disable notifications
761
762enable_notifications=1
763
764
765
766# EVENT HANDLER USE OPTION
767# This determines whether or not Nagios will run any host or
768# service event handlers when it is initially (re)started.  Unless
769# you're implementing redundant hosts, leave this option enabled.
770# Values: 1 = enable event handlers, 0 = disable event handlers
771
772enable_event_handlers=1
773
774
775
776# PROCESS PERFORMANCE DATA OPTION
777# This determines whether or not Nagios will process performance
778# data returned from service and host checks.  If this option is
779# enabled, host performance data will be processed using the
780# host_perfdata_command (defined below) and service performance
781# data will be processed using the service_perfdata_command (also
782# defined below).  Read the HTML docs for more information on
783# performance data.
784# Values: 1 = process performance data, 0 = do not process performance data
785
786process_performance_data=0
787
788
789
790# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
791# These commands are run after every host and service check is
792# performed.  These commands are executed only if the
793# enable_performance_data option (above) is set to 1.  The command
794# argument is the short name of a command definition that you
795# define in your host configuration file.  Read the HTML docs for
796# more information on performance data.
797
798#host_perfdata_command=process-host-perfdata
799#service_perfdata_command=process-service-perfdata
800
801
802
803# HOST AND SERVICE PERFORMANCE DATA FILES
804# These files are used to store host and service performance data.
805# Performance data is only written to these files if the
806# enable_performance_data option (above) is set to 1.
807
808#host_perfdata_file=/tmp/host-perfdata
809#service_perfdata_file=/tmp/service-perfdata
810
811
812
813# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
814# These options determine what data is written (and how) to the
815# performance data files.  The templates may contain macros, special
816# characters (\t for tab, \r for carriage return, \n for newline)
817# and plain text.  A newline is automatically added after each write
818# to the performance data file.  Some examples of what you can do are
819# shown below.
820
821#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
822#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
823
824
825
826# HOST AND SERVICE PERFORMANCE DATA FILE MODES
827# This option determines whether or not the host and service
828# performance data files are opened in write ("w") or append ("a")
829# mode. If you want to use named pipes, you should use the special
830# pipe ("p") mode which avoid blocking at startup, otherwise you will
831# likely want the defult append ("a") mode.
832
833#host_perfdata_file_mode=a
834#service_perfdata_file_mode=a
835
836
837
838# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
839# These options determine how often (in seconds) the host and service
840# performance data files are processed using the commands defined
841# below.  A value of 0 indicates the files should not be periodically
842# processed.
843
844#host_perfdata_file_processing_interval=0
845#service_perfdata_file_processing_interval=0
846
847
848
849# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
850# These commands are used to periodically process the host and
851# service performance data files.  The interval at which the
852# processing occurs is determined by the options above.
853
854#host_perfdata_file_processing_command=process-host-perfdata-file
855#service_perfdata_file_processing_command=process-service-perfdata-file
856
857
858
859# OBSESS OVER SERVICE CHECKS OPTION
860# This determines whether or not Nagios will obsess over service
861# checks and run the ocsp_command defined below.  Unless you're
862# planning on implementing distributed monitoring, do not enable
863# this option.  Read the HTML docs for more information on
864# implementing distributed monitoring.
865# Values: 1 = obsess over services, 0 = do not obsess (default)
866
867obsess_over_services=0
868
869
870
871# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
872# This is the command that is run for every service check that is
873# processed by Nagios.  This command is executed only if the
874# obsess_over_services option (above) is set to 1.  The command
875# argument is the short name of a command definition that you
876# define in your host configuration file. Read the HTML docs for
877# more information on implementing distributed monitoring.
878
879#ocsp_command=somecommand
880
881
882
883# OBSESS OVER HOST CHECKS OPTION
884# This determines whether or not Nagios will obsess over host
885# checks and run the ochp_command defined below.  Unless you're
886# planning on implementing distributed monitoring, do not enable
887# this option.  Read the HTML docs for more information on
888# implementing distributed monitoring.
889# Values: 1 = obsess over hosts, 0 = do not obsess (default)
890
891obsess_over_hosts=0
892
893
894
895# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
896# This is the command that is run for every host check that is
897# processed by Nagios.  This command is executed only if the
898# obsess_over_hosts option (above) is set to 1.  The command
899# argument is the short name of a command definition that you
900# define in your host configuration file. Read the HTML docs for
901# more information on implementing distributed monitoring.
902
903#ochp_command=somecommand
904
905
906
907# TRANSLATE PASSIVE HOST CHECKS OPTION
908# This determines whether or not Nagios will translate
909# DOWN/UNREACHABLE passive host check results into their proper
910# state for this instance of Nagios.  This option is useful
911# if you have distributed or failover monitoring setup.  In
912# these cases your other Nagios servers probably have a different
913# "view" of the network, with regards to the parent/child relationship
914# of hosts.  If a distributed monitoring server thinks a host
915# is DOWN, it may actually be UNREACHABLE from the point of
916# this Nagios instance.  Enabling this option will tell Nagios
917# to translate any DOWN or UNREACHABLE host states it receives
918# passively into the correct state from the view of this server.
919# Values: 1 = perform translation, 0 = do not translate (default)
920
921translate_passive_host_checks=0
922
923
924
925# PASSIVE HOST CHECKS ARE SOFT OPTION
926# This determines whether or not Nagios will treat passive host
927# checks as being HARD or SOFT.  By default, a passive host check
928# result will put a host into a HARD state type.  This can be changed
929# by enabling this option.
930# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT
931
932passive_host_checks_are_soft=0
933
934
935
936# ORPHANED HOST/SERVICE CHECK OPTIONS
937# These options determine whether or not Nagios will periodically
938# check for orphaned host service checks.  Since service checks are
939# not rescheduled until the results of their previous execution
940# instance are processed, there exists a possibility that some
941# checks may never get rescheduled.  A similar situation exists for
942# host checks, although the exact scheduling details differ a bit
943# from service checks.  Orphaned checks seem to be a rare
944# problem and should not happen under normal circumstances.
945# If you have problems with service checks never getting
946# rescheduled, make sure you have orphaned service checks enabled.
947# Values: 1 = enable checks, 0 = disable checks
948
949check_for_orphaned_services=1
950check_for_orphaned_hosts=1
951
952
953
954# SERVICE FRESHNESS CHECK OPTION
955# This option determines whether or not Nagios will periodically
956# check the "freshness" of service results.  Enabling this option
957# is useful for ensuring passive checks are received in a timely
958# manner.
959# Values: 1 = enabled freshness checking, 0 = disable freshness checking
960
961check_service_freshness=1
962
963
964
965# SERVICE FRESHNESS CHECK INTERVAL
966# This setting determines how often (in seconds) Nagios will
967# check the "freshness" of service check results.  If you have
968# disabled service freshness checking, this option has no effect.
969
970service_freshness_check_interval=60
971
972
973
974# HOST FRESHNESS CHECK OPTION
975# This option determines whether or not Nagios will periodically
976# check the "freshness" of host results.  Enabling this option
977# is useful for ensuring passive checks are received in a timely
978# manner.
979# Values: 1 = enabled freshness checking, 0 = disable freshness checking
980
981check_host_freshness=0
982
983
984
985# HOST FRESHNESS CHECK INTERVAL
986# This setting determines how often (in seconds) Nagios will
987# check the "freshness" of host check results.  If you have
988# disabled host freshness checking, this option has no effect.
989
990host_freshness_check_interval=60
991
992
993
994
995# ADDITIONAL FRESHNESS THRESHOLD LATENCY
996# This setting determines the number of seconds that Nagios
997# will add to any host and service freshness thresholds that
998# it calculates (those not explicitly specified by the user).
999
1000additional_freshness_latency=15
1001
1002
1003
1004
1005# FLAP DETECTION OPTION
1006# This option determines whether or not Nagios will try
1007# and detect hosts and services that are "flapping". 
1008# Flapping occurs when a host or service changes between
1009# states too frequently.  When Nagios detects that a
1010# host or service is flapping, it will temporarily suppress
1011# notifications for that host/service until it stops
1012# flapping.  Flap detection is very experimental, so read
1013# the HTML documentation before enabling this feature!
1014# Values: 1 = enable flap detection
1015#         0 = disable flap detection (default)
1016
1017enable_flap_detection=1
1018
1019
1020
1021# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
1022# Read the HTML documentation on flap detection for
1023# an explanation of what this option does.  This option
1024# has no effect if flap detection is disabled.
1025
1026low_service_flap_threshold=5.0
1027high_service_flap_threshold=20.0
1028low_host_flap_threshold=5.0
1029high_host_flap_threshold=20.0
1030
1031
1032
1033# DATE FORMAT OPTION
1034# This option determines how short dates are displayed. Valid options
1035# include:
1036#       us              (MM-DD-YYYY HH:MM:SS)
1037#       euro            (DD-MM-YYYY HH:MM:SS)
1038#       iso8601         (YYYY-MM-DD HH:MM:SS)
1039#       strict-iso8601  (YYYY-MM-DDTHH:MM:SS)
1040#
1041
1042date_format=iso8601
1043
1044
1045
1046
1047# TIMEZONE OFFSET
1048# This option is used to override the default timezone that this
1049# instance of Nagios runs in.  If not specified, Nagios will use
1050# the system configured timezone.
1051#
1052# NOTE: In order to display the correct timezone in the CGIs, you
1053# will also need to alter the Apache directives for the CGI path
1054# to include your timezone.  Example:
1055#
1056#   <Directory "/usr/local/nagios/sbin/">
1057#      SetEnv TZ "Australia/Brisbane"
1058#      ...
1059#   </Directory>
1060
1061#use_timezone=US/Mountain
1062#use_timezone=Australia/Brisbane
1063
1064
1065
1066
1067# P1.PL FILE LOCATION
1068# This value determines where the p1.pl perl script (used by the
1069# embedded Perl interpreter) is located.  If you didn't compile
1070# Nagios with embedded Perl support, this option has no effect.
1071
1072p1_file=/usr/lib/nagios3/p1.pl
1073
1074
1075
1076# EMBEDDED PERL INTERPRETER OPTION
1077# This option determines whether or not the embedded Perl interpreter
1078# will be enabled during runtime.  This option has no effect if Nagios
1079# has not been compiled with support for embedded Perl.
1080# Values: 0 = disable interpreter, 1 = enable interpreter
1081
1082enable_embedded_perl=1
1083
1084
1085
1086# EMBEDDED PERL USAGE OPTION
1087# This option determines whether or not Nagios will process Perl plugins
1088# and scripts with the embedded Perl interpreter if the plugins/scripts
1089# do not explicitly indicate whether or not it is okay to do so. Read
1090# the HTML documentation on the embedded Perl interpreter for more
1091# information on how this option works.
1092
1093use_embedded_perl_implicitly=1
1094
1095
1096
1097# ILLEGAL OBJECT NAME CHARACTERS
1098# This option allows you to specify illegal characters that cannot
1099# be used in host names, service descriptions, or names of other
1100# object types.
1101
1102illegal_object_name_chars=`~!$%^&*|'"<>?,()=
1103
1104
1105
1106# ILLEGAL MACRO OUTPUT CHARACTERS
1107# This option allows you to specify illegal characters that are
1108# stripped from macros before being used in notifications, event
1109# handlers, etc.  This DOES NOT affect macros used in service or
1110# host check commands.
1111# The following macros are stripped of the characters you specify:
1112#       $HOSTOUTPUT$
1113#       $HOSTPERFDATA$
1114#       $HOSTACKAUTHOR$
1115#       $HOSTACKCOMMENT$
1116#       $SERVICEOUTPUT$
1117#       $SERVICEPERFDATA$
1118#       $SERVICEACKAUTHOR$
1119#       $SERVICEACKCOMMENT$
1120
1121illegal_macro_output_chars=`~$&|'"<>
1122
1123
1124
1125# REGULAR EXPRESSION MATCHING
1126# This option controls whether or not regular expression matching
1127# takes place in the object config files.  Regular expression
1128# matching is used to match host, hostgroup, service, and service
1129# group names/descriptions in some fields of various object types.
1130# Values: 1 = enable regexp matching, 0 = disable regexp matching
1131
1132use_regexp_matching=0
1133
1134
1135
1136# "TRUE" REGULAR EXPRESSION MATCHING
1137# This option controls whether or not "true" regular expression
1138# matching takes place in the object config files.  This option
1139# only has an effect if regular expression matching is enabled
1140# (see above).  If this option is DISABLED, regular expression
1141# matching only occurs if a string contains wildcard characters
1142# (* and ?).  If the option is ENABLED, regexp matching occurs
1143# all the time (which can be annoying).
1144# Values: 1 = enable true matching, 0 = disable true matching
1145
1146use_true_regexp_matching=0
1147
1148
1149
1150# ADMINISTRATOR EMAIL/PAGER ADDRESSES
1151# The email and pager address of a global administrator (likely you).
1152# Nagios never uses these values itself, but you can access them by
1153# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
1154# commands.
1155
1156admin_email=sipb-nagios@mit.edu
1157admin_pager=sipb-nagios@mit.edu
1158
1159
1160
1161# DAEMON CORE DUMP OPTION
1162# This option determines whether or not Nagios is allowed to create
1163# a core dump when it runs as a daemon.  Note that it is generally
1164# considered bad form to allow this, but it may be useful for
1165# debugging purposes.  Enabling this option doesn't guarantee that
1166# a core file will be produced, but that's just life...
1167# Values: 1 - Allow core dumps
1168#         0 - Do not allow core dumps (default)
1169
1170daemon_dumps_core=0
1171
1172
1173
1174# LARGE INSTALLATION TWEAKS OPTION
1175# This option determines whether or not Nagios will take some shortcuts
1176# which can save on memory and CPU usage in large Nagios installations.
1177# Read the documentation for more information on the benefits/tradeoffs
1178# of enabling this option.
1179# Values: 1 - Enabled tweaks
1180#         0 - Disable tweaks (default)
1181
1182use_large_installation_tweaks=0
1183
1184
1185
1186# ENABLE ENVIRONMENT MACROS
1187# This option determines whether or not Nagios will make all standard
1188# macros available as environment variables when host/service checks
1189# and system commands (event handlers, notifications, etc.) are
1190# executed.  Enabling this option can cause performance issues in
1191# large installations, as it will consume a bit more memory and (more
1192# importantly) consume more CPU.
1193# Values: 1 - Enable environment variable macros (default)
1194#         0 - Disable environment variable macros
1195
1196enable_environment_macros=1
1197
1198
1199
1200# CHILD PROCESS MEMORY OPTION
1201# This option determines whether or not Nagios will free memory in
1202# child processes (processed used to execute system commands and host/
1203# service checks).  If you specify a value here, it will override
1204# program defaults.
1205# Value: 1 - Free memory in child processes
1206#        0 - Do not free memory in child processes
1207
1208#free_child_process_memory=1
1209
1210
1211
1212# CHILD PROCESS FORKING BEHAVIOR
1213# This option determines how Nagios will fork child processes
1214# (used to execute system commands and host/service checks).  Normally
1215# child processes are fork()ed twice, which provides a very high level
1216# of isolation from problems.  Fork()ing once is probably enough and will
1217# save a great deal on CPU usage (in large installs), so you might
1218# want to consider using this.  If you specify a value here, it will
1219# program defaults.
1220# Value: 1 - Child processes fork() twice
1221#        0 - Child processes fork() just once
1222
1223#child_processes_fork_twice=1
1224
1225
1226
1227# DEBUG LEVEL
1228# This option determines how much (if any) debugging information will
1229# be written to the debug file.  OR values together to log multiple
1230# types of information.
1231# Values:
1232#          -1 = Everything
1233#          0 = Nothing
1234#          1 = Functions
1235#          2 = Configuration
1236#          4 = Process information
1237#          8 = Scheduled events
1238#          16 = Host/service checks
1239#          32 = Notifications
1240#          64 = Event broker
1241#          128 = External commands
1242#          256 = Commands
1243#          512 = Scheduled downtime
1244#          1024 = Comments
1245#          2048 = Macros
1246
1247debug_level=0
1248
1249
1250
1251# DEBUG VERBOSITY
1252# This option determines how verbose the debug log out will be.
1253# Values: 0 = Brief output
1254#         1 = More detailed
1255#         2 = Very detailed
1256
1257debug_verbosity=1
1258
1259
1260
1261# DEBUG FILE
1262# This option determines where Nagios should write debugging information.
1263
1264debug_file=/var/lib/nagios3/nagios.debug
1265
1266
1267
1268# MAX DEBUG FILE SIZE
1269# This option determines the maximum size (in bytes) of the debug file.  If
1270# the file grows larger than this size, it will be renamed with a .old
1271# extension.  If a file already exists with a .old extension it will
1272# automatically be deleted.  This helps ensure your disk space usage doesn't
1273# get out of control when debugging Nagios.
1274
1275max_debug_file_size=1000000
1276
1277
Note: See TracBrowser for help on using the repository browser.