Author: glen Date: Sun Oct 5 02:09:16 2008 New Revision: 9890 Modified: nagios-config/trunk/cgi.cfg nagios-config/trunk/contacts.cfg nagios-config/trunk/nagios.cfg Log: - partial update to nagios 3.0.2
Modified: nagios-config/trunk/cgi.cfg ============================================================================== --- nagios-config/trunk/cgi.cfg (original) +++ nagios-config/trunk/cgi.cfg Sun Oct 5 02:09:16 2008 @@ -1,8 +1,8 @@ ################################################################# # # CGI.CFG - CGI Configuration File for Nagios -# $Id$ # +# $Id$ ################################################################# @@ -46,22 +46,14 @@ -# 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. +# 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/check_nagios /var/lib/nagios/status.log 5 '/usr/sbin/nagios' @@ -248,6 +240,16 @@ +# 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 + + + + # SOUND OPTIONS # These options allow you to specify an optional audio file # that should be played in your browser window when there are @@ -272,4 +274,48 @@ #service_unknown_sound=warning.wav #normal_sound=noproblem.wav + + +# URL TARGET FRAMES +# These options determine the target frames in which notes and +# action URLs will open. + +action_url_target=_blank +notes_url_target=_blank + + + + +# LOCK AUTHOR NAMES OPTION +# This option determines whether users can change the author name +# when submitting comments, scheduling downtime. If disabled, the +# author names will be locked into their contact name, as defined in Nagios. +# Values: 0 = allow editing author names +# 1 = lock author names (disallow editing) + +lock_author_names=1 + + + + +# SPLUNK INTEGRATION OPTIONS +# These options allow you to enable integration with Splunk +# in the web interface. If enabled, you'll be presented with +# "Splunk It" links in various places in the CGIs (log file, +# alert history, host/service detail, etc). Useful if you're +# trying to research why a particular problem occurred. +# For more information on Splunk, visit http://www.splunk.com/ + +# This option determines whether the Splunk integration is enabled +# Values: 0 = disable Splunk integration +# 1 = enable Splunk integration + +#enable_splunk_integration=1 + + +# This option should be the URL used to access your instance of Splunk + +#splunk_url=http://127.0.0.1:8000/ + + # vim:ts=8:sw=8:syn=cfg Modified: nagios-config/trunk/contacts.cfg ============================================================================== --- nagios-config/trunk/contacts.cfg (original) +++ nagios-config/trunk/contacts.cfg Sun Oct 5 02:09:16 2008 @@ -1,11 +1,11 @@ ################################################################################ # Object config file for Nagios -# $Id: $ +# $Id$ # ################################################################################ ################################################################################ -# CONTACT DEFINITIONS +# CONTACTS.CFG - CONTACT/CONTACTGROUP DEFINITIONS # ################################################################################ @@ -27,4 +27,4 @@ pager [EMAIL PROTECTED] } -# vim:ts=8:sw=8:syn=nagios +# vim:ts=8:sw=8:ft=nagios Modified: nagios-config/trunk/nagios.cfg ============================================================================== --- nagios-config/trunk/nagios.cfg (original) +++ nagios-config/trunk/nagios.cfg Sun Oct 5 02:09:16 2008 @@ -21,43 +21,29 @@ # 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/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. - -#cfg_file=/etc/nagios/minimal.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 - -# 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 +# 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/nagios/objects/commands.cfg +cfg_file=/etc/nagios/objects/contacts.cfg +cfg_file=/etc/nagios/objects/timeperiods.cfg +cfg_file=/etc/nagios/objects/templates.cfg + +# Definitions for monitoring the local (Linux) host +cfg_file=/etc/nagios/objects/localhost.cfg + +# Definitions for monitoring a Windows machine +#cfg_file=/etc/nagios/objects/windows.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 + # You can also tell Nagios to process all config files (with a .cfg # extension) in a particular directory by using the cfg_dir @@ -73,6 +59,7 @@ + # OBJECT CACHE FILE # This option determines where object definitions are cached when # Nagios starts/restarts. The CGIs read object definitions from @@ -84,6 +71,22 @@ +# 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/nagios/objects.precache + + + # RESOURCE FILE # This is an optional resource file that contains $USERx$ macro # definitions. Multiple resource files can be specified by using @@ -100,13 +103,22 @@ # STATUS FILE # This is where the current status of all monitored services and # hosts is stored. Its contents are read and processed by the CGIs. -# The contentsof the status file are deleted every time Nagios +# The contents of the status file are deleted every time Nagios # restarts. status_file=/var/lib/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. @@ -128,8 +140,8 @@ # 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 @@ -148,7 +160,6 @@ # 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=-1 @@ -166,19 +177,13 @@ -# COMMENT FILE -# This is the file that Nagios will use for storing host and service -# comments. - -comment_file=/var/lib/nagios/comments.dat +# 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. - - -# DOWNTIME FILE -# This is the file that Nagios will use for storing host and service -# downtime data. - -downtime_file=/var/lib/nagios/downtime.dat +external_command_buffer_slots=4096 @@ -200,6 +205,14 @@ +# 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 @@ -216,16 +229,27 @@ # 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: # -# nebmodule=<modulepath> [moduleargs] +# broker_module=<modulepath> [moduleargs] #broker_module=/somewhere/module1.o #broker_module=/somewhere/module2.o arg1 arg2=3 debug=0 - # LOG ROTATION METHOD # This is the log rotation method that Nagios should use to rotate # the main log file. Values are as follows.. @@ -249,7 +273,7 @@ # 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 @@ -313,7 +337,7 @@ # PASSIVE CHECKS LOGGING OPTION # If you don't want Nagios to log passive host and service checks, set -# this value to 0. If passive service checks should be logged, set +# this value to 0. If passive checks should be logged, set # this value to 1. log_passive_checks=1 @@ -414,12 +438,112 @@ -# 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. + +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/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 + + -service_reaper_frequency=10 +# 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 @@ -447,7 +571,6 @@ - # AUTO-RESCHEDULING WINDOW # This option determines the "window" of time (in seconds) that # Nagios will look at when automatically rescheduling checks. @@ -543,7 +666,41 @@ # 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 @@ -653,8 +810,8 @@ # define in your host configuration file. Read the HTML docs for # more information on performance data. -host_perfdata_command=process-host-perfdata -service_perfdata_command=process-service-perfdata +#host_perfdata_command=process-host-perfdata +#service_perfdata_command=process-service-perfdata @@ -663,8 +820,8 @@ # Performance data is only written to these files if the # enable_performance_data option (above) is set to 1. -host_perfdata_file=/var/lib/nagios/host-perfdata -service_perfdata_file=/var/lib/nagios/service-perfdata +#host_perfdata_file=/var/lib/nagios/host-perfdata +#service_perfdata_file=/var/lib/nagios/service-perfdata @@ -676,19 +833,20 @@ # to the performance data file. Some examples of what you can do are # shown below. -host_perfdata_file_template=$TIMET$\t$HOSTNAME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$ -service_perfdata_file_template=$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEOUTPUT$\t$SERVICESTATE$\t$SERVICEPERFDATA$ +#host_perfdata_file_template=[HOSTPERFDATA]\t$TIMET$\t$HOSTNAME$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$ +#service_perfdata_file_template=[SERVICEPERFDATA]\t$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$ # 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 +#host_perfdata_file_mode=a +#service_perfdata_file_mode=a @@ -698,8 +856,8 @@ # below. A value of 0 indicates the files should not be periodically # processed. -host_perfdata_file_processing_interval=0 -service_perfdata_file_processing_interval=0 +#host_perfdata_file_processing_interval=0 +#service_perfdata_file_processing_interval=0 @@ -728,7 +886,7 @@ # 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. @@ -737,18 +895,74 @@ -# 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 <<diff output has been trimmed to 500 lines, 203 line(s) remained.>> _______________________________________________ pld-cvs-commit mailing list [email protected] http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit
