Changeset 1060 for noc

Timestamp:

Apr 4, 2009, 12:59:01 AM (15 years ago)

Author:

quentin

Message:

Update Nagios configuration for Nagios 3

Location:

noc/nagios

Files:

• cgi.cfg (modified) (6 diffs)
• nagios.cfg (modified) (30 diffs)

noc/nagios/cgi.cfg

@@ -11 +11 @@
 # data they might need.
 
-main_config_file=/etc/nagios2/nagios.cfg
+main_config_file=/etc/nagios3/nagios.cfg
 
 
@@ -20 +20 @@
 # and statuswrl CGIs.
 
-physical_html_path=/usr/share/nagios2/htdocs
+physical_html_path=/usr/share/nagios3/htdocs
 
 
@@ -32 +32 @@
 # (without the quotes).
 
-url_html_path=/nagios2
+url_html_path=/nagios3
 
 
@@ -46 +46 @@
 
 
-# NAGIOS PROCESS CHECK COMMAND
-# This is the full path and filename of the program used to check
-# the status of the Nagios process.  It is used only by the CGIs
-# and is completely optional.  However, if you don't use it, you'll
-# see warning messages in the CGIs about the Nagios process
-# not running and you won't be able to execute any commands from
-# the web interface.  The program should follow the same rules
-# as plugins; the return codes are the same as for the plugins,
-# it should have timeout protection, it should output something
-# to STDIO, etc.
-#
-# Note: The command line for the check_nagios plugin below may
-# have to be tweaked a bit, as different versions of the plugin
-# use different command line arguments/syntaxes.
-
-nagios_check_command=/usr/lib/nagios/plugins/check_nagios /var/cache/nagios2/status.dat 5 '/usr/sbin/nagios2'
-
+# PENDING STATES OPTION
+# This option determines what states should be displayed in the web
+# interface for hosts/services that have not yet been checked.
+# Values: 0 = leave hosts/services that have not been check yet in their original state
+#         1 = mark hosts/services that have not been checked yet as PENDING
+
+use_pending_states=1
+
+nagios_check_command=/usr/lib/nagios/plugins/check_nagios /var/cache/nagios3/status.dat 5 '/usr/sbin/nagios3'
 
 
@@ -83 +75 @@
 
 use_authentication=1
+
+
+
+
+# x509 CERT AUTHENTICATION
+# When enabled, this option allows you to use x509 cert (SSL)
+# authentication in the CGIs.  This is an advanced option and should
+# not be enabled unless you know what you're doing.
+
+use_ssl_authentication=0
+
 
 
@@ -246 +249 @@
 # of various CGIs (status, statusmap, extinfo, and outages).  
 
-refresh_rate=60
+refresh_rate=90
+
+
+
+# ESCAPE HTML TAGS
+# This option determines whether HTML tags in host and service
+# status output is escaped in the web interface.  If enabled,
+# your plugin output will not be able to contain clickable links.
+
+escape_html_tags=1
+
 
 

noc/nagios/nagios.cfg

@@ -1 +1 @@
 ##############################################################################
 #
-# NAGIOS.CFG - Main Config File for Nagios
+# NAGIOS.CFG - Sample Main Config File for Nagios 
+#
 #
 ##############################################################################
@@ -11 +12 @@
 # in the config file!!!
 
-log_file=/var/log/nagios2/nagios.log
-
-
-
-# OBJECT CONFIGURATION FILE(S)
-# This is the configuration file in which you define hosts, host
-# groups, contacts, contact groups, services, etc.  I guess it would
-# be better called an object definition file, but for historical
-# reasons it isn't.  You can split object definitions into several
-# different config files by using multiple cfg_file statements here.
-# Nagios will read and process all the config files you define.
-# This can be very useful if you want to keep command definitions 
-# separate from host and contact definitions...
-
-# Plugin commands (service and host check commands)
-# Arguments are likely to change between different releases of the
-# plugins, so you should use the same config file provided with the
-# plugin release rather than the one provided with Nagios.
-cfg_file=/etc/nagios2/checkcommands.cfg
+log_file=/var/log/nagios3/nagios.log
 
 # Debian also defaults to using the check commands defined by the debian
