source: branches/fc11-dev/noc/nagios/nagios.cfg @ 1258

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