source: noc/nagios/nagios.cfg @ 923

Last change on this file since 923 was 898, checked in by quentin, 15 years ago
Include XVM Nagios configuration
File size: 29.6 KB
Line 
1##############################################################################
2#
3# NAGIOS.CFG - Main Config File for Nagios
4#
5##############################################################################
6
7
8# LOG FILE
9# This is the main log file where service and host events are logged
10# for historical purposes.  This should be the first option specified
11# in the config file!!!
12
13log_file=/var/log/nagios2/nagios.log
14
15
16
17# OBJECT CONFIGURATION FILE(S)
18# This is the configuration file in which you define hosts, host
19# groups, contacts, contact groups, services, etc.  I guess it would
20# be better called an object definition file, but for historical
21# reasons it isn't.  You can split object definitions into several
22# different config files by using multiple cfg_file statements here.
23# Nagios will read and process all the config files you define.
24# This can be very useful if you want to keep command definitions
25# separate from host and contact definitions...
26
27# Plugin commands (service and host check commands)
28# Arguments are likely to change between different releases of the
29# plugins, so you should use the same config file provided with the
30# plugin release rather than the one provided with Nagios.
31cfg_file=/etc/nagios2/checkcommands.cfg
32
33# Debian also defaults to using the check commands defined by the debian
34# nagios-plugins package
35cfg_dir=/etc/nagios-plugins/config
36
37# Misc commands (notification and event handler commands, etc)
38cfg_file=/etc/nagios2/misccommands.cfg
39
40# You can split other types of object definitions across several
41# config files if you wish (as done here), or keep them all in a
42# single config file.
43
44cfg_file=/etc/nagios2/base.cfg
45cfg_file=/etc/nagios2/contacts.cfg
46cfg_file=/etc/nagios2/hostgroups.cfg
47cfg_file=/etc/nagios2/hosts.cfg
48cfg_file=/etc/nagios2/services.cfg
49
50cfg_file=/etc/nagios2/xvm.cfg
51#cfg_file=/etc/nagios2/test.cfg
52
53
54
55# OBJECT CACHE FILE
56# This option determines where object definitions are cached when
57# Nagios starts/restarts.  The CGIs read object definitions from
58# this cache file (rather than looking at the object config files
59# directly) in order to prevent inconsistencies that can occur
60# when the config files are modified after Nagios starts.
61
62object_cache_file=/var/cache/nagios2/objects.cache
63
64
65
66# RESOURCE FILE
67# This is an optional resource file that contains $USERx$ macro
68# definitions. Multiple resource files can be specified by using
69# multiple resource_file definitions.  The CGIs will not attempt to
70# read the contents of resource files, so information that is
71# considered to be sensitive (usernames, passwords, etc) can be
72# defined as macros in this file and restrictive permissions (600)
73# can be placed on this file.
74
75resource_file=/etc/nagios2/private/resource.cfg
76
77
78
79# STATUS FILE
80# This is where the current status of all monitored services and
81# hosts is stored.  Its contents are read and processed by the CGIs.
82# The contents of the status file are deleted every time Nagios
83#  restarts.
84
85status_file=/var/cache/nagios2/status.dat
86
87
88
89# NAGIOS USER
90# This determines the effective user that Nagios should run as. 
91# You can either supply a username or a UID.
92
93nagios_user=nagios
94
95
96
97# NAGIOS GROUP
98# This determines the effective group that Nagios should run as. 
99# You can either supply a group name or a GID.
100
101nagios_group=nagios
102
103
104
105# EXTERNAL COMMAND OPTION
106# This option allows you to specify whether or not Nagios should check
107# for external commands (in the command file defined below).  By default
108# Nagios will *not* check for external commands, just to be on the
109# cautious side.  If you want to be able to use the CGI command interface
110# you will have to enable this.  Setting this value to 0 disables command
111# checking (the default), other values enable it.
112
113check_external_commands=1
114
115
116
117# EXTERNAL COMMAND CHECK INTERVAL
118# This is the interval at which Nagios should check for external commands.
119# This value works of the interval_length you specify later.  If you leave
120# that at its default value of 60 (seconds), a value of 1 here will cause
121# Nagios to check for external commands every minute.  If you specify a
122# number followed by an "s" (i.e. 15s), this will be interpreted to mean
123# actual seconds rather than a multiple of the interval_length variable.
124# Note: In addition to reading the external command file at regularly
125# scheduled intervals, Nagios will also check for external commands after
126# event handlers are executed.
127# NOTE: Setting this value to -1 causes Nagios to check the external
128# command file as often as possible.
129
130#command_check_interval=1
131command_check_interval=1s
132#command_check_interval=-1
133
134
135
136# EXTERNAL COMMAND FILE
137# This is the file that Nagios checks for external command requests.
138# It is also where the command CGI will write commands that are submitted
139# by users, so it must be writeable by the user that the web server
140# is running as (usually 'nobody').  Permissions should be set at the
141# directory level instead of on the file, as the file is deleted every
142# time its contents are processed.
143# Debian Users: In case you didn't read README.Debian yet, _NOW_ is the
144# time to do it.
145
146command_file=/var/lib/nagios2/rw/nagios.cmd
147
148
149
150# COMMENT FILE
151# This is the file that Nagios will use for storing host and service
152# comments.
153
154comment_file=/var/lib/nagios2/comments.dat
155
156
157
158# DOWNTIME FILE
159# This is the file that Nagios will use for storing host and service
160# downtime data.
161
162downtime_file=/var/lib/nagios2/downtime.dat
163
164
165
166# LOCK FILE
167# This is the lockfile that Nagios will use to store its PID number
168# in when it is running in daemon mode.
169
170lock_file=/var/run/nagios2/nagios2.pid
171
172
173
174# TEMP FILE
175# This is a temporary file that is used as scratch space when Nagios
176# updates the status log, cleans the comment file, etc.  This file
177# is created, used, and deleted throughout the time that Nagios is
178# running.
179
180temp_file=/var/cache/nagios2/nagios.tmp
181
182
183
184# EVENT BROKER OPTIONS
185# Controls what (if any) data gets sent to the event broker.
186# Values:  0      = Broker nothing
187#         -1      = Broker everything
188#         <other> = See documentation
189
190event_broker_options=-1
191
192
193
194# EVENT BROKER MODULE(S)
195# This directive is used to specify an event broker module that should
196# by loaded by Nagios at startup.  Use multiple directives if you want
197# to load more than one module.  Arguments that should be passed to
198# the module at startup are seperated from the module path by a space.
199#
200# Example:
201#
202#   broker_module=<modulepath> [moduleargs]
203
204#broker_module=/somewhere/module1.o
205#broker_module=/somewhere/module2.o arg1 arg2=3 debug=0
206
207
208
209
210# LOG ROTATION METHOD
211# This is the log rotation method that Nagios should use to rotate
212# the main log file. Values are as follows..
213#       n       = None - don't rotate the log
214#       h       = Hourly rotation (top of the hour)
215#       d       = Daily rotation (midnight every day)
216#       w       = Weekly rotation (midnight on Saturday evening)
217#       m       = Monthly rotation (midnight last day of month)
218
219log_rotation_method=d
220
221
222
223# LOG ARCHIVE PATH
224# This is the directory where archived (rotated) log files should be
225# placed (assuming you've chosen to do log rotation).
226
227log_archive_path=/var/log/nagios2/archives
228
229
230
231# LOGGING OPTIONS
232# If you want messages logged to the syslog facility, as well as the
233# NetAlarm log file set this option to 1.  If not, set it to 0.
234
235use_syslog=0
236
237
238
239# NOTIFICATION LOGGING OPTION
240# If you don't want notifications to be logged, set this value to 0.
241# If notifications should be logged, set the value to 1.
242
243log_notifications=1
244
245
246
247# SERVICE RETRY LOGGING OPTION
248# If you don't want service check retries to be logged, set this value
249# to 0.  If retries should be logged, set the value to 1.
250
251log_service_retries=1
252
253
254
255# HOST RETRY LOGGING OPTION
256# If you don't want host check retries to be logged, set this value to
257# 0.  If retries should be logged, set the value to 1.
258
259log_host_retries=1
260
261
262
263# EVENT HANDLER LOGGING OPTION
264# If you don't want host and service event handlers to be logged, set
265# this value to 0.  If event handlers should be logged, set the value
266# to 1.
267
268log_event_handlers=1
269
270
271
272# INITIAL STATES LOGGING OPTION
273# If you want Nagios to log all initial host and service states to
274# the main log file (the first time the service or host is checked)
275# you can enable this option by setting this value to 1.  If you
276# are not using an external application that does long term state
277# statistics reporting, you do not need to enable this option.  In
278# this case, set the value to 0.
279
280log_initial_states=0
281
282
283
284# EXTERNAL COMMANDS LOGGING OPTION
285# If you don't want Nagios to log external commands, set this value
286# to 0.  If external commands should be logged, set this value to 1.
287# Note: This option does not include logging of passive service
288# checks - see the option below for controlling whether or not
289# passive checks are logged.
290
291log_external_commands=1
292
293
294
295# PASSIVE CHECKS LOGGING OPTION
296# If you don't want Nagios to log passive host and service checks, set
297# this value to 0.  If passive checks should be logged, set
298# this value to 1.
299
300log_passive_checks=1
301
302
303
304# GLOBAL HOST AND SERVICE EVENT HANDLERS
305# These options allow you to specify a host and service event handler
306# command that is to be run for every host or service state change.
307# The global event handler is executed immediately prior to the event
308# handler that you have optionally specified in each host or
309# service definition. The command argument is the short name of a
310# command definition that you define in your host configuration file.
311# Read the HTML docs for more information.
312
313#global_host_event_handler=somecommand
314#global_service_event_handler=somecommand
315
316
317
318# SERVICE INTER-CHECK DELAY METHOD
319# This is the method that Nagios should use when initially
320# "spreading out" service checks when it starts monitoring.  The
321# default is to use smart delay calculation, which will try to
322# space all service checks out evenly to minimize CPU load.
323# Using the dumb setting will cause all checks to be scheduled
324# at the same time (with no delay between them)!  This is not a
325# good thing for production, but is useful when testing the
326# parallelization functionality.
327#       n       = None - don't use any delay between checks
328#       d       = Use a "dumb" delay of 1 second between checks
329#       s       = Use "smart" inter-check delay calculation
330#       x.xx    = Use an inter-check delay of x.xx seconds
331
332service_inter_check_delay_method=s
333
334
335
336# MAXIMUM SERVICE CHECK SPREAD
337# This variable determines the timeframe (in minutes) from the
338# program start time that an initial check of all services should
339# be completed.  Default is 30 minutes.
340
341max_service_check_spread=30
342
343
344
345# SERVICE CHECK INTERLEAVE FACTOR
346# This variable determines how service checks are interleaved.
347# Interleaving the service checks allows for a more even
348# distribution of service checks and reduced load on remote
349# hosts.  Setting this value to 1 is equivalent to how versions
350# of Nagios previous to 0.0.5 did service checks.  Set this
351# value to s (smart) for automatic calculation of the interleave
352# factor unless you have a specific reason to change it.
353#       s       = Use "smart" interleave factor calculation
354#       x       = Use an interleave factor of x, where x is a
355#                 number greater than or equal to 1.
356
357service_interleave_factor=s
358
359
360
361# HOST INTER-CHECK DELAY METHOD
362# This is the method that Nagios should use when initially
363# "spreading out" host checks when it starts monitoring.  The
364# default is to use smart delay calculation, which will try to
365# space all host checks out evenly to minimize CPU load.
366# Using the dumb setting will cause all checks to be scheduled
367# at the same time (with no delay between them)!
368#       n       = None - don't use any delay between checks
369#       d       = Use a "dumb" delay of 1 second between checks
370#       s       = Use "smart" inter-check delay calculation
371#       x.xx    = Use an inter-check delay of x.xx seconds
372
373host_inter_check_delay_method=s
374
375
376
377# MAXIMUM HOST CHECK SPREAD
378# This variable determines the timeframe (in minutes) from the
379# program start time that an initial check of all hosts should
380# be completed.  Default is 30 minutes.
381
382max_host_check_spread=30
383
384
385
386# MAXIMUM CONCURRENT SERVICE CHECKS
387# This option allows you to specify the maximum number of
388# service checks that can be run in parallel at any given time.
389# Specifying a value of 1 for this variable essentially prevents
390# any service checks from being parallelized.  A value of 0
391# will not restrict the number of concurrent checks that are
392# being executed.
393
394max_concurrent_checks=0
395
396
397
398# SERVICE CHECK REAPER FREQUENCY
399# This is the frequency (in seconds!) that Nagios will process
400# the results of services that have been checked.
401
402service_reaper_frequency=10
403
404
405
406
407# AUTO-RESCHEDULING OPTION
408# This option determines whether or not Nagios will attempt to
409# automatically reschedule active host and service checks to
410# "smooth" them out over time.  This can help balance the load on
411# the monitoring server. 
412# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
413# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
414
415auto_reschedule_checks=0
416
417
418
419# AUTO-RESCHEDULING INTERVAL
420# This option determines how often (in seconds) Nagios will
421# attempt to automatically reschedule checks.  This option only
422# has an effect if the auto_reschedule_checks option is enabled.
423# Default is 30 seconds.
424# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
425# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
426
427auto_rescheduling_interval=30
428
429
430
431
432# AUTO-RESCHEDULING WINDOW
433# This option determines the "window" of time (in seconds) that
434# Nagios will look at when automatically rescheduling checks.
435# Only host and service checks that occur in the next X seconds
436# (determined by this variable) will be rescheduled. This option
437# only has an effect if the auto_reschedule_checks option is
438# enabled.  Default is 180 seconds (3 minutes).
439# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
440# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
441
442auto_rescheduling_window=180
443
444
445
446# SLEEP TIME
447# This is the number of seconds to sleep between checking for system
448# events and service checks that need to be run.
449
450sleep_time=0.25
451
452
453
454# TIMEOUT VALUES
455# These options control how much time Nagios will allow various
456# types of commands to execute before killing them off.  Options
457# are available for controlling maximum time allotted for
458# service checks, host checks, event handlers, notifications, the
459# ocsp command, and performance data commands.  All values are in
460# seconds.
461
462service_check_timeout=60
463host_check_timeout=30
464event_handler_timeout=30
465notification_timeout=30
466ocsp_timeout=5
467perfdata_timeout=30
468
469
470
471# RETAIN STATE INFORMATION
472# This setting determines whether or not Nagios will save state
473# information for services and hosts before it shuts down.  Upon
474# startup Nagios will reload all saved service and host state
475# information before starting to monitor.  This is useful for
476# maintaining long-term data on state statistics, etc, but will
477# slow Nagios down a bit when it (re)starts.  Since its only
478# a one-time penalty, I think its well worth the additional
479# startup delay.
480
481retain_state_information=1
482
483
484
485# STATE RETENTION FILE
486# This is the file that Nagios should use to store host and
487# service state information before it shuts down.  The state
488# information in this file is also read immediately prior to
489# starting to monitor the network when Nagios is restarted.
490# This file is used only if the preserve_state_information
491# variable is set to 1.
492
493state_retention_file=/var/lib/nagios2/retention.dat
494
495
496
497# RETENTION DATA UPDATE INTERVAL
498# This setting determines how often (in minutes) that Nagios
499# will automatically save retention data during normal operation.
500# If you set this value to 0, Nagios will not save retention
501# data at regular interval, but it will still save retention
502# data before shutting down or restarting.  If you have disabled
503# state retention, this option has no effect.
504
505retention_update_interval=60
506
507
508
509# USE RETAINED PROGRAM STATE
510# This setting determines whether or not Nagios will set
511# program status variables based on the values saved in the
512# retention file.  If you want to use retained program status
513# information, set this value to 1.  If not, set this value
514# to 0.
515
516use_retained_program_state=1
517
518
519
520# USE RETAINED SCHEDULING INFO
521# This setting determines whether or not Nagios will retain
522# the scheduling info (next check time) for hosts and services
523# based on the values saved in the retention file.  If you
524# If you want to use retained scheduling info, set this
525# value to 1.  If not, set this value to 0.
526
527use_retained_scheduling_info=0
528
529
530
531# INTERVAL LENGTH
532# This is the seconds per unit interval as used in the
533# host/contact/service configuration files.  Setting this to 60 means
534# that each interval is one minute long (60 seconds).  Other settings
535# have not been tested much, so your mileage is likely to vary...
536
537interval_length=30
538
539
540
541# AGGRESSIVE HOST CHECKING OPTION
542# If you don't want to turn on aggressive host checking features, set
543# this value to 0 (the default).  Otherwise set this value to 1 to
544# enable the aggressive check option.  Read the docs for more info
545# on what aggressive host check is or check out the source code in
546# base/checks.c
547
548use_aggressive_host_checking=0
549
550
551
552# SERVICE CHECK EXECUTION OPTION
553# This determines whether or not Nagios will actively execute
554# service checks when it initially starts.  If this option is
555# disabled, checks are not actively made, but Nagios can still
556# receive and process passive check results that come in.  Unless
557# you're implementing redundant hosts or have a special need for
558# disabling the execution of service checks, leave this enabled!
559# Values: 1 = enable checks, 0 = disable checks
560
561execute_service_checks=1
562
563
564
565# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
566# This determines whether or not Nagios will accept passive
567# service checks results when it initially (re)starts.
568# Values: 1 = accept passive checks, 0 = reject passive checks
569
570accept_passive_service_checks=1
571
572
573
574# HOST CHECK EXECUTION OPTION
575# This determines whether or not Nagios will actively execute
576# host checks when it initially starts.  If this option is
577# disabled, checks are not actively made, but Nagios can still
578# receive and process passive check results that come in.  Unless
579# you're implementing redundant hosts or have a special need for
580# disabling the execution of host checks, leave this enabled!
581# Values: 1 = enable checks, 0 = disable checks
582
583execute_host_checks=1
584
585
586
587# PASSIVE HOST CHECK ACCEPTANCE OPTION
588# This determines whether or not Nagios will accept passive
589# host checks results when it initially (re)starts.
590# Values: 1 = accept passive checks, 0 = reject passive checks
591
592accept_passive_host_checks=1
593
594
595
596# NOTIFICATIONS OPTION
597# This determines whether or not Nagios will sent out any host or
598# service notifications when it is initially (re)started.
599# Values: 1 = enable notifications, 0 = disable notifications
600
601enable_notifications=1
602
603
604
605# EVENT HANDLER USE OPTION
606# This determines whether or not Nagios will run any host or
607# service event handlers when it is initially (re)started.  Unless
608# you're implementing redundant hosts, leave this option enabled.
609# Values: 1 = enable event handlers, 0 = disable event handlers
610
611enable_event_handlers=1
612
613
614
615# PROCESS PERFORMANCE DATA OPTION
616# This determines whether or not Nagios will process performance
617# data returned from service and host checks.  If this option is
618# enabled, host performance data will be processed using the
619# host_perfdata_command (defined below) and service performance
620# data will be processed using the service_perfdata_command (also
621# defined below).  Read the HTML docs for more information on
622# performance data.
623# Values: 1 = process performance data, 0 = do not process performance data
624
625process_performance_data=0
626
627
628
629# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
630# These commands are run after every host and service check is
631# performed.  These commands are executed only if the
632# enable_performance_data option (above) is set to 1.  The command
633# argument is the short name of a command definition that you
634# define in your host configuration file.  Read the HTML docs for
635# more information on performance data.
636
637#host_perfdata_command=process-host-perfdata
638#service_perfdata_command=process-service-perfdata
639
640
641
642# HOST AND SERVICE PERFORMANCE DATA FILES
643# These files are used to store host and service performance data.
644# Performance data is only written to these files if the
645# enable_performance_data option (above) is set to 1.
646
647#host_perfdata_file=/tmp/host-perfdata
648#service_perfdata_file=/tmp/service-perfdata
649
650
651
652# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
653# These options determine what data is written (and how) to the
654# performance data files.  The templates may contain macros, special
655# characters (\t for tab, \r for carriage return, \n for newline)
656# and plain text.  A newline is automatically added after each write
657# to the performance data file.  Some examples of what you can do are
658# shown below.
659
660#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
661#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
662
663
664
665
666# HOST AND SERVICE PERFORMANCE DATA FILE MODES
667# This option determines whether or not the host and service
668# performance data files are opened in write ("w") or append ("a")
669# mode.  Unless you are the files are named pipes, you will probably
670# want to use the default mode of append ("a").
671
672#host_perfdata_file_mode=a
673#service_perfdata_file_mode=a
674
675
676
677# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
678# These options determine how often (in seconds) the host and service
679# performance data files are processed using the commands defined
680# below.  A value of 0 indicates the files should not be periodically
681# processed.
682
683#host_perfdata_file_processing_interval=0
684#service_perfdata_file_processing_interval=0
685
686
687
688# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
689# These commands are used to periodically process the host and
690# service performance data files.  The interval at which the
691# processing occurs is determined by the options above.
692
693#host_perfdata_file_processing_command=process-host-perfdata-file
694#service_perfdata_file_processing_command=process-service-perfdata-file
695
696
697
698# OBSESS OVER SERVICE CHECKS OPTION
699# This determines whether or not Nagios will obsess over service
700# checks and run the ocsp_command defined below.  Unless you're
701# planning on implementing distributed monitoring, do not enable
702# this option.  Read the HTML docs for more information on
703# implementing distributed monitoring.
704# Values: 1 = obsess over services, 0 = do not obsess (default)
705
706obsess_over_services=0
707
708
709
710# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
711# This is the command that is run for every service check that is
712# processed by Nagios.  This command is executed only if the
713# obsess_over_service option (above) is set to 1.  The command
714# argument is the short name of a command definition that you
715# define in your host configuration file. Read the HTML docs for
716# more information on implementing distributed monitoring.
717
718#ocsp_command=somecommand
719
720
721
722# ORPHANED SERVICE CHECK OPTION
723# This determines whether or not Nagios will periodically
724# check for orphaned services.  Since service checks are not
725# rescheduled until the results of their previous execution
726# instance are processed, there exists a possibility that some
727# checks may never get rescheduled.  This seems to be a rare
728# problem and should not happen under normal circumstances.
729# If you have problems with service checks never getting
730# rescheduled, you might want to try enabling this option.
731# Values: 1 = enable checks, 0 = disable checks
732
733check_for_orphaned_services=0
734
735
736
737# SERVICE FRESHNESS CHECK OPTION
738# This option determines whether or not Nagios will periodically
739# check the "freshness" of service results.  Enabling this option
740# is useful for ensuring passive checks are received in a timely
741# manner.
742# Values: 1 = enabled freshness checking, 0 = disable freshness checking
743
744check_service_freshness=1
745
746
747
748# SERVICE FRESHNESS CHECK INTERVAL
749# This setting determines how often (in seconds) Nagios will
750# check the "freshness" of service check results.  If you have
751# disabled service freshness checking, this option has no effect.
752
753service_freshness_check_interval=60
754
755
756
757# HOST FRESHNESS CHECK OPTION
758# This option determines whether or not Nagios will periodically
759# check the "freshness" of host results.  Enabling this option
760# is useful for ensuring passive checks are received in a timely
761# manner.
762# Values: 1 = enabled freshness checking, 0 = disable freshness checking
763
764check_host_freshness=0
765
766
767
768# HOST FRESHNESS CHECK INTERVAL
769# This setting determines how often (in seconds) Nagios will
770# check the "freshness" of host check results.  If you have
771# disabled host freshness checking, this option has no effect.
772
773host_freshness_check_interval=60
774
775
776
777# AGGREGATED STATUS UPDATES
778# This option determines whether or not Nagios will
779# aggregate updates of host, service, and program status
780# data.  Normally, status data is updated immediately when
781# a change occurs.  This can result in high CPU loads if
782# you are monitoring a lot of services.  If you want Nagios
783# to only refresh status data every few seconds, disable
784# this option.
785# Values: 1 = enable aggregate updates, 0 = disable aggregate updates
786
787aggregate_status_updates=1
788
789
790
791# AGGREGATED STATUS UPDATE INTERVAL
792# Combined with the aggregate_status_updates option,
793# this option determines the frequency (in seconds!) that
794# Nagios will periodically dump program, host, and
795# service status data.  If you are not using aggregated
796# status data updates, this option has no effect.
797
798status_update_interval=15
799
800
801
802# FLAP DETECTION OPTION
803# This option determines whether or not Nagios will try
804# and detect hosts and services that are "flapping". 
805# Flapping occurs when a host or service changes between
806# states too frequently.  When Nagios detects that a
807# host or service is flapping, it will temporarily suppress
808# notifications for that host/service until it stops
809# flapping.  Flap detection is very experimental, so read
810# the HTML documentation before enabling this feature!
811# Values: 1 = enable flap detection
812#         0 = disable flap detection (default)
813
814enable_flap_detection=0
815
816
817
818# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
819# Read the HTML documentation on flap detection for
820# an explanation of what this option does.  This option
821# has no effect if flap detection is disabled.
822
823low_service_flap_threshold=5.0
824high_service_flap_threshold=20.0
825low_host_flap_threshold=5.0
826high_host_flap_threshold=20.0
827
828
829
830# DATE FORMAT OPTION
831# This option determines how short dates are displayed. Valid options
832# include:
833#       us              (MM-DD-YYYY HH:MM:SS)
834#       euro            (DD-MM-YYYY HH:MM:SS)
835#       iso8601         (YYYY-MM-DD HH:MM:SS)
836#       strict-iso8601  (YYYY-MM-DDTHH:MM:SS)
837#
838
839date_format=us
840
841
842
843# P1.PL FILE LOCATION
844# This value determines where the p1.pl perl script (used by the
845# embedded Perl interpreter) is located.  If you didn't compile
846# Nagios with embedded Perl support, this option has no effect.
847
848p1_file=/usr/lib/nagios2/p1.pl
849
850
851
852# ILLEGAL OBJECT NAME CHARACTERS
853# This option allows you to specify illegal characters that cannot
854# be used in host names, service descriptions, or names of other
855# object types.
856
857illegal_object_name_chars=`~!$%^&*|'"<>?,()=
858
859
860
861# ILLEGAL MACRO OUTPUT CHARACTERS
862# This option allows you to specify illegal characters that are
863# stripped from macros before being used in notifications, event
864# handlers, etc.  This DOES NOT affect macros used in service or
865# host check commands.
866# The following macros are stripped of the characters you specify:
867#       $HOSTOUTPUT$
868#       $HOSTPERFDATA$
869#       $HOSTACKAUTHOR$
870#       $HOSTACKCOMMENT$
871#       $SERVICEOUTPUT$
872#       $SERVICEPERFDATA$
873#       $SERVICEACKAUTHOR$
874#       $SERVICEACKCOMMENT$
875
876illegal_macro_output_chars=`~$&|'"<>
877
878
879
880# REGULAR EXPRESSION MATCHING
881# This option controls whether or not regular expression matching
882# takes place in the object config files.  Regular expression
883# matching is used to match host, hostgroup, service, and service
884# group names/descriptions in some fields of various object types.
885# Values: 1 = enable regexp matching, 0 = disable regexp matching
886
887use_regexp_matching=0
888
889
890
891# "TRUE" REGULAR EXPRESSION MATCHING
892# This option controls whether or not "true" regular expression
893# matching takes place in the object config files.  This option
894# only has an effect if regular expression matching is enabled
895# (see above).  If this option is DISABLED, regular expression
896# matching only occurs if a string contains wildcard characters
897# (* and ?).  If the option is ENABLED, regexp matching occurs
898# all the time (which can be annoying).
899# Values: 1 = enable true matching, 0 = disable true matching
900
901use_true_regexp_matching=0
902
903
904
905
906# ADMINISTRATOR EMAIL ADDRESS
907# The email address of the administrator of *this* machine (the one
908# doing the monitoring).  Nagios never uses this value itself, but
909# you can access this value by using the $ADMINEMAIL$ macro in your
910# notification commands.
911
912admin_email=nagios
913
914
915
916# ADMINISTRATOR PAGER NUMBER/ADDRESS
917# The pager number/address for the administrator of *this* machine.
918# Nagios never uses this value itself, but you can access this
919# value by using the $ADMINPAGER$ macro in your notification
920# commands.
921
922admin_pager=pagenagios
923
924
925
926# DAEMON CORE DUMP OPTION
927# This option determines whether or not Nagios is allowed to create
928# a core dump when it runs as a daemon.  Note that it is generally
929# considered bad form to allow this, but it may be useful for
930# debugging purposes.
931# Values: 1 - Allow core dumps
932#         0 - Do not allow core dumps (default)
933
934daemon_dumps_core=0
935
936
937#process_performance_data=1
938#service_perfdata_file=/home/noc/ng/log/perfdata
939#service_perfdata_file_template=$LASTSERVICECHECK$||$HOSTNAME$||$SERVICEDESC$||$SERVICEOUTPUT$||$SERVICEPERFDATA$
940#service_perfdata_file_mode=a
941#service_perfdata_file_processing_interval=60
942#service_perfdata_file_processing_command=ng-service-perfdata
943# EOF (End of file)
Note: See TracBrowser for help on using the repository browser.