@@ -35 +18 @@
 cfg_dir=/etc/nagios-plugins/config
 
-# Misc commands (notification and event handler commands, etc)
-cfg_file=/etc/nagios2/misccommands.cfg
-
-# You can split other types of object definitions across several
-# config files if you wish (as done here), or keep them all in a
-# single config file.
-
-cfg_file=/etc/nagios2/base.cfg
-cfg_file=/etc/nagios2/contacts.cfg
-cfg_file=/etc/nagios2/hostgroups.cfg
-cfg_file=/etc/nagios2/hosts.cfg
-cfg_file=/etc/nagios2/services.cfg
-
-cfg_file=/etc/nagios2/xvm.cfg
-#cfg_file=/etc/nagios2/test.cfg
-
+# OBJECT CONFIGURATION FILE(S)
+# These are the object configuration files in which you define hosts,
+# host groups, contacts, contact groups, services, etc.
+# You can split your object definitions across several config files
+# if you wish (as shown below), or keep them all in a single config file.
+
+# You can specify individual object config files as shown below:
+cfg_file=/etc/nagios3/misccommands.cfg
+cfg_file=/etc/nagios3/contacts.cfg
+cfg_file=/etc/nagios3/hostgroups.cfg
+cfg_file=/etc/nagios3/hosts.cfg
+cfg_file=/etc/nagios3/services.cfg
+
+cfg_file=/etc/nagios3/xvm.cfg
 
 
@@ -60 +41 @@
 # when the config files are modified after Nagios starts.
 
-object_cache_file=/var/cache/nagios2/objects.cache
+object_cache_file=/var/cache/nagios3/objects.cache
+
+
+
+# PRE-CACHED OBJECT FILE
+# This options determines the location of the precached object file.
+# If you run Nagios with the -p command line option, it will preprocess
+# your object configuration file(s) and write the cached config to this
+# file.  You can then start Nagios with the -u option to have it read
+# object definitions from this precached file, rather than the standard
+# object configuration files (see the cfg_file and cfg_dir options above).
+# Using a precached object file can speed up the time needed to (re)start 
+# the Nagios process if you've got a large and/or complex configuration.
+# Read the documentation section on optimizing Nagios to find our more
+# about how this feature works.
+
+precached_object_file=/var/lib/nagios3/objects.precache
 
 
@@ -73 +70 @@
 # can be placed on this file.
 
-resource_file=/etc/nagios2/private/resource.cfg
+resource_file=/etc/nagios3/private/resource.cfg
 
 
@@ -83 +80 @@
 #  restarts.
 
-status_file=/var/cache/nagios2/status.dat
+status_file=/var/cache/nagios3/status.dat
+
+
+
+# STATUS FILE UPDATE INTERVAL
+# This option determines the frequency (in seconds) that
+# Nagios will periodically dump program, host, and 
+# service status data.
+
+status_update_interval=10
 
 
@@ -108 +114 @@
 # Nagios will *not* check for external commands, just to be on the
 # cautious side.  If you want to be able to use the CGI command interface
-# you will have to enable this.  Setting this value to 0 disables command
-# checking (the default), other values enable it.
+# you will have to enable this.
+# Values: 0 = disable commands, 1 = enable commands
 
 check_external_commands=1
@@ -128 +134 @@
 # command file as often as possible.
 
-#command_check_interval=1
-command_check_interval=1s
-#command_check_interval=-1
+#command_check_interval=15s
+command_check_interval=-1
 
 
@@ -144 +149 @@
 # time to do it.
 
-command_file=/var/lib/nagios2/rw/nagios.cmd
-
-
-
-# COMMENT FILE
-# This is the file that Nagios will use for storing host and service
-# comments.
-
-comment_file=/var/lib/nagios2/comments.dat
-
-
-
-# DOWNTIME FILE
-# This is the file that Nagios will use for storing host and service
-# downtime data.
-
-downtime_file=/var/lib/nagios2/downtime.dat
+command_file=/var/lib/nagios3/rw/nagios.cmd
+
+
+
+# EXTERNAL COMMAND BUFFER SLOTS
+# This settings is used to tweak the number of items or "slots" that
+# the Nagios daemon should allocate to the buffer that holds incoming 
+# external commands before they are processed.  As external commands 
+# are processed by the daemon, they are removed from the buffer.  
+
+external_command_buffer_slots=4096
 
 
@@ -168 +167 @@
 # in when it is running in daemon mode.
 
-lock_file=/var/run/nagios2/nagios2.pid
+lock_file=/var/run/nagios3/nagios3.pid
 
 
@@ -178 +177 @@
 # running.
 
-temp_file=/var/cache/nagios2/nagios.tmp
+temp_file=/var/cache/nagios3/nagios.tmp
+
+
+
+# TEMP PATH
+# This is path where Nagios can create temp files for service and
+# host check results, etc.
+
+temp_path=/tmp
 
 
@@ -198 +205 @@
 # the module at startup are seperated from the module path by a space.
 #
+#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+# WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING
+#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+#
+# Do NOT overwrite modules while they are being used by Nagios or Nagios
+# will crash in a fiery display of SEGFAULT glory.  This is a bug/limitation
+# either in dlopen(), the kernel, and/or the filesystem.  And maybe Nagios...
+#
+# The correct/safe way of updating a module is by using one of these methods:
+#    1. Shutdown Nagios, replace the module file, restart Nagios
+#    2. Delete the original module file, move the new module file into place, restart Nagios
+#
 # Example:
 #
@@ -204 +223 @@
 #broker_module=/somewhere/module1.o
 #broker_module=/somewhere/module2.o arg1 arg2=3 debug=0
-
 
 
@@ -225 +243 @@
 # placed (assuming you've chosen to do log rotation).
 
-log_archive_path=/var/log/nagios2/archives
+log_archive_path=/var/log/nagios3/archives
 
 
@@ -231 +249 @@
 # LOGGING OPTIONS
 # If you want messages logged to the syslog facility, as well as the
-# NetAlarm log file set this option to 1.  If not, set it to 0.
+# Nagios log file set this option to 1.  If not, set it to 0.
 
 use_syslog=0
@@ -396 +414 @@
 
 
-# SERVICE CHECK REAPER FREQUENCY
+# HOST AND SERVICE CHECK REAPER FREQUENCY
 # This is the frequency (in seconds!) that Nagios will process
