Adjust for nagios 4 on noc01
This commit is contained in:
Kevin Fenzi
parent
a8684a9d4d
commit
81de968011
1 changed files with 528 additions and 159 deletions
|
|
@ -1,12 +1,11 @@
|
|||
##############################################################################
|
||||
#
|
||||
# NAGIOS.CFG - Sample Main Config File for Nagios
|
||||
# NAGIOS.CFG - Sample Main Config File for Nagios 4.0.8
|
||||
#
|
||||
# Read the documentation for more information on this configuration
|
||||
# file. I've provided some comments here, but things may not be so
|
||||
# clear without further explanation.
|
||||
#
|
||||
# Last Modified: 11-23-2005
|
||||
#
|
||||
##############################################################################
|
||||
|
||||
|
|
@ -21,61 +20,45 @@ log_file=/var/log/nagios/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...
|
||||
# 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.
|
||||
|
||||
# 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.
|
||||
# You can specify individual object config files as shown below:
|
||||
#cfg_file=/etc/nagios/objects/commands.cfg
|
||||
#cfg_file=/etc/nagios/objects/contacts.cfg
|
||||
cfg_file=/etc/nagios/timeperiods.cfg
|
||||
#cfg_file=/etc/nagios/objects/templates.cfg
|
||||
cfg_file=/etc/nagios/escalations.cfg
|
||||
cfg_file=/etc/nagios/checkcommands.cfg
|
||||
|
||||
# Misc commands (notification and event handler commands, etc)
|
||||
cfg_file=/etc/nagios/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.
|
||||
# Definitions for monitoring the local (Linux) host
|
||||
#cfg_file=/etc/nagios/objects/localhost.cfg
|
||||
|
||||
#cfg_file=/etc/nagios/minimal.cfg
|
||||
# Definitions for monitoring a Windows machine
|
||||
#cfg_file=/etc/nagios/objects/windows.cfg
|
||||
|
||||
#cfg_file=/etc/nagios/contactgroups.cfg
|
||||
#cfg_file=/etc/nagios/contacts.cfg
|
||||
#cfg_file=/etc/nagios/dependencies.cfg
|
||||
cfg_file=/etc/nagios/escalations.cfg
|
||||
#cfg_file=/etc/nagios/hostgroups.cfg
|
||||
#cfg_file=/etc/nagios/hosts.cfg
|
||||
#cfg_file=/etc/nagios/services.cfg
|
||||
cfg_file=/etc/nagios/timeperiods.cfg
|
||||
# Definitions for monitoring a router/switch
|
||||
#cfg_file=/etc/nagios/objects/switch.cfg
|
||||
|
||||
# Definitions for monitoring a network printer
|
||||
#cfg_file=/etc/nagios/objects/printer.cfg
|
||||
|
||||
# Extended host/service info definitions are now stored along with
|
||||
# other object definitions:
|
||||
#cfg_file=/etc/nagios/hostextinfo.cfg
|
||||
#cfg_file=/etc/nagios/serviceextinfo.cfg
|
||||
|
||||
# You can also tell Nagios to process all config files (with a .cfg
|
||||
# extension) in a particular directory by using the cfg_dir
|
||||
# directive as shown below:
|
||||
cfg_dir=/etc/nagios/hosts
|
||||
cfg_dir=/etc/nagios/hostgroups
|
||||
cfg_dir=/etc/nagios/services
|
||||
cfg_dir=/etc/nagios/contacts
|
||||
cfg_dir=/etc/nagios/contactgroups
|
||||
cfg_dir=/etc/nagios/servicegroups
|
||||
cfg_dir=/etc/nagios/servicedeps
|
||||
|
||||
|
||||
#cfg_dir=/etc/nagios/servers
|
||||
#cfg_dir=/etc/nagios/printers
|
||||
#cfg_dir=/etc/nagios/switches
|
||||
#cfg_dir=/etc/nagios/routers
|
||||
|
||||
cfg_dir=/etc/nagios/conf.d
|
||||
|
||||
|
||||
|
||||
|
||||
# OBJECT CACHE FILE
|
||||
|
|
@ -89,6 +72,22 @@ object_cache_file=/var/log/nagios/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/log/nagios/objects.precache
|
||||
|
||||
|
||||
|
||||
# RESOURCE FILE
|
||||
# This is an optional resource file that contains $USERx$ macro
|
||||
# definitions. Multiple resource files can be specified by using
|
||||
|
|
@ -112,6 +111,15 @@ status_file=/var/log/nagios/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
|
||||
|
||||
|
||||
|
||||
# NAGIOS USER
|
||||
# This determines the effective user that Nagios should run as.
|
||||
# You can either supply a username or a UID.
|
||||
|
|
@ -133,32 +141,13 @@ nagios_group=nagios
|
|||
# for external commands (in the command file defined below). By default
|
||||
# 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
|
||||
|
||||
|
||||
|
||||
# EXTERNAL COMMAND CHECK INTERVAL
|
||||
# This is the interval at which Nagios should check for external commands.
|
||||
# This value works of the interval_length you specify later. If you leave
|
||||
# that at its default value of 60 (seconds), a value of 1 here will cause
|
||||
# Nagios to check for external commands every minute. If you specify a
|
||||
# number followed by an "s" (i.e. 15s), this will be interpreted to mean
|
||||
# actual seconds rather than a multiple of the interval_length variable.
|
||||
# Note: In addition to reading the external command file at regularly
|
||||
# scheduled intervals, Nagios will also check for external commands after
|
||||
# event handlers are executed.
|
||||
# NOTE: Setting this value to -1 causes Nagios to check the external
|
||||
# command file as often as possible.
|
||||
|
||||
#command_check_interval=1
|
||||
#command_check_interval=15s
|
||||
command_check_interval=15s
|
||||
|
||||
|
||||
|
||||
# EXTERNAL COMMAND FILE
|
||||
# This is the file that Nagios checks for external command requests.
|
||||
# It is also where the command CGI will write commands that are submitted
|
||||
|
|
@ -171,19 +160,10 @@ command_file=/var/spool/nagios/cmd/nagios.cmd
|
|||
|
||||
|
||||
|
||||
# COMMENT FILE
|
||||
# This is the file that Nagios will use for storing host and service
|
||||
# comments.
|
||||
# QUERY HANDLER INTERFACE
|
||||
# This is the socket that is created for the Query Handler interface
|
||||
|
||||
comment_file=/var/log/nagios/comments.dat
|
||||
|
||||
|
||||
|
||||
# DOWNTIME FILE
|
||||
# This is the file that Nagios will use for storing host and service
|
||||
# downtime data.
|
||||
|
||||
downtime_file=/var/log/nagios/downtime.dat
|
||||
query_socket=/var/spool/nagios/cmd/nagios.qh
|
||||
|
||||
|
||||
|
||||
|
|
@ -191,7 +171,7 @@ downtime_file=/var/log/nagios/downtime.dat
|
|||
# This is the lockfile that Nagios will use to store its PID number
|
||||
# in when it is running in daemon mode.
|
||||
|
||||
lock_file=/var/run/nagios.pid
|
||||
lock_file=/var/run/nagios/nagios.pid
|
||||
|
||||
|
||||
|
||||
|
|
@ -205,13 +185,21 @@ temp_file=/var/log/nagios/nagios.tmp
|
|||
|
||||
|
||||
|
||||
# TEMP PATH
|
||||
# This is path where Nagios can create temp files for service and
|
||||
# host check results, etc.
|
||||
|
||||
temp_path=/tmp
|
||||
|
||||
|
||||
|
||||
# EVENT BROKER OPTIONS
|
||||
# Controls what (if any) data gets sent to the event broker.
|
||||
# Values: 0 = Broker nothing
|
||||
# -1 = Broker everything
|
||||
# <other> = See documentation
|
||||
|
||||
event_broker_options=0
|
||||
event_broker_options=-1
|
||||
|
||||
|
||||
|
||||
|
|
@ -221,6 +209,18 @@ event_broker_options=0
|
|||
# to load more than one module. Arguments that should be passed to
|
||||
# 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:
|
||||
#
|
||||
# broker_module=<modulepath> [moduleargs]
|
||||
|
|
@ -230,7 +230,6 @@ event_broker_options=0
|
|||
|
||||
|
||||
|
||||
|
||||
# LOG ROTATION METHOD
|
||||
# This is the log rotation method that Nagios should use to rotate
|
||||
# the main log file. Values are as follows..
|
||||
|
|
@ -254,7 +253,7 @@ log_archive_path=/var/log/nagios/archives
|
|||
|
||||
# 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=1
|
||||
|
||||
|
|
@ -305,6 +304,15 @@ log_initial_states=0
|
|||
|
||||
|
||||
|
||||
# CURRENT STATES LOGGING OPTION
|
||||
# If you don't want Nagios to log all current host and service states
|
||||
# after log has been rotated to the main log file, you can disable this
|
||||
# option by setting this value to 0. Default value is 1.
|
||||
|
||||
log_current_states=1
|
||||
|
||||
|
||||
|
||||
# EXTERNAL COMMANDS LOGGING OPTION
|
||||
# If you don't want Nagios to log external commands, set this value
|
||||
# to 0. If external commands should be logged, set this value to 1.
|
||||
|
|
@ -419,15 +427,123 @@ max_concurrent_checks=0
|
|||
|
||||
|
||||
|
||||
# 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.
|
||||
# the results of host and service checks.
|
||||
|
||||
service_reaper_frequency=10
|
||||
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/log/nagios/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
|
||||
|
||||
|
||||
|
||||
# AUTO-RESCHEDULING OPTION
|
||||
# This option determines whether or not Nagios will attempt to
|
||||
# automatically reschedule active host and service checks to
|
||||
|
|
@ -452,7 +568,6 @@ auto_rescheduling_interval=30
|
|||
|
||||
|
||||
|
||||
|
||||
# AUTO-RESCHEDULING WINDOW
|
||||
# This option determines the "window" of time (in seconds) that
|
||||
# Nagios will look at when automatically rescheduling checks.
|
||||
|
|
@ -467,14 +582,6 @@ auto_rescheduling_window=180
|
|||
|
||||
|
||||
|
||||
# SLEEP TIME
|
||||
# This is the number of seconds to sleep between checking for system
|
||||
# events and service checks that need to be run.
|
||||
|
||||
sleep_time=0.25
|
||||
|
||||
|
||||
|
||||
# TIMEOUT VALUES
|
||||
# These options control how much time Nagios will allow various
|
||||
# types of commands to execute before killing them off. Options
|
||||
|
|
@ -511,7 +618,7 @@ retain_state_information=1
|
|||
# service state information before it shuts down. The state
|
||||
# information in this file is also read immediately prior to
|
||||
# starting to monitor the network when Nagios is restarted.
|
||||
# This file is used only if the preserve_state_information
|
||||
# This file is used only if the retain_state_information
|
||||
# variable is set to 1.
|
||||
|
||||
state_retention_file=/var/log/nagios/retention.dat
|
||||
|
|
@ -548,7 +655,41 @@ use_retained_program_state=1
|
|||
# If you want to use retained scheduling info, set this
|
||||
# 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
|
||||
|
||||
|
||||
|
||||
|
|
@ -562,6 +703,31 @@ interval_length=60
|
|||
|
||||
|
||||
|
||||
# CHECK FOR UPDATES
|
||||
# This option determines whether Nagios will automatically check to
|
||||
# see if new updates (releases) are available. It is recommend that you
|
||||
# enable this option to ensure that you stay on top of the latest critical
|
||||
# patches to Nagios. Nagios is critical to you - make sure you keep it in
|
||||
# good shape. Nagios will check once a day for new updates. Data collected
|
||||
# by Nagios Enterprises from the update check is processed in accordance
|
||||
# with our privacy policy - see http://api.nagios.org for details.
|
||||
|
||||
check_for_updates=1
|
||||
|
||||
|
||||
|
||||
# BARE UPDATE CHECK
|
||||
# This option deterines what data Nagios will send to api.nagios.org when
|
||||
# it checks for updates. By default, Nagios will send information on the
|
||||
# current version of Nagios you have installed, as well as an indicator as
|
||||
# to whether this was a new installation or not. Nagios Enterprises uses
|
||||
# this data to determine the number of users running specific version of
|
||||
# Nagios. Enable this option if you do not want this information to be sent.
|
||||
|
||||
bare_update_check=0
|
||||
|
||||
|
||||
|
||||
# AGGRESSIVE HOST CHECKING OPTION
|
||||
# If you don't want to turn on aggressive host checking features, set
|
||||
# this value to 0 (the default). Otherwise set this value to 1 to
|
||||
|
|
@ -668,8 +834,8 @@ process_performance_data=0
|
|||
# Performance data is only written to these files if the
|
||||
# enable_performance_data option (above) is set to 1.
|
||||
|
||||
#host_perfdata_file=/tmp/host-perfdata
|
||||
#service_perfdata_file=/tmp/service-perfdata
|
||||
#host_perfdata_file=/var/log/nagios/host-perfdata
|
||||
#service_perfdata_file=/var/log/nagios/service-perfdata
|
||||
|
||||
|
||||
|
||||
|
|
@ -686,12 +852,12 @@ process_performance_data=0
|
|||
|
||||
|
||||
|
||||
|
||||
# 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
|
||||
#service_perfdata_file_mode=a
|
||||
|
|
@ -719,6 +885,18 @@ process_performance_data=0
|
|||
|
||||
|
||||
|
||||
# HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS
|
||||
# These options determine wether the core will process empty perfdata
|
||||
# results or not. This is needed for distributed monitoring, and intentionally
|
||||
# turned on by default.
|
||||
# If you don't require empty perfdata - saving some cpu cycles
|
||||
# on unwanted macro calculation - you can turn that off. Be careful!
|
||||
# Values: 1 = enable, 0 = disable
|
||||
|
||||
#host_perfdata_process_empty_results=1
|
||||
#service_perfdata_process_empty_results=1
|
||||
|
||||
|
||||
# OBSESS OVER SERVICE CHECKS OPTION
|
||||
# This determines whether or not Nagios will obsess over service
|
||||
# checks and run the ocsp_command defined below. Unless you're
|
||||
|
|
@ -734,7 +912,7 @@ obsess_over_services=0
|
|||
# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND
|
||||
# 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
|
||||
# more information on implementing distributed monitoring.
|
||||
|
|
@ -743,18 +921,74 @@ obsess_over_services=0
|
|||
|
||||
|
||||
|
||||
# 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
|
||||
|
||||
|
||||
|
||||
|
|
@ -774,7 +1008,23 @@ check_service_freshness=1
|
|||
# check the "freshness" of service check results. If you have
|
||||
# disabled service freshness checking, this option has no effect.
|
||||
|
||||
service_freshness_check_interval=45
|
||||
service_freshness_check_interval=60
|
||||
|
||||
|
||||
|
||||
# SERVICE CHECK TIMEOUT STATE
|
||||
# This setting determines the state Nagios will report when a
|
||||
# service check times out - that is does not respond within
|
||||
# service_check_timeout seconds. This can be useful if a
|
||||
# machine is running at too high a load and you do not want
|
||||
# to consider a failed service check to be critical (the default).
|
||||
# Valid settings are:
|
||||
# c - Critical (default)
|
||||
# u - Unknown
|
||||
# w - Warning
|
||||
# o - OK
|
||||
|
||||
service_check_timeout_state=c
|
||||
|
||||
|
||||
|
||||
|
|
@ -798,29 +1048,15 @@ host_freshness_check_interval=60
|
|||
|
||||
|
||||
|
||||
# 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
|
||||
# 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
|
||||
|
||||
|
||||
# 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
|
||||
|
||||
|
||||
|
||||
# FLAP DETECTION OPTION
|
||||
|
|
@ -858,18 +1094,29 @@ high_host_flap_threshold=20.0
|
|||
# euro (DD-MM-YYYY HH:MM:SS)
|
||||
# iso8601 (YYYY-MM-DD HH:MM:SS)
|
||||
# strict-iso8601 (YYYY-MM-DDTHH:MM:SS)
|
||||
|
||||
#
|
||||
|
||||
date_format=us
|
||||
|
||||
|
||||
|
||||
# P1.PL FILE LOCATION
|
||||
# This value determines where the p1.pl perl script (used by the
|
||||
# embedded Perl interpreter) is located. If you didn't compile
|
||||
# Nagios with embedded Perl support, this option has no effect.
|
||||
|
||||
p1_file=/usr/sbin/p1.pl
|
||||
# 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
|
||||
|
||||
|
||||
|
||||
|
|
@ -922,28 +1169,18 @@ use_regexp_matching=0
|
|||
# all the time (which can be annoying).
|
||||
# Values: 1 = enable true matching, 0 = disable true matching
|
||||
|
||||
use_true_regexp_matching=1
|
||||
use_true_regexp_matching=0
|
||||
|
||||
|
||||
|
||||
|
||||
# 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=nagios@localhost
|
||||
admin_pager=pagenagios@localhost
|
||||
|
||||
|
||||
|
||||
|
|
@ -951,22 +1188,154 @@ admin_pager=pagenagios
|
|||
# This option determines whether or not Nagios is allowed to create
|
||||
# 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)
|
||||
|
||||
daemon_dumps_core=0
|
||||
|
||||
# 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=1
|
||||
|
||||
# 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 is a very bad idea for anything but very small setups,
|
||||
# as it means plugins, notification scripts and eventhandlers may run
|
||||
# out of environment space. It will also cause a significant increase
|
||||
# in CPU- and memory usage and drastically reduce the number of checks
|
||||
# you can run.
|
||||
# Values: 1 - Enable environment variable macros
|
||||
# 0 - Disable environment variable macros (default)
|
||||
|
||||
enable_environment_macros=0
|
||||
|
||||
|
||||
|
||||
# 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/log/nagios/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
|
||||
|
||||
|
||||
|
||||
# Should we allow hostgroups to have no hosts, we default this to off since
|
||||
# that was the old behavior
|
||||
|
||||
allow_empty_hostgroup_assignment=0
|
||||
|
||||
|
||||
|
||||
# Normally worker count is dynamically allocated based on 1.5 * number of cpu's
|
||||
# with a minimum of 4 workers. This value will override the defaults
|
||||
|
||||
#check_workers=3
|
||||
|
||||
|
||||
|
||||
# EXPERIMENTAL load controlling options
|
||||
# To get current defaults based on your system issue a command to
|
||||
# the query handler. Please note that this is an experimental feature
|
||||
# and not meant for production use. Used incorrectly it can induce
|
||||
# enormous latency.
|
||||
# #core loadctl
|
||||
# jobs_max - The maximum amount of jobs to run at one time
|
||||
# jobs_min - The minimum amount of jobs to run at one time
|
||||
# jobs_limit - The maximum amount of jobs the current load lets us run
|
||||
# backoff_limit - The minimum backoff_change
|
||||
# backoff_change - # of jobs to remove from jobs_limit when backing off
|
||||
# rampup_limit - Minimum rampup_change
|
||||
# rampup_change - # of jobs to add to jobs_limit when ramping up
|
||||
# NOTE: The backoff_limit and rampup_limit are NOT used by anything currently,
|
||||
# so if your system is under load nothing will actively modify the jobs
|
||||
# even if you have these options enabled, they are for external
|
||||
# connector information only. However, if you change the jobs_max or
|
||||
# jobs_min manually here or through the query handler interface that
|
||||
# WILL affect your system
|
||||
#loadctl_options=jobs_max=100;backoff_limit=10;rampup_change=5
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue