1
##############################################################################
3
# NAGIOS.CFG - Sample Main Config File for Nagios 3.2.3
5
# Read the documentation for more information on this configuration
6
# file. I've provided some comments here, but things may not be so
7
# clear without further explanation.
9
# Last Modified: 12-14-2008
11
##############################################################################
15
# This is the main log file where service and host events are logged
16
# for historical purposes. This should be the first option specified
17
# in the config file!!!
19
log_file=/var/log/nagios/nagios.log
23
# OBJECT CONFIGURATION FILE(S)
24
# These are the object configuration files in which you define hosts,
25
# host groups, contacts, contact groups, services, etc.
26
# You can split your object definitions across several config files
27
# if you wish (as shown below), or keep them all in a single config file.
29
# You can specify individual object config files as shown below:
30
cfg_file=/etc/nagios/objects/commands.cfg
31
cfg_file=/etc/nagios/objects/contacts.cfg
32
cfg_file=/etc/nagios/objects/timeperiods.cfg
33
cfg_file=/etc/nagios/objects/templates.cfg
35
# Definitions for monitoring the local (Linux) host
36
#cfg_file=/etc/nagios/objects/localhost.cfg
38
# Definitions for monitoring a Windows machine
39
#cfg_file=/etc/nagios/objects/windows.cfg
41
# Definitions for monitoring a router/switch
42
#cfg_file=/etc/nagios/objects/switch.cfg
44
# Definitions for monitoring a network printer
45
#cfg_file=/etc/nagios/objects/printer.cfg
48
# Definitions for hadoop servers
49
cfg_file=/etc/nagios/objects/hadoop-hosts.cfg
50
cfg_file=/etc/nagios/objects/hadoop-hostgroups.cfg
51
cfg_file=/etc/nagios/objects/hadoop-services.cfg
52
cfg_file=/etc/nagios/objects/hadoop-commands.cfg
53
cfg_file=/etc/nagios/objects/hadoop-servicegroups.cfg
56
# You can also tell Nagios to process all config files (with a .cfg
57
# extension) in a particular directory by using the cfg_dir
58
# directive as shown below:
60
#cfg_dir=/etc/nagios/servers
61
#cfg_dir=/etc/nagios/printers
62
#cfg_dir=/etc/nagios/switches
63
#cfg_dir=/etc/nagios/routers
67
# This option determines where object definitions are cached when
68
# Nagios starts/restarts. The CGIs read object definitions from
69
# this cache file (rather than looking at the object config files
70
# directly) in order to prevent inconsistencies that can occur
71
# when the config files are modified after Nagios starts.
73
object_cache_file=/var/lib/nagios/objects.cache
77
# PRE-CACHED OBJECT FILE
78
# This options determines the location of the precached object file.
79
# If you run Nagios with the -p command line option, it will preprocess
80
# your object configuration file(s) and write the cached config to this
81
# file. You can then start Nagios with the -u option to have it read
82
# object definitions from this precached file, rather than the standard
83
# object configuration files (see the cfg_file and cfg_dir options above).
84
# Using a precached object file can speed up the time needed to (re)start
85
# the Nagios process if you've got a large and/or complex configuration.
86
# Read the documentation section on optimizing Nagios to find our more
87
# about how this feature works.
89
precached_object_file=/var/lib/nagios/objects.precache
94
# This is an optional resource file that contains $USERx$ macro
95
# definitions. Multiple resource files can be specified by using
96
# multiple resource_file definitions. The CGIs will not attempt to
97
# read the contents of resource files, so information that is
98
# considered to be sensitive (usernames, passwords, etc) can be
99
# defined as macros in this file and restrictive permissions (600)
100
# can be placed on this file.
102
resource_file=/etc/nagios/resource.cfg
107
# This is where the current status of all monitored services and
108
# hosts is stored. Its contents are read and processed by the CGIs.
109
# The contents of the status file are deleted every time Nagios
112
status_file=/var/lib/nagios/status.dat
116
# STATUS FILE UPDATE INTERVAL
117
# This option determines the frequency (in seconds) that
118
# Nagios will periodically dump program, host, and
119
# service status data.
121
status_update_interval=10
126
# This determines the effective user that Nagios should run as.
127
# You can either supply a username or a UID.
134
# This determines the effective group that Nagios should run as.
135
# You can either supply a group name or a GID.
141
# EXTERNAL COMMAND OPTION
142
# This option allows you to specify whether or not Nagios should check
143
# for external commands (in the command file defined below). By default
144
# Nagios will *not* check for external commands, just to be on the
145
# cautious side. If you want to be able to use the CGI command interface
146
# you will have to enable this.
147
# Values: 0 = disable commands, 1 = enable commands
149
check_external_commands=1
153
# EXTERNAL COMMAND CHECK INTERVAL
154
# This is the interval at which Nagios should check for external commands.
155
# This value works of the interval_length you specify later. If you leave
156
# that at its default value of 60 (seconds), a value of 1 here will cause
157
# Nagios to check for external commands every minute. If you specify a
158
# number followed by an "s" (i.e. 15s), this will be interpreted to mean
159
# actual seconds rather than a multiple of the interval_length variable.
160
# Note: In addition to reading the external command file at regularly
161
# scheduled intervals, Nagios will also check for external commands after
162
# event handlers are executed.
163
# NOTE: Setting this value to -1 causes Nagios to check the external
164
# command file as often as possible.
166
#command_check_interval=15s
167
command_check_interval=-1
171
# EXTERNAL COMMAND FILE
172
# This is the file that Nagios checks for external command requests.
173
# It is also where the command CGI will write commands that are submitted
174
# by users, so it must be writeable by the user that the web server
175
# is running as (usually 'nobody'). Permissions should be set at the
176
# directory level instead of on the file, as the file is deleted every
177
# time its contents are processed.
179
command_file=/var/spool/nagios/nagios.cmd
183
# EXTERNAL COMMAND BUFFER SLOTS
184
# This settings is used to tweak the number of items or "slots" that
185
# the Nagios daemon should allocate to the buffer that holds incoming
186
# external commands before they are processed. As external commands
187
# are processed by the daemon, they are removed from the buffer.
189
external_command_buffer_slots=4096
194
# This is the lockfile that Nagios will use to store its PID number
195
# in when it is running in daemon mode.
197
lock_file=/var/run/nagios/nagios.pid
202
# This is a temporary file that is used as scratch space when Nagios
203
# updates the status log, cleans the comment file, etc. This file
204
# is created, used, and deleted throughout the time that Nagios is
207
temp_file=/var/lib/nagios/nagios.tmp
212
# This is path where Nagios can create temp files for service and
213
# host check results, etc.
219
# EVENT BROKER OPTIONS
220
# Controls what (if any) data gets sent to the event broker.
221
# Values: 0 = Broker nothing
222
# -1 = Broker everything
223
# <other> = See documentation
225
event_broker_options=-1
229
# EVENT BROKER MODULE(S)
230
# This directive is used to specify an event broker module that should
231
# by loaded by Nagios at startup. Use multiple directives if you want
232
# to load more than one module. Arguments that should be passed to
233
# the module at startup are seperated from the module path by a space.
235
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
236
# WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING
237
#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
239
# Do NOT overwrite modules while they are being used by Nagios or Nagios
240
# will crash in a fiery display of SEGFAULT glory. This is a bug/limitation
241
# either in dlopen(), the kernel, and/or the filesystem. And maybe Nagios...
243
# The correct/safe way of updating a module is by using one of these methods:
244
# 1. Shutdown Nagios, replace the module file, restart Nagios
245
# 2. Delete the original module file, move the new module file into place, restart Nagios
249
# broker_module=<modulepath> [moduleargs]
251
#broker_module=/somewhere/module1.o
252
#broker_module=/somewhere/module2.o arg1 arg2=3 debug=0
256
# LOG ROTATION METHOD
257
# This is the log rotation method that Nagios should use to rotate
258
# the main log file. Values are as follows..
259
# n = None - don't rotate the log
260
# h = Hourly rotation (top of the hour)
261
# d = Daily rotation (midnight every day)
262
# w = Weekly rotation (midnight on Saturday evening)
263
# m = Monthly rotation (midnight last day of month)
265
log_rotation_method=d
270
# This is the directory where archived (rotated) log files should be
271
# placed (assuming you've chosen to do log rotation).
273
log_archive_path=/var/log/nagios/archives
278
# If you want messages logged to the syslog facility, as well as the
279
# Nagios log file set this option to 1. If not, set it to 0.
285
# NOTIFICATION LOGGING OPTION
286
# If you don't want notifications to be logged, set this value to 0.
287
# If notifications should be logged, set the value to 1.
293
# SERVICE RETRY LOGGING OPTION
294
# If you don't want service check retries to be logged, set this value
295
# to 0. If retries should be logged, set the value to 1.
297
log_service_retries=1
301
# HOST RETRY LOGGING OPTION
302
# If you don't want host check retries to be logged, set this value to
303
# 0. If retries should be logged, set the value to 1.
309
# EVENT HANDLER LOGGING OPTION
310
# If you don't want host and service event handlers to be logged, set
311
# this value to 0. If event handlers should be logged, set the value
318
# INITIAL STATES LOGGING OPTION
319
# If you want Nagios to log all initial host and service states to
320
# the main log file (the first time the service or host is checked)
321
# you can enable this option by setting this value to 1. If you
322
# are not using an external application that does long term state
323
# statistics reporting, you do not need to enable this option. In
324
# this case, set the value to 0.
330
# EXTERNAL COMMANDS LOGGING OPTION
331
# If you don't want Nagios to log external commands, set this value
332
# to 0. If external commands should be logged, set this value to 1.
333
# Note: This option does not include logging of passive service
334
# checks - see the option below for controlling whether or not
335
# passive checks are logged.
337
log_external_commands=1
341
# PASSIVE CHECKS LOGGING OPTION
342
# If you don't want Nagios to log passive host and service checks, set
343
# this value to 0. If passive checks should be logged, set
350
# GLOBAL HOST AND SERVICE EVENT HANDLERS
351
# These options allow you to specify a host and service event handler
352
# command that is to be run for every host or service state change.
353
# The global event handler is executed immediately prior to the event
354
# handler that you have optionally specified in each host or
355
# service definition. The command argument is the short name of a
356
# command definition that you define in your host configuration file.
357
# Read the HTML docs for more information.
359
#global_host_event_handler=somecommand
360
#global_service_event_handler=somecommand
364
# SERVICE INTER-CHECK DELAY METHOD
365
# This is the method that Nagios should use when initially
366
# "spreading out" service checks when it starts monitoring. The
367
# default is to use smart delay calculation, which will try to
368
# space all service checks out evenly to minimize CPU load.
369
# Using the dumb setting will cause all checks to be scheduled
370
# at the same time (with no delay between them)! This is not a
371
# good thing for production, but is useful when testing the
372
# parallelization functionality.
373
# n = None - don't use any delay between checks
374
# d = Use a "dumb" delay of 1 second between checks
375
# s = Use "smart" inter-check delay calculation
376
# x.xx = Use an inter-check delay of x.xx seconds
378
service_inter_check_delay_method=s
382
# MAXIMUM SERVICE CHECK SPREAD
383
# This variable determines the timeframe (in minutes) from the
384
# program start time that an initial check of all services should
385
# be completed. Default is 30 minutes.
387
max_service_check_spread=30
391
# SERVICE CHECK INTERLEAVE FACTOR
392
# This variable determines how service checks are interleaved.
393
# Interleaving the service checks allows for a more even
394
# distribution of service checks and reduced load on remote
395
# hosts. Setting this value to 1 is equivalent to how versions
396
# of Nagios previous to 0.0.5 did service checks. Set this
397
# value to s (smart) for automatic calculation of the interleave
398
# factor unless you have a specific reason to change it.
399
# s = Use "smart" interleave factor calculation
400
# x = Use an interleave factor of x, where x is a
401
# number greater than or equal to 1.
403
service_interleave_factor=s
407
# HOST INTER-CHECK DELAY METHOD
408
# This is the method that Nagios should use when initially
409
# "spreading out" host checks when it starts monitoring. The
410
# default is to use smart delay calculation, which will try to
411
# space all host checks out evenly to minimize CPU load.
412
# Using the dumb setting will cause all checks to be scheduled
413
# at the same time (with no delay between them)!
414
# n = None - don't use any delay between checks
415
# d = Use a "dumb" delay of 1 second between checks
416
# s = Use "smart" inter-check delay calculation
417
# x.xx = Use an inter-check delay of x.xx seconds
419
host_inter_check_delay_method=s
423
# MAXIMUM HOST CHECK SPREAD
424
# This variable determines the timeframe (in minutes) from the
425
# program start time that an initial check of all hosts should
426
# be completed. Default is 30 minutes.
428
max_host_check_spread=30
432
# MAXIMUM CONCURRENT SERVICE CHECKS
433
# This option allows you to specify the maximum number of
434
# service checks that can be run in parallel at any given time.
435
# Specifying a value of 1 for this variable essentially prevents
436
# any service checks from being parallelized. A value of 0
437
# will not restrict the number of concurrent checks that are
440
max_concurrent_checks=0
444
# HOST AND SERVICE CHECK REAPER FREQUENCY
445
# This is the frequency (in seconds!) that Nagios will process
446
# the results of host and service checks.
448
check_result_reaper_frequency=10
453
# MAX CHECK RESULT REAPER TIME
454
# This is the max amount of time (in seconds) that a single
455
# check result reaper event will be allowed to run before
456
# returning control back to Nagios so it can perform other
459
max_check_result_reaper_time=30
465
# This is directory where Nagios stores the results of host and
466
# service checks that have not yet been processed.
468
# Note: Make sure that only one instance of Nagios has access
471
check_result_path=/var/spool/nagios
476
# MAX CHECK RESULT FILE AGE
477
# This option determines the maximum age (in seconds) which check
478
# result files are considered to be valid. Files older than this
479
# threshold will be mercilessly deleted without further processing.
481
max_check_result_file_age=3600
486
# CACHED HOST CHECK HORIZON
487
# This option determines the maximum amount of time (in seconds)
488
# that the state of a previous host check is considered current.
489
# Cached host states (from host checks that were performed more
490
# recently that the timeframe specified by this value) can immensely
491
# improve performance in regards to the host check logic.
492
# Too high of a value for this option may result in inaccurate host
493
# states being used by Nagios, while a lower value may result in a
494
# performance hit for host checks. Use a value of 0 to disable host
497
cached_host_check_horizon=15
501
# CACHED SERVICE CHECK HORIZON
502
# This option determines the maximum amount of time (in seconds)
503
# that the state of a previous service check is considered current.
504
# Cached service states (from service checks that were performed more
505
# recently that the timeframe specified by this value) can immensely
506
# improve performance in regards to predictive dependency checks.
507
# Use a value of 0 to disable service check caching.
509
cached_service_check_horizon=15
513
# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
514
# This option determines whether or not Nagios will attempt to execute
515
# checks of hosts when it predicts that future dependency logic test
516
# may be needed. These predictive checks can help ensure that your
517
# host dependency logic works well.
519
# 0 = Disable predictive checks
520
# 1 = Enable predictive checks (default)
522
enable_predictive_host_dependency_checks=1
526
# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
527
# This option determines whether or not Nagios will attempt to execute
528
# checks of service when it predicts that future dependency logic test
529
# may be needed. These predictive checks can help ensure that your
530
# service dependency logic works well.
532
# 0 = Disable predictive checks
533
# 1 = Enable predictive checks (default)
535
enable_predictive_service_dependency_checks=1
539
# SOFT STATE DEPENDENCIES
540
# This option determines whether or not Nagios will use soft state
541
# information when checking host and service dependencies. Normally
542
# Nagios will only use the latest hard host or service state when
543
# checking dependencies. If you want it to use the latest state (regardless
544
# of whether its a soft or hard state type), enable this option.
546
# 0 = Don't use soft state dependencies (default)
547
# 1 = Use soft state dependencies
549
soft_state_dependencies=0
553
# TIME CHANGE ADJUSTMENT THRESHOLDS
554
# These options determine when Nagios will react to detected changes
555
# in system time (either forward or backwards).
557
#time_change_threshold=900
561
# AUTO-RESCHEDULING OPTION
562
# This option determines whether or not Nagios will attempt to
563
# automatically reschedule active host and service checks to
564
# "smooth" them out over time. This can help balance the load on
565
# the monitoring server.
566
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
567
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
569
auto_reschedule_checks=0
573
# AUTO-RESCHEDULING INTERVAL
574
# This option determines how often (in seconds) Nagios will
575
# attempt to automatically reschedule checks. This option only
576
# has an effect if the auto_reschedule_checks option is enabled.
577
# Default is 30 seconds.
578
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
579
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
581
auto_rescheduling_interval=30
585
# AUTO-RESCHEDULING WINDOW
586
# This option determines the "window" of time (in seconds) that
587
# Nagios will look at when automatically rescheduling checks.
588
# Only host and service checks that occur in the next X seconds
589
# (determined by this variable) will be rescheduled. This option
590
# only has an effect if the auto_reschedule_checks option is
591
# enabled. Default is 180 seconds (3 minutes).
592
# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE
593
# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY
595
auto_rescheduling_window=180
600
# This is the number of seconds to sleep between checking for system
601
# events and service checks that need to be run.
608
# These options control how much time Nagios will allow various
609
# types of commands to execute before killing them off. Options
610
# are available for controlling maximum time allotted for
611
# service checks, host checks, event handlers, notifications, the
612
# ocsp command, and performance data commands. All values are in
615
service_check_timeout=60
616
host_check_timeout=30
617
event_handler_timeout=30
618
notification_timeout=30
624
# RETAIN STATE INFORMATION
625
# This setting determines whether or not Nagios will save state
626
# information for services and hosts before it shuts down. Upon
627
# startup Nagios will reload all saved service and host state
628
# information before starting to monitor. This is useful for
629
# maintaining long-term data on state statistics, etc, but will
630
# slow Nagios down a bit when it (re)starts. Since its only
631
# a one-time penalty, I think its well worth the additional
634
retain_state_information=1
638
# STATE RETENTION FILE
639
# This is the file that Nagios should use to store host and
640
# service state information before it shuts down. The state
641
# information in this file is also read immediately prior to
642
# starting to monitor the network when Nagios is restarted.
643
# This file is used only if the retain_state_information
644
# variable is set to 1.
646
state_retention_file=/var/lib/nagios/retention.dat
650
# RETENTION DATA UPDATE INTERVAL
651
# This setting determines how often (in minutes) that Nagios
652
# will automatically save retention data during normal operation.
653
# If you set this value to 0, Nagios will not save retention
654
# data at regular interval, but it will still save retention
655
# data before shutting down or restarting. If you have disabled
656
# state retention, this option has no effect.
658
retention_update_interval=60
662
# USE RETAINED PROGRAM STATE
663
# This setting determines whether or not Nagios will set
664
# program status variables based on the values saved in the
665
# retention file. If you want to use retained program status
666
# information, set this value to 1. If not, set this value
669
use_retained_program_state=1
673
# USE RETAINED SCHEDULING INFO
674
# This setting determines whether or not Nagios will retain
675
# the scheduling info (next check time) for hosts and services
676
# based on the values saved in the retention file. If you
677
# If you want to use retained scheduling info, set this
678
# value to 1. If not, set this value to 0.
680
use_retained_scheduling_info=1
684
# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
685
# The following variables are used to specify specific host and
686
# service attributes that should *not* be retained by Nagios during
689
# The values of the masks are bitwise ANDs of values specified
690
# by the "MODATTR_" definitions found in include/common.h.
691
# For example, if you do not want the current enabled/disabled state
692
# of flap detection and event handlers for hosts to be retained, you
693
# would use a value of 24 for the host attribute mask...
694
# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24
696
# This mask determines what host attributes are not retained
697
retained_host_attribute_mask=0
699
# This mask determines what service attributes are not retained
700
retained_service_attribute_mask=0
702
# These two masks determine what process attributes are not retained.
703
# There are two masks, because some process attributes have host and service
704
# options. For example, you can disable active host checks, but leave active
705
# service checks enabled.
706
retained_process_host_attribute_mask=0
707
retained_process_service_attribute_mask=0
709
# These two masks determine what contact attributes are not retained.
710
# There are two masks, because some contact attributes have host and
711
# service options. For example, you can disable host notifications for
712
# a contact, but leave service notifications enabled for them.
713
retained_contact_host_attribute_mask=0
714
retained_contact_service_attribute_mask=0
719
# This is the seconds per unit interval as used in the
720
# host/contact/service configuration files. Setting this to 60 means
721
# that each interval is one minute long (60 seconds). Other settings
722
# have not been tested much, so your mileage is likely to vary...
729
# This option determines whether Nagios will automatically check to
730
# see if new updates (releases) are available. It is recommend that you
731
# enable this option to ensure that you stay on top of the latest critical
732
# patches to Nagios. Nagios is critical to you - make sure you keep it in
733
# good shape. Nagios will check once a day for new updates. Data collected
734
# by Nagios Enterprises from the update check is processed in accordance
735
# with our privacy policy - see http://api.nagios.org for details.
742
# This option deterines what data Nagios will send to api.nagios.org when
743
# it checks for updates. By default, Nagios will send information on the
744
# current version of Nagios you have installed, as well as an indicator as
745
# to whether this was a new installation or not. Nagios Enterprises uses
746
# this data to determine the number of users running specific version of
747
# Nagios. Enable this option if you do not want this information to be sent.
753
# AGGRESSIVE HOST CHECKING OPTION
754
# If you don't want to turn on aggressive host checking features, set
755
# this value to 0 (the default). Otherwise set this value to 1 to
756
# enable the aggressive check option. Read the docs for more info
757
# on what aggressive host check is or check out the source code in
760
use_aggressive_host_checking=0
764
# SERVICE CHECK EXECUTION OPTION
765
# This determines whether or not Nagios will actively execute
766
# service checks when it initially starts. If this option is
767
# disabled, checks are not actively made, but Nagios can still
768
# receive and process passive check results that come in. Unless
769
# you're implementing redundant hosts or have a special need for
770
# disabling the execution of service checks, leave this enabled!
771
# Values: 1 = enable checks, 0 = disable checks
773
execute_service_checks=1
777
# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
778
# This determines whether or not Nagios will accept passive
779
# service checks results when it initially (re)starts.
780
# Values: 1 = accept passive checks, 0 = reject passive checks
782
accept_passive_service_checks=1
786
# HOST CHECK EXECUTION OPTION
787
# This determines whether or not Nagios will actively execute
788
# host checks when it initially starts. If this option is
789
# disabled, checks are not actively made, but Nagios can still
790
# receive and process passive check results that come in. Unless
791
# you're implementing redundant hosts or have a special need for
792
# disabling the execution of host checks, leave this enabled!
793
# Values: 1 = enable checks, 0 = disable checks
795
execute_host_checks=1
799
# PASSIVE HOST CHECK ACCEPTANCE OPTION
800
# This determines whether or not Nagios will accept passive
801
# host checks results when it initially (re)starts.
802
# Values: 1 = accept passive checks, 0 = reject passive checks
804
accept_passive_host_checks=1
808
# NOTIFICATIONS OPTION
809
# This determines whether or not Nagios will sent out any host or
810
# service notifications when it is initially (re)started.
811
# Values: 1 = enable notifications, 0 = disable notifications
813
enable_notifications=1
817
# EVENT HANDLER USE OPTION
818
# This determines whether or not Nagios will run any host or
819
# service event handlers when it is initially (re)started. Unless
820
# you're implementing redundant hosts, leave this option enabled.
821
# Values: 1 = enable event handlers, 0 = disable event handlers
823
enable_event_handlers=1
827
# PROCESS PERFORMANCE DATA OPTION
828
# This determines whether or not Nagios will process performance
829
# data returned from service and host checks. If this option is
830
# enabled, host performance data will be processed using the
831
# host_perfdata_command (defined below) and service performance
832
# data will be processed using the service_perfdata_command (also
833
# defined below). Read the HTML docs for more information on
835
# Values: 1 = process performance data, 0 = do not process performance data
837
process_performance_data=0
841
# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
842
# These commands are run after every host and service check is
843
# performed. These commands are executed only if the
844
# enable_performance_data option (above) is set to 1. The command
845
# argument is the short name of a command definition that you
846
# define in your host configuration file. Read the HTML docs for
847
# more information on performance data.
849
#host_perfdata_command=process-host-perfdata
850
#service_perfdata_command=process-service-perfdata
854
# HOST AND SERVICE PERFORMANCE DATA FILES
855
# These files are used to store host and service performance data.
856
# Performance data is only written to these files if the
857
# enable_performance_data option (above) is set to 1.
859
#host_perfdata_file=/tmp/host-perfdata
860
#service_perfdata_file=/tmp/service-perfdata
864
# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES
865
# These options determine what data is written (and how) to the
866
# performance data files. The templates may contain macros, special
867
# characters (\t for tab, \r for carriage return, \n for newline)
868
# and plain text. A newline is automatically added after each write
869
# to the performance data file. Some examples of what you can do are
872
#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$
873
#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$
877
# HOST AND SERVICE PERFORMANCE DATA FILE MODES
878
# This option determines whether or not the host and service
879
# performance data files are opened in write ("w") or append ("a")
880
# mode. If you want to use named pipes, you should use the special
881
# pipe ("p") mode which avoid blocking at startup, otherwise you will
882
# likely want the defult append ("a") mode.
884
#host_perfdata_file_mode=a
885
#service_perfdata_file_mode=a
889
# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL
890
# These options determine how often (in seconds) the host and service
891
# performance data files are processed using the commands defined
892
# below. A value of 0 indicates the files should not be periodically
895
#host_perfdata_file_processing_interval=0
896
#service_perfdata_file_processing_interval=0
900
# HOST AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS
901
# These commands are used to periodically process the host and
902
# service performance data files. The interval at which the
903
# processing occurs is determined by the options above.
905
#host_perfdata_file_processing_command=process-host-perfdata-file
906
#service_perfdata_file_processing_command=process-service-perfdata-file
910
# OBSESS OVER SERVICE CHECKS OPTION
911
# This determines whether or not Nagios will obsess over service
912
# checks and run the ocsp_command defined below. Unless you're
913
# planning on implementing distributed monitoring, do not enable
914
# this option. Read the HTML docs for more information on
915
# implementing distributed monitoring.
916
# Values: 1 = obsess over services, 0 = do not obsess (default)
918
obsess_over_services=0
922
# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
923
# This is the command that is run for every service check that is
924
# processed by Nagios. This command is executed only if the
925
# obsess_over_services option (above) is set to 1. The command
926
# argument is the short name of a command definition that you
927
# define in your host configuration file. Read the HTML docs for
928
# more information on implementing distributed monitoring.
930
#ocsp_command=somecommand
934
# OBSESS OVER HOST CHECKS OPTION
935
# This determines whether or not Nagios will obsess over host
936
# checks and run the ochp_command defined below. Unless you're
937
# planning on implementing distributed monitoring, do not enable
938
# this option. Read the HTML docs for more information on
939
# implementing distributed monitoring.
940
# Values: 1 = obsess over hosts, 0 = do not obsess (default)
946
# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
947
# This is the command that is run for every host check that is
948
# processed by Nagios. This command is executed only if the
949
# obsess_over_hosts option (above) is set to 1. The command
950
# argument is the short name of a command definition that you
951
# define in your host configuration file. Read the HTML docs for
952
# more information on implementing distributed monitoring.
954
#ochp_command=somecommand
958
# TRANSLATE PASSIVE HOST CHECKS OPTION
959
# This determines whether or not Nagios will translate
960
# DOWN/UNREACHABLE passive host check results into their proper
961
# state for this instance of Nagios. This option is useful
962
# if you have distributed or failover monitoring setup. In
963
# these cases your other Nagios servers probably have a different
964
# "view" of the network, with regards to the parent/child relationship
965
# of hosts. If a distributed monitoring server thinks a host
966
# is DOWN, it may actually be UNREACHABLE from the point of
967
# this Nagios instance. Enabling this option will tell Nagios
968
# to translate any DOWN or UNREACHABLE host states it receives
969
# passively into the correct state from the view of this server.
970
# Values: 1 = perform translation, 0 = do not translate (default)
972
translate_passive_host_checks=0
976
# PASSIVE HOST CHECKS ARE SOFT OPTION
977
# This determines whether or not Nagios will treat passive host
978
# checks as being HARD or SOFT. By default, a passive host check
979
# result will put a host into a HARD state type. This can be changed
980
# by enabling this option.
981
# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT
983
passive_host_checks_are_soft=0
987
# ORPHANED HOST/SERVICE CHECK OPTIONS
988
# These options determine whether or not Nagios will periodically
989
# check for orphaned host service checks. Since service checks are
990
# not rescheduled until the results of their previous execution
991
# instance are processed, there exists a possibility that some
992
# checks may never get rescheduled. A similar situation exists for
993
# host checks, although the exact scheduling details differ a bit
994
# from service checks. Orphaned checks seem to be a rare
995
# problem and should not happen under normal circumstances.
996
# If you have problems with service checks never getting
997
# rescheduled, make sure you have orphaned service checks enabled.
998
# Values: 1 = enable checks, 0 = disable checks
1000
check_for_orphaned_services=1
1001
check_for_orphaned_hosts=1
1005
# SERVICE FRESHNESS CHECK OPTION
1006
# This option determines whether or not Nagios will periodically
1007
# check the "freshness" of service results. Enabling this option
1008
# is useful for ensuring passive checks are received in a timely
1010
# Values: 1 = enabled freshness checking, 0 = disable freshness checking
1012
check_service_freshness=1
1016
# SERVICE FRESHNESS CHECK INTERVAL
1017
# This setting determines how often (in seconds) Nagios will
1018
# check the "freshness" of service check results. If you have
1019
# disabled service freshness checking, this option has no effect.
1021
service_freshness_check_interval=60
1025
# HOST FRESHNESS CHECK OPTION
1026
# This option determines whether or not Nagios will periodically
1027
# check the "freshness" of host results. Enabling this option
1028
# is useful for ensuring passive checks are received in a timely
1030
# Values: 1 = enabled freshness checking, 0 = disable freshness checking
1032
check_host_freshness=0
1036
# HOST FRESHNESS CHECK INTERVAL
1037
# This setting determines how often (in seconds) Nagios will
1038
# check the "freshness" of host check results. If you have
1039
# disabled host freshness checking, this option has no effect.
1041
host_freshness_check_interval=60
1046
# ADDITIONAL FRESHNESS THRESHOLD LATENCY
1047
# This setting determines the number of seconds that Nagios
1048
# will add to any host and service freshness thresholds that
1049
# it calculates (those not explicitly specified by the user).
1051
additional_freshness_latency=15
1056
# FLAP DETECTION OPTION
1057
# This option determines whether or not Nagios will try
1058
# and detect hosts and services that are "flapping".
1059
# Flapping occurs when a host or service changes between
1060
# states too frequently. When Nagios detects that a
1061
# host or service is flapping, it will temporarily suppress
1062
# notifications for that host/service until it stops
1063
# flapping. Flap detection is very experimental, so read
1064
# the HTML documentation before enabling this feature!
1065
# Values: 1 = enable flap detection
1066
# 0 = disable flap detection (default)
1068
enable_flap_detection=1
1072
# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES
1073
# Read the HTML documentation on flap detection for
1074
# an explanation of what this option does. This option
1075
# has no effect if flap detection is disabled.
1077
low_service_flap_threshold=5.0
1078
high_service_flap_threshold=20.0
1079
low_host_flap_threshold=5.0
1080
high_host_flap_threshold=20.0
1084
# DATE FORMAT OPTION
1085
# This option determines how short dates are displayed. Valid options
1087
# us (MM-DD-YYYY HH:MM:SS)
1088
# euro (DD-MM-YYYY HH:MM:SS)
1089
# iso8601 (YYYY-MM-DD HH:MM:SS)
1090
# strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
1099
# This option is used to override the default timezone that this
1100
# instance of Nagios runs in. If not specified, Nagios will use
1101
# the system configured timezone.
1103
# NOTE: In order to display the correct timezone in the CGIs, you
1104
# will also need to alter the Apache directives for the CGI path
1105
# to include your timezone. Example:
1107
# <Directory "/usr/local/nagios/sbin/">
1108
# SetEnv TZ "Australia/Brisbane"
1112
#use_timezone=US/Mountain
1113
#use_timezone=Australia/Brisbane
1118
# P1.PL FILE LOCATION
1119
# This value determines where the p1.pl perl script (used by the
1120
# embedded Perl interpreter) is located. If you didn't compile
1121
# Nagios with embedded Perl support, this option has no effect.
1123
p1_file=/usr/lib/nagios/p1.pl
1127
# EMBEDDED PERL INTERPRETER OPTION
1128
# This option determines whether or not the embedded Perl interpreter
1129
# will be enabled during runtime. This option has no effect if Nagios
1130
# has not been compiled with support for embedded Perl.
1131
# Values: 0 = disable interpreter, 1 = enable interpreter
1133
enable_embedded_perl=1
1137
# EMBEDDED PERL USAGE OPTION
1138
# This option determines whether or not Nagios will process Perl plugins
1139
# and scripts with the embedded Perl interpreter if the plugins/scripts
1140
# do not explicitly indicate whether or not it is okay to do so. Read
1141
# the HTML documentation on the embedded Perl interpreter for more
1142
# information on how this option works.
1144
use_embedded_perl_implicitly=1
1148
# ILLEGAL OBJECT NAME CHARACTERS
1149
# This option allows you to specify illegal characters that cannot
1150
# be used in host names, service descriptions, or names of other
1153
illegal_object_name_chars=`~!$%^&*|'"<>?,()=
1157
# ILLEGAL MACRO OUTPUT CHARACTERS
1158
# This option allows you to specify illegal characters that are
1159
# stripped from macros before being used in notifications, event
1160
# handlers, etc. This DOES NOT affect macros used in service or
1161
# host check commands.
1162
# The following macros are stripped of the characters you specify:
1169
# $SERVICEACKAUTHOR$
1170
# $SERVICEACKCOMMENT$
1172
illegal_macro_output_chars=`~$&|'"<>
1176
# REGULAR EXPRESSION MATCHING
1177
# This option controls whether or not regular expression matching
1178
# takes place in the object config files. Regular expression
1179
# matching is used to match host, hostgroup, service, and service
1180
# group names/descriptions in some fields of various object types.
1181
# Values: 1 = enable regexp matching, 0 = disable regexp matching
1183
use_regexp_matching=0
1187
# "TRUE" REGULAR EXPRESSION MATCHING
1188
# This option controls whether or not "true" regular expression
1189
# matching takes place in the object config files. This option
1190
# only has an effect if regular expression matching is enabled
1191
# (see above). If this option is DISABLED, regular expression
1192
# matching only occurs if a string contains wildcard characters
1193
# (* and ?). If the option is ENABLED, regexp matching occurs
1194
# all the time (which can be annoying).
1195
# Values: 1 = enable true matching, 0 = disable true matching
1197
use_true_regexp_matching=0
1201
# ADMINISTRATOR EMAIL/PAGER ADDRESSES
1202
# The email and pager address of a global administrator (likely you).
1203
# Nagios never uses these values itself, but you can access them by
1204
# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
1207
admin_email=nagios@localhost
1208
admin_pager=pagenagios@localhost
1212
# DAEMON CORE DUMP OPTION
1213
# This option determines whether or not Nagios is allowed to create
1214
# a core dump when it runs as a daemon. Note that it is generally
1215
# considered bad form to allow this, but it may be useful for
1216
# debugging purposes. Enabling this option doesn't guarantee that
1217
# a core file will be produced, but that's just life...
1218
# Values: 1 - Allow core dumps
1219
# 0 - Do not allow core dumps (default)
1225
# LARGE INSTALLATION TWEAKS OPTION
1226
# This option determines whether or not Nagios will take some shortcuts
1227
# which can save on memory and CPU usage in large Nagios installations.
1228
# Read the documentation for more information on the benefits/tradeoffs
1229
# of enabling this option.
1230
# Values: 1 - Enabled tweaks
1231
# 0 - Disable tweaks (default)
1233
use_large_installation_tweaks=0
1237
# ENABLE ENVIRONMENT MACROS
1238
# This option determines whether or not Nagios will make all standard
1239
# macros available as environment variables when host/service checks
1240
# and system commands (event handlers, notifications, etc.) are
1241
# executed. Enabling this option can cause performance issues in
1242
# large installations, as it will consume a bit more memory and (more
1243
# importantly) consume more CPU.
1244
# Values: 1 - Enable environment variable macros (default)
1245
# 0 - Disable environment variable macros
1247
enable_environment_macros=1
1251
# CHILD PROCESS MEMORY OPTION
1252
# This option determines whether or not Nagios will free memory in
1253
# child processes (processed used to execute system commands and host/
1254
# service checks). If you specify a value here, it will override
1256
# Value: 1 - Free memory in child processes
1257
# 0 - Do not free memory in child processes
1259
#free_child_process_memory=1
1263
# CHILD PROCESS FORKING BEHAVIOR
1264
# This option determines how Nagios will fork child processes
1265
# (used to execute system commands and host/service checks). Normally
1266
# child processes are fork()ed twice, which provides a very high level
1267
# of isolation from problems. Fork()ing once is probably enough and will
1268
# save a great deal on CPU usage (in large installs), so you might
1269
# want to consider using this. If you specify a value here, it will
1271
# Value: 1 - Child processes fork() twice
1272
# 0 - Child processes fork() just once
1274
#child_processes_fork_twice=1
1279
# This option determines how much (if any) debugging information will
1280
# be written to the debug file. OR values together to log multiple
1281
# types of information.
1287
# 4 = Process information
1288
# 8 = Scheduled events
1289
# 16 = Host/service checks
1290
# 32 = Notifications
1292
# 128 = External commands
1294
# 512 = Scheduled downtime
1303
# This option determines how verbose the debug log out will be.
1304
# Values: 0 = Brief output
1313
# This option determines where Nagios should write debugging information.
1315
debug_file=/var/lib/nagios/nagios.debug
1319
# MAX DEBUG FILE SIZE
1320
# This option determines the maximum size (in bytes) of the debug file. If
1321
# the file grows larger than this size, it will be renamed with a .old
1322
# extension. If a file already exists with a .old extension it will
1323
# automatically be deleted. This helps ensure your disk space usage doesn't
1324
# get out of control when debugging Nagios.
1326
max_debug_file_size=1000000
added
removed
hooks/test/hdp_scripts/hdp_manual_install_rpm_helper_files-2.1.1.385/configuration_files/nagios/objects/nagios.cfg-suse