-# the results of services that have been checked.
-
-service_reaper_frequency=10
-
+# the results of host and service checks.
+
+check_result_reaper_frequency=10
+
+
+
+
+# MAX CHECK RESULT REAPER TIME
+# This is the max amount of time (in seconds) that  a single
+# check result reaper event will be allowed to run before 
+# returning control back to Nagios so it can perform other
+# duties.
+
+max_check_result_reaper_time=30
+
+
+
+
+# CHECK RESULT PATH
+# This is directory where Nagios stores the results of host and
+# service checks that have not yet been processed.
+#
+# Note: Make sure that only one instance of Nagios has access
+# to this directory!  
+
+check_result_path=/var/lib/nagios3/spool/checkresults
+
+
+
+
+# MAX CHECK RESULT FILE AGE
+# This option determines the maximum age (in seconds) which check
+# result files are considered to be valid.  Files older than this 
+# threshold will be mercilessly deleted without further processing.
+
+max_check_result_file_age=3600
+
+
+
+
+# CACHED HOST CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous host check is considered current.
+# Cached host states (from host checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to the host check logic.
+# Too high of a value for this option may result in inaccurate host
+# states being used by Nagios, while a lower value may result in a
+# performance hit for host checks.  Use a value of 0 to disable host
+# check caching.
+
+cached_host_check_horizon=15
+
+
+
+# CACHED SERVICE CHECK HORIZON
+# This option determines the maximum amount of time (in seconds)
+# that the state of a previous service check is considered current.
+# Cached service states (from service checks that were performed more
+# recently that the timeframe specified by this value) can immensely
+# improve performance in regards to predictive dependency checks.
+# Use a value of 0 to disable service check caching.
+
+cached_service_check_horizon=15
+
+
+
+# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
+# This option determines whether or not Nagios will attempt to execute
+# checks of hosts when it predicts that future dependency logic test
+# may be needed.  These predictive checks can help ensure that your
+# host dependency logic works well.
+# Values:
+#  0 = Disable predictive checks
+#  1 = Enable predictive checks (default)
+
+enable_predictive_host_dependency_checks=1
+
+
+
+# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
+# This option determines whether or not Nagios will attempt to execute
+# checks of service when it predicts that future dependency logic test
+# may be needed.  These predictive checks can help ensure that your
+# service dependency logic works well.
+# Values:
+#  0 = Disable predictive checks
+#  1 = Enable predictive checks (default)
+
+enable_predictive_service_dependency_checks=1
+
+
+
+# SOFT STATE DEPENDENCIES
+# This option determines whether or not Nagios will use soft state 
+# information when checking host and service dependencies. Normally 
+# Nagios will only use the latest hard host or service state when 
+# checking dependencies. If you want it to use the latest state (regardless
+# of whether its a soft or hard state type), enable this option. 
+# Values:
+#  0 = Don't use soft state dependencies (default) 
+#  1 = Use soft state dependencies 
+
+soft_state_dependencies=0
+
+
+
+# TIME CHANGE ADJUSTMENT THRESHOLDS
+# These options determine when Nagios will react to detected changes
+# in system time (either forward or backwards).
+
+#time_change_threshold=900
 
 
@@ -426 +552 @@
 
 auto_rescheduling_interval=30
-
 
 
@@ -465 +590 @@
 notification_timeout=30
 ocsp_timeout=5
-perfdata_timeout=30
+perfdata_timeout=5
 
 
@@ -491 +616 @@
 # variable is set to 1.
 
-state_retention_file=/var/lib/nagios2/retention.dat
+state_retention_file=/var/lib/nagios3/retention.dat
 
 
@@ -525 +650 @@
 # value to 1.  If not, set this value to 0.
 
-use_retained_scheduling_info=0
+use_retained_scheduling_info=1
+
+
+
+# RETAINED ATTRIBUTE MASKS (ADVANCED FEATURE)
+# The following variables are used to specify specific host and
+# service attributes that should *not* be retained by Nagios during
+# program restarts.
+#
+# The values of the masks are bitwise ANDs of values specified
+# by the "MODATTR_" definitions found in include/common.h.  
+# For example, if you do not want the current enabled/disabled state
+# of flap detection and event handlers for hosts to be retained, you
+# would use a value of 24 for the host attribute mask...
+# MODATTR_EVENT_HANDLER_ENABLED (8) + MODATTR_FLAP_DETECTION_ENABLED (16) = 24
+
+# This mask determines what host attributes are not retained
+retained_host_attribute_mask=0
+
+# This mask determines what service attributes are not retained
+retained_service_attribute_mask=0
+
+# These two masks determine what process attributes are not retained.
+# There are two masks, because some process attributes have host and service
+# options.  For example, you can disable active host checks, but leave active
+# service checks enabled.
+retained_process_host_attribute_mask=0
+retained_process_service_attribute_mask=0
+
+# These two masks determine what contact attributes are not retained.
+# There are two masks, because some contact attributes have host and
+# service options.  For example, you can disable host notifications for
+# a contact, but leave service notifications enabled for them.
+retained_contact_host_attribute_mask=0
+retained_contact_service_attribute_mask=0
 
 
@@ -663 +822 @@
 
 
-
 # HOST AND SERVICE PERFORMANCE DATA FILE MODES
 # This option determines whether or not the host and service
 # performance data files are opened in write ("w") or append ("a")
-# mode.  Unless you are the files are named pipes, you will probably
-# want to use the default mode of append ("a").
+# mode. If you want to use named pipes, you should use the special
+# pipe ("p") mode which avoid blocking at startup, otherwise you will
+# likely want the defult append ("a") mode.
 
 #host_perfdata_file_mode=a
@@ -711 +870 @@
 # This is the command that is run for every service check that is
 # processed by Nagios.  This command is executed only if the
-# obsess_over_service option (above) is set to 1.  The command 
+# obsess_over_services option (above) is set to 1.  The command 
 # argument is the short name of a command definition that you
 # define in your host configuration file. Read the HTML docs for
@@ -720 +879 @@
 
 
-# ORPHANED SERVICE CHECK OPTION
-# This determines whether or not Nagios will periodically 
-# check for orphaned services.  Since service checks are not
-# rescheduled until the results of their previous execution 
+# OBSESS OVER HOST CHECKS OPTION
+# This determines whether or not Nagios will obsess over host
+# checks and run the ochp_command defined below.  Unless you're
+# planning on implementing distributed monitoring, do not enable
+# this option.  Read the HTML docs for more information on
+# implementing distributed monitoring.
+# Values: 1 = obsess over hosts, 0 = do not obsess (default)
+
+obsess_over_hosts=0
+
+
+
+# OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND
+# This is the command that is run for every host check that is
+# processed by Nagios.  This command is executed only if the
+# obsess_over_hosts option (above) is set to 1.  The command 
+# argument is the short name of a command definition that you
+# define in your host configuration file. Read the HTML docs for
+# more information on implementing distributed monitoring.
+
+#ochp_command=somecommand
+
+
+
+# TRANSLATE PASSIVE HOST CHECKS OPTION
+# This determines whether or not Nagios will translate
+# DOWN/UNREACHABLE passive host check results into their proper
+# state for this instance of Nagios.  This option is useful
+# if you have distributed or failover monitoring setup.  In
+# these cases your other Nagios servers probably have a different
+# "view" of the network, with regards to the parent/child relationship
+# of hosts.  If a distributed monitoring server thinks a host
+# is DOWN, it may actually be UNREACHABLE from the point of
+# this Nagios instance.  Enabling this option will tell Nagios
+# to translate any DOWN or UNREACHABLE host states it receives
+# passively into the correct state from the view of this server.
+# Values: 1 = perform translation, 0 = do not translate (default)
+
+translate_passive_host_checks=0
+
+
+
+# PASSIVE HOST CHECKS ARE SOFT OPTION
+# This determines whether or not Nagios will treat passive host
+# checks as being HARD or SOFT.  By default, a passive host check
+# result will put a host into a HARD state type.  This can be changed
+# by enabling this option.
+# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT
+
+passive_host_checks_are_soft=0
+
+
+
+# ORPHANED HOST/SERVICE CHECK OPTIONS
+# These options determine whether or not Nagios will periodically 
+# check for orphaned host service checks.  Since service checks are
+# not rescheduled until the results of their previous execution 
 # instance are processed, there exists a possibility that some
-# checks may never get rescheduled.  This seems to be a rare
+# checks may never get rescheduled.  A similar situation exists for
+# host checks, although the exact scheduling details differ a bit
+# from service checks.  Orphaned checks seem to be a rare
 # problem and should not happen under normal circumstances.
 # If you have problems with service checks never getting
-# rescheduled, you might want to try enabling this option.
+# rescheduled, make sure you have orphaned service checks enabled.
 # Values: 1 = enable checks, 0 = disable checks
 
-check_for_orphaned_services=0
+check_for_orphaned_services=1
+check_for_orphaned_hosts=1
 
 
@@ -775 +990 @@
 
 
-# AGGREGATED STATUS UPDATES
-# This option determines whether or not Nagios will 
-# aggregate updates of host, service, and program status
-# data.  Normally, status data is updated immediately when
-# a change occurs.  This can result in high CPU loads if
-# you are monitoring a lot of services.  If you want Nagios
-# to only refresh status data every few seconds, disable
-# this option.
-# Values: 1 = enable aggregate updates, 0 = disable aggregate updates
-
-aggregate_status_updates=1
-
-
-
-# AGGREGATED STATUS UPDATE INTERVAL
-# Combined with the aggregate_status_updates option,
-# this option determines the frequency (in seconds!) that
-# Nagios will periodically dump program, host, and 
-# service status data.  If you are not using aggregated
-# status data updates, this option has no effect.
-
-status_update_interval=15
+
+# ADDITIONAL FRESHNESS THRESHOLD LATENCY
+# This setting determines the number of seconds that Nagios
+# will add to any host and service freshness thresholds that
+# it calculates (those not explicitly specified by the user).
+
+additional_freshness_latency=15
+
 
 
@@ -812 +1013 @@
 #         0 = disable flap detection (default)
 
-enable_flap_detection=0
+enable_flap_detection=1
 
 
@@ -837 +1038 @@
 #
 
-date_format=us
+date_format=iso8601
+
+
+
+
+# TIMEZONE OFFSET
+# This option is used to override the default timezone that this
+# instance of Nagios runs in.  If not specified, Nagios will use
+# the system configured timezone.
+#
+# NOTE: In order to display the correct timezone in the CGIs, you
+# will also need to alter the Apache directives for the CGI path 
+# to include your timezone.  Example:
+#
+#   <Directory "/usr/local/nagios/sbin/">
+#      SetEnv TZ "Australia/Brisbane"
+#      ...
+#   </Directory>
+
+#use_timezone=US/Mountain
+#use_timezone=Australia/Brisbane
+
 
 
@@ -846 +1068 @@
 # Nagios with embedded Perl support, this option has no effect.
 
-p1_file=/usr/lib/nagios2/p1.pl
+p1_file=/usr/lib/nagios3/p1.pl
+
+
+
+# EMBEDDED PERL INTERPRETER OPTION
+# This option determines whether or not the embedded Perl interpreter
+# will be enabled during runtime.  This option has no effect if Nagios
+# has not been compiled with support for embedded Perl.
+# Values: 0 = disable interpreter, 1 = enable interpreter
+
+enable_embedded_perl=1
+
+
+
+# EMBEDDED PERL USAGE OPTION
+# This option determines whether or not Nagios will process Perl plugins
+# and scripts with the embedded Perl interpreter if the plugins/scripts
+# do not explicitly indicate whether or not it is okay to do so. Read
+# the HTML documentation on the embedded Perl interpreter for more 
+# information on how this option works.
+
+use_embedded_perl_implicitly=1
 
 
@@ -903 +1146 @@
 
 
-
-# ADMINISTRATOR EMAIL ADDRESS
-# The email address of the administrator of *this* machine (the one
-# doing the monitoring).  Nagios never uses this value itself, but
-# you can access this value by using the $ADMINEMAIL$ macro in your
-# notification commands.
-
-admin_email=nagios
-
-
-
-# ADMINISTRATOR PAGER NUMBER/ADDRESS
-# The pager number/address for the administrator of *this* machine.
-# Nagios never uses this value itself, but you can access this
-# value by using the $ADMINPAGER$ macro in your notification
+# ADMINISTRATOR EMAIL/PAGER ADDRESSES
+# The email and pager address of a global administrator (likely you).
+# Nagios never uses these values itself, but you can access them by
+# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
 # commands.
 
-admin_pager=pagenagios
+admin_email=sipb-nagios@mit.edu
+admin_pager=sipb-nagios@mit.edu
 
 
@@ -928 +1161 @@
 # a core dump when it runs as a daemon.  Note that it is generally
 # considered bad form to allow this, but it may be useful for
-# debugging purposes.
+# debugging purposes.  Enabling this option doesn't guarantee that
+# a core file will be produced, but that's just life...
 # Values: 1 - Allow core dumps
 #         0 - Do not allow core dumps (default)
@@ -935 +1169 @@
 
 
-#process_performance_data=1
-#service_perfdata_file=/home/noc/ng/log/perfdata
-#service_perfdata_file_template=$LASTSERVICECHECK$||$HOSTNAME$||$SERVICEDESC$||$SERVICEOUTPUT$||$SERVICEPERFDATA$
-#service_perfdata_file_mode=a
-#service_perfdata_file_processing_interval=60
-#service_perfdata_file_processing_command=ng-service-perfdata
-# EOF (End of file)
+
+# LARGE INSTALLATION TWEAKS OPTION
+# This option determines whether or not Nagios will take some shortcuts
+# which can save on memory and CPU usage in large Nagios installations.
+# Read the documentation for more information on the benefits/tradeoffs
+# of enabling this option.
+# Values: 1 - Enabled tweaks
+#         0 - Disable tweaks (default)
+
+use_large_installation_tweaks=0
+
+
+
+# ENABLE ENVIRONMENT MACROS
+# This option determines whether or not Nagios will make all standard
+# macros available as environment variables when host/service checks
+# and system commands (event handlers, notifications, etc.) are
+# executed.  Enabling this option can cause performance issues in 
+# large installations, as it will consume a bit more memory and (more
+# importantly) consume more CPU.
+# Values: 1 - Enable environment variable macros (default)
+#         0 - Disable environment variable macros
+
+enable_environment_macros=1
+
+
+
+# CHILD PROCESS MEMORY OPTION
+# This option determines whether or not Nagios will free memory in
+# child processes (processed used to execute system commands and host/
+# service checks).  If you specify a value here, it will override
+# program defaults.
+# Value: 1 - Free memory in child processes
+#        0 - Do not free memory in child processes
+
+#free_child_process_memory=1
+
+
+
+# CHILD PROCESS FORKING BEHAVIOR
+# This option determines how Nagios will fork child processes
+# (used to execute system commands and host/service checks).  Normally
+# child processes are fork()ed twice, which provides a very high level
+# of isolation from problems.  Fork()ing once is probably enough and will
+# save a great deal on CPU usage (in large installs), so you might
+# want to consider using this.  If you specify a value here, it will
+# program defaults.
+# Value: 1 - Child processes fork() twice
+#        0 - Child processes fork() just once
+
+#child_processes_fork_twice=1
+
+
+
+# DEBUG LEVEL
+# This option determines how much (if any) debugging information will
+# be written to the debug file.  OR values together to log multiple
+# types of information.
+# Values: 
+#          -1 = Everything
+#          0 = Nothing
+#          1 = Functions
+#          2 = Configuration
+#          4 = Process information
+#          8 = Scheduled events
+#          16 = Host/service checks
+#          32 = Notifications
+#          64 = Event broker
+#          128 = External commands
+#          256 = Commands
+#          512 = Scheduled downtime
+#          1024 = Comments
+#          2048 = Macros
+
+debug_level=0
+
+
+
+# DEBUG VERBOSITY
+# This option determines how verbose the debug log out will be.
+# Values: 0 = Brief output
+#         1 = More detailed
+#         2 = Very detailed
+
+debug_verbosity=1
+
+
+
+# DEBUG FILE
+# This option determines where Nagios should write debugging information.
+
+debug_file=/var/lib/nagios3/nagios.debug
+
+
+
+# MAX DEBUG FILE SIZE
+# This option determines the maximum size (in bytes) of the debug file.  If
+# the file grows larger than this size, it will be renamed with a .old
+# extension.  If a file already exists with a .old extension it will
+# automatically be deleted.  This helps ensure your disk space usage doesn't
+# get out of control when debugging Nagios.
+
+max_debug_file_size=1000000
+
+