-#############################################################################
-## THIS FILE IS COPIED TO THE FINAL LOCATION USING PUPPET
-## ITS AUTHORITATIVE HOME IS THE DSA-NAGIOS CONFIGURATION GIT
-#############################################################################
-
##############################################################################
#
-# NAGIOS.CFG - Sample Main Config File for Nagios
+# ICINGA.CFG - Sample Main Config File for Icinga
#
+# 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.
#
##############################################################################
# LOG FILE
# This is the main log file where service and host events are logged
-# for historical purposes. This should be the first option specified
+# for historical purposes. This should be the first option specified
# in the config file!!!
-log_file=/var/log/nagios3/nagios.log
+log_file=/var/log/icinga/icinga.log
# Commands definitions
-cfg_file=/etc/nagios3/commands.cfg
+cfg_file=/etc/icinga/commands.cfg
# Debian also defaults to using the check commands defined by the debian
# nagios-plugins package
cfg_dir=/etc/nagios-plugins/config
-# Debian uses by default a configuration directory where nagios3-common,
-# other packages and the local admin can dump or link configuration
-# files into.
-cfg_dir=/etc/nagios3/puppetconf.d
-
# 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/objects/commands.cfg
-#cfg_file=/etc/nagios3/objects/contacts.cfg
-#cfg_file=/etc/nagios3/objects/timeperiods.cfg
-#cfg_file=/etc/nagios3/objects/templates.cfg
-
-# Definitions for monitoring a Windows machine
-#cfg_file=/etc/nagios3/objects/windows.cfg
-
-# Definitions for monitoring a router/switch
-#cfg_file=/etc/nagios3/objects/switch.cfg
-
-# Definitions for monitoring a network printer
-#cfg_file=/etc/nagios3/objects/printer.cfg
-
+# Hint: Check the docs/wiki on how to monitor remote hosts with different
+# transport methods and plugins
-# 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:
+# Debian uses by default a configuration directory where icinga-common,
+# other packages and the local admin can dump or link configuration
+# files into.
+cfg_dir=/etc/icinga/objects/
-#cfg_dir=/etc/nagios3/servers
-#cfg_dir=/etc/nagios3/printers
-#cfg_dir=/etc/nagios3/switches
-#cfg_dir=/etc/nagios3/routers
+# Definitions for ido2db process checks
+#cfg_file=/etc/icinga/objects/ido2db_check_proc.cfg
+# Definitions for broker modules like idoutils.cfg
+cfg_dir=/etc/icinga/modules
# OBJECT CACHE FILE
# This option determines where object definitions are cached when
-# Nagios starts/restarts. The CGIs read object definitions from
+# Icinga starts/restarts. The CGIs read object definitions from
# this cache file (rather than looking at the object config files
# directly) in order to prevent inconsistencies that can occur
-# when the config files are modified after Nagios starts.
+# when the config files are modified after Icinga starts.
-object_cache_file=/var/cache/nagios3/objects.cache
+object_cache_file=/var/cache/icinga/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
+# If you run Icinga 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
+# file. You can then start Icinga 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
+# Using a precached object file can speed up the time needed to (re)start
+# the Icinga process if you've got a large and/or complex configuration.
+# Read the documentation section on optimizing Icinga to find our more
# about how this feature works.
-precached_object_file=/var/lib/nagios3/objects.precache
+precached_object_file=/var/cache/icinga/objects.precache
# defined as macros in this file and restrictive permissions (600)
# can be placed on this file.
-resource_file=/etc/nagios3/resource.cfg
+resource_file=/etc/icinga/resource.cfg
# 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 contents of the status file are deleted every time Nagios
+# The contents of the status file are deleted every time Icinga
# restarts.
-status_file=/var/cache/nagios3/status.dat
+status_file=/var/lib/icinga/status.dat
# STATUS FILE UPDATE INTERVAL
# This option determines the frequency (in seconds) that
-# Nagios will periodically dump program, host, and
+# Icinga will periodically dump program, host, and
# service status data.
+# Increase the value, if you don't require it that often.
+#status_update_interval=30
status_update_interval=10
-# NAGIOS USER
-# This determines the effective user that Nagios should run as.
+# ICINGA USER
+# This determines the effective user that Icinga should run as.
# You can either supply a username or a UID.
-nagios_user=nagios
+icinga_user=nagios
-# NAGIOS GROUP
-# This determines the effective group that Nagios should run as.
+# ICINGA GROUP
+# This determines the effective group that Icinga should run as.
# You can either supply a group name or a GID.
-nagios_group=nagios
+icinga_group=nagios
# EXTERNAL COMMAND OPTION
-# This option allows you to specify whether or not Nagios should check
+# This option allows you to specify whether or not Icinga should check
# for external commands (in the command file defined below). By default
-# Nagios will *not* check for external commands, just to be on the
+# Icinga 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.
# Values: 0 = disable commands, 1 = enable commands
# EXTERNAL COMMAND CHECK INTERVAL
-# This is the interval at which Nagios should check for external commands.
+# This is the interval at which Icinga 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
+# Icinga 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
+# scheduled intervals, Icinga will also check for external commands after
# event handlers are executed.
-# NOTE: Setting this value to -1 causes Nagios to check the external
+# NOTE: Setting this value to -1 causes Icinga to check the external
# command file as often as possible.
#command_check_interval=15s
# EXTERNAL COMMAND FILE
-# This is the file that Nagios checks for external command requests.
+# This is the file that Icinga checks for external command requests.
# It is also where the command CGI will write commands that are submitted
# by users, so it must be writeable by the user that the web server
# is running as (usually 'nobody'). Permissions should be set at the
# Debian Users: In case you didn't read README.Debian yet, _NOW_ is the
# time to do it.
-command_file=/var/lib/nagios3/rw/nagios.cmd
+command_file=/var/lib/icinga/rw/icinga.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.
+# the Icinga 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.
+# Increase the value, if you are using addons like check_mk supplying
+# more external commands (passive check results) than usual.
+#external_command_buffer_slots=32768
external_command_buffer_slots=4096
# LOCK FILE
-# This is the lockfile that Nagios will use to store its PID number
+# This is the lockfile that Icinga will use to store its PID number
# in when it is running in daemon mode.
-lock_file=/var/run/nagios3/nagios3.pid
+lock_file=/var/run/icinga/icinga.pid
# TEMP FILE
-# This is a temporary file that is used as scratch space when Nagios
+# This is a temporary file that is used as scratch space when Icinga
# updates the status log, cleans the comment file, etc. This file
-# is created, used, and deleted throughout the time that Nagios is
+# is created, used, and deleted throughout the time that Icinga is
# running.
-temp_file=/var/cache/nagios3/nagios.tmp
+temp_file=/var/cache/icinga/icinga.tmp
# TEMP PATH
-# This is path where Nagios can create temp files for service and
+# This is path where Icinga can create temp files for service and
# host check results, etc.
temp_path=/tmp
# EVENT BROKER MODULE(S)
-# This directive is used to specify an event broker module that should
-# by loaded by Nagios at startup. Use multiple directives if you want
+# ----> use the new *module definition* instead:
+# ----> http://docs.icinga.org/latest/en/objectdefinitions.html
+#
+# This directive can be used to specify an event broker module that should
+# by loaded by Icinga at startup. Use multiple directives if you want
# 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...
+# Do NOT overwrite modules while they are being used by Icinga or Icinga
+# will crash in a fiery display of SEGFAULT glory.
#
# 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
+# 1. Shutdown Icinga, replace the module file, restart Icinga
+# 2. Delete the original module file, move the new module file into place, restart Icinga
#
-# Example:
+#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+# WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING
+#!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+#
+# IDOUtils idomod.so should be enabled using the module definition,
+# i.e. using a package. First check that, and if not, you can
+# enable it here.
#
+# ATTENTION: DO NOT load the same module here AND as a module definition.
+# This can lead into problems with races on ressources.
+#
+# Example:
# broker_module=<modulepath> [moduleargs]
-#broker_module=/somewhere/module1.o
-#broker_module=/somewhere/module2.o arg1 arg2=3 debug=0
+# Enabling idoutils in icinga.cfg is not recommended. If you want to
+# enable idoutils in Debian install icinga-idoutils and copy
+# /usr/share/doc/icinga-idoutils/examples/idoutils.cfg-sample to
+# /etc/icinga/modules/idoutils.cfg.
+# Don't forget to also enable the daemon in /etc/default/icinga
+#broker_module=/usr/lib/icinga/idomod.so config_file=/etc/icinga/idomod.cfg
# LOG ROTATION METHOD
-# This is the log rotation method that Nagios should use to rotate
+# This is the log rotation method that Icinga should use to rotate
# the main log file. Values are as follows..
# n = None - don't rotate the log
# h = Hourly rotation (top of the hour)
# This is the directory where archived (rotated) log files should be
# placed (assuming you've chosen to do log rotation).
-log_archive_path=/var/log/nagios3/archives
+log_archive_path=/var/log/icinga/archives
+
+
+
+# LOGGING OPTIONS FOR DAEMON
+# If you want messages logged to the daemon log file (usually icinga.log).
+# Default option is 1 (yes), the other valid option is 0 (no)
+use_daemon_log=1
-# LOGGING OPTIONS
+
+# LOGGING OPTIONS FOR SYSLOG
# If you want messages logged to the syslog facility, as well as the
-# Nagios log file set this option to 1. If not, set it to 0.
+# Icinga log file set this option to 1. If not, set it to 0.
use_syslog=1
+# SYSLOG FACILITY
+# If you enabled use_syslog you can set icinga to use a local facility
+# instead of the default.To enable set this option to 1, if not, set it to 0.
+
+use_syslog_local_facility=0
+
+
+
+# SYSLOG LOCAL FACILITY
+# If you specified the use_syslog_local_facility you can chose which
+# local facility to use. Valid values are from 0 to 7
+
+syslog_local_facility=5
+
+
+
# NOTIFICATION LOGGING OPTION
# If you don't want notifications to be logged, set this value to 0.
# If notifications should be logged, set the value to 1.
# INITIAL STATES LOGGING OPTION
-# If you want Nagios to log all initial host and service states to
+# If you want Icinga to log all initial host and service states to
# the main log file (the first time the service or host is checked)
# you can enable this option by setting this value to 1. If you
# are not using an external application that does long term state
+# CURRENT STATES LOGGING OPTION
+# If you don't want Icinga 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
+# If you don't want Icinga to log external commands, set this value
# to 0. If external commands should be logged, set this value to 1.
# Note: This option does not include logging of passive service
# checks - see the option below for controlling whether or not
# PASSIVE CHECKS LOGGING OPTION
-# If you don't want Nagios to log passive host and service checks, set
+# If you don't want Icinga to log passive host and service checks, set
# this value to 0. If passive checks should be logged, set
# this value to 1.
+# LONG PLUGIN OUTPUT LOGGING OPTION
+# If you want Icinga to log the complete text of the plugin output
+# to the log instead of only the first line then set this value to 1.
+# Default value is 0.
+
+log_long_plugin_output=0
+
+
+
# GLOBAL HOST AND SERVICE EVENT HANDLERS
# These options allow you to specify a host and service event handler
# command that is to be run for every host or service state change.
# SERVICE INTER-CHECK DELAY METHOD
-# This is the method that Nagios should use when initially
+# This is the method that Icinga should use when initially
# "spreading out" service checks when it starts monitoring. The
# default is to use smart delay calculation, which will try to
# space all service checks out evenly to minimize CPU load.
# Interleaving the service checks allows for a more even
# distribution of service checks and reduced load on remote
# hosts. Setting this value to 1 is equivalent to how versions
-# of Nagios previous to 0.0.5 did service checks. Set this
+# of Icinga previous to 0.0.5 did service checks. Set this
# value to s (smart) for automatic calculation of the interleave
# factor unless you have a specific reason to change it.
# s = Use "smart" interleave factor calculation
# HOST INTER-CHECK DELAY METHOD
-# This is the method that Nagios should use when initially
+# This is the method that Icinga should use when initially
# "spreading out" host checks when it starts monitoring. The
# default is to use smart delay calculation, which will try to
# space all host checks out evenly to minimize CPU load.
# HOST AND SERVICE CHECK REAPER FREQUENCY
-# This is the frequency (in seconds!) that Nagios will process
+# This is the frequency (in seconds!) that Icinga will process
# the results of host and service checks.
+# Lower this value in larger environments to allow faster
+# check result processing (requires more cpu power).
+#check_result_reaper_frequency=1
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
+# returning control back to Icinga 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
+# This is directory where Icinga 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
+# Note: Make sure that only one instance of Icinga has access
# to this directory!
-check_result_path=/var/lib/nagios3/spool/checkresults
+check_result_path=/var/lib/icinga/spool/checkresults
# 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
+# states being used by Icinga, while a lower value may result in a
# performance hit for host checks. Use a value of 0 to disable host
# check caching.
# ENABLE PREDICTIVE HOST DEPENDENCY CHECKS
-# This option determines whether or not Nagios will attempt to execute
+# This option determines whether or not Icinga 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.
# ENABLE PREDICTIVE SERVICE DEPENDENCY CHECKS
-# This option determines whether or not Nagios will attempt to execute
+# This option determines whether or not Icinga 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.
# SOFT STATE DEPENDENCIES
-# This option determines whether or not Nagios will use soft state
+# This option determines whether or not Icinga will use soft state
# information when checking host and service dependencies. Normally
-# Nagios will only use the latest hard host or service state when
+# Icinga 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:
# TIME CHANGE ADJUSTMENT THRESHOLDS
-# These options determine when Nagios will react to detected changes
+# These options determine when Icinga 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
+# This option determines whether or not Icinga will attempt to
# automatically reschedule active host and service checks to
# "smooth" them out over time. This can help balance the load on
# the monitoring server.
# AUTO-RESCHEDULING INTERVAL
-# This option determines how often (in seconds) Nagios will
+# This option determines how often (in seconds) Icinga will
# attempt to automatically reschedule checks. This option only
# has an effect if the auto_reschedule_checks option is enabled.
# Default is 30 seconds.
# AUTO-RESCHEDULING WINDOW
# This option determines the "window" of time (in seconds) that
-# Nagios will look at when automatically rescheduling checks.
+# Icinga will look at when automatically rescheduling checks.
# Only host and service checks that occur in the next X seconds
# (determined by this variable) will be rescheduled. This option
# only has an effect if the auto_reschedule_checks option is
# TIMEOUT VALUES
-# These options control how much time Nagios will allow various
+# These options control how much time Icinga will allow various
# types of commands to execute before killing them off. Options
# are available for controlling maximum time allotted for
# service checks, host checks, event handlers, notifications, the
# ocsp command, and performance data commands. All values are in
# seconds.
+# Increase the timeout values in case you are experiencing a lot
+# of check timeouts. Addons like e.g. check_mk will perform
+# one combined active servicecheck which could take longer than
+# the default of 60sec.
+#service_check_timeout=120
service_check_timeout=60
host_check_timeout=30
event_handler_timeout=30
# RETAIN STATE INFORMATION
-# This setting determines whether or not Nagios will save state
+# This setting determines whether or not Icinga will save state
# information for services and hosts before it shuts down. Upon
-# startup Nagios will reload all saved service and host state
+# startup Icinga will reload all saved service and host state
# information before starting to monitor. This is useful for
# maintaining long-term data on state statistics, etc, but will
-# slow Nagios down a bit when it (re)starts. Since its only
+# slow Icinga down a bit when it (re)starts. Since its only
# a one-time penalty, I think its well worth the additional
# startup delay.
# STATE RETENTION FILE
-# This is the file that Nagios should use to store host and
+# This is the file that Icinga should use to store host and
# 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
+# starting to monitor the network when Icinga is restarted.
+# This file is used only if the retain_state_information
# variable is set to 1.
-state_retention_file=/var/lib/nagios3/retention.dat
+state_retention_file=/var/cache/icinga/retention.dat
+
+
+
+# SYNC FILE
+# This is an advanced facility to pass a subset of retention
+# information into Icinga on a running system. This is similar
+# to the state retention file with the following difference:
+#
+# - if the last_check value is less than the current last_check,
+# then the state information is ignored (this must be specified
+# immediately after the object identifiers)
+#
+# - downtimes and comments are not identified by an id number, but
+# by other "similar characteristics". This is required to work in
+# a distributed Nagios environment
+# * downtimes: hostname, servicename (if appropriate), author,
+# comment, start_time, end_time, fixed, duration
+# * comments: hostname, servicename, author, comment
+#
+# If this variable is set, then on Icinga startup, the sync file
+# will be read after the retention file has been processed. If the
+# file is read successfully, it will be removed.
+# If the file does not exist, no error will appear.
+# There is also an API that will force a read of the sync file.
+
+#sync_retention_file=/var/cache/icinga/sync.dat
# RETENTION DATA UPDATE INTERVAL
-# This setting determines how often (in minutes) that Nagios
+# This setting determines how often (in minutes) that Icinga
# will automatically save retention data during normal operation.
-# If you set this value to 0, Nagios will not save retention
+# If you set this value to 0, Icinga will not save retention
# data at regular interval, but it will still save retention
# data before shutting down or restarting. If you have disabled
# state retention, this option has no effect.
# USE RETAINED PROGRAM STATE
-# This setting determines whether or not Nagios will set
+# This setting determines whether or not Icinga will set
# program status variables based on the values saved in the
# retention file. If you want to use retained program status
# information, set this value to 1. If not, set this value
use_retained_program_state=1
+# DUMP RETAINED HOST SERVICE STATES TO NEB
+# This setting determines wether or not Icinga will dump host
+# and service states based on the values saved in the retention
+# file to the neb modules. If you don't want that, use at your
+# own risk and disable it
+
+dump_retained_host_service_states_to_neb=1
+
+
# USE RETAINED SCHEDULING INFO
-# This setting determines whether or not Nagios will retain
+# This setting determines whether or not Icinga will retain
# the scheduling info (next check time) for hosts and services
# based on the values saved in the retention file. If you
# If you want to use retained scheduling info, set this
# 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
+# service attributes that should *not* be retained by Icinga during
# program restarts.
#
# The values of the masks are bitwise ANDs of values specified
# SERVICE CHECK EXECUTION OPTION
-# This determines whether or not Nagios will actively execute
+# This determines whether or not Icinga will actively execute
# service checks when it initially starts. If this option is
-# disabled, checks are not actively made, but Nagios can still
+# disabled, checks are not actively made, but Icinga can still
# receive and process passive check results that come in. Unless
# you're implementing redundant hosts or have a special need for
# disabling the execution of service checks, leave this enabled!
# PASSIVE SERVICE CHECK ACCEPTANCE OPTION
-# This determines whether or not Nagios will accept passive
+# This determines whether or not Icinga will accept passive
# service checks results when it initially (re)starts.
# Values: 1 = accept passive checks, 0 = reject passive checks
# HOST CHECK EXECUTION OPTION
-# This determines whether or not Nagios will actively execute
+# This determines whether or not Icinga will actively execute
# host checks when it initially starts. If this option is
-# disabled, checks are not actively made, but Nagios can still
+# disabled, checks are not actively made, but Icinga can still
# receive and process passive check results that come in. Unless
# you're implementing redundant hosts or have a special need for
# disabling the execution of host checks, leave this enabled!
# PASSIVE HOST CHECK ACCEPTANCE OPTION
-# This determines whether or not Nagios will accept passive
+# This determines whether or not Icinga will accept passive
# host checks results when it initially (re)starts.
# Values: 1 = accept passive checks, 0 = reject passive checks
# NOTIFICATIONS OPTION
-# This determines whether or not Nagios will sent out any host or
+# This determines whether or not Icinga will sent out any host or
# service notifications when it is initially (re)started.
# Values: 1 = enable notifications, 0 = disable notifications
# EVENT HANDLER USE OPTION
-# This determines whether or not Nagios will run any host or
+# This determines whether or not Icinga will run any host or
# service event handlers when it is initially (re)started. Unless
# you're implementing redundant hosts, leave this option enabled.
# Values: 1 = enable event handlers, 0 = disable event handlers
# PROCESS PERFORMANCE DATA OPTION
-# This determines whether or not Nagios will process performance
+# This determines whether or not Icinga will process performance
# data returned from service and host checks. If this option is
# enabled, host performance data will be processed using the
# host_perfdata_command (defined below) and service performance
# HOST AND SERVICE PERFORMANCE DATA PROCESSING COMMANDS
# These commands are run after every host and service check is
# performed. These commands are executed only if the
-# enable_performance_data option (above) is set to 1. The command
-# argument is the short name of a command definition that you
+# process_performance_data 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 performance data.
# HOST AND SERVICE PERFORMANCE DATA FILES
# These files are used to store host and service performance data.
# Performance data is only written to these files if the
-# enable_performance_data option (above) is set to 1.
+# process_performance_data option (above) is set to 1.
#host_perfdata_file=/tmp/host-perfdata
#service_perfdata_file=/tmp/service-perfdata
#service_perfdata_file_processing_command=process-service-perfdata-file
+# 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
+
+
+
+# ALLOW EMPTY HOSTGROUP ASSIGMENT FOR SERVICES
+# This boolean option determines whether services assigned to empty
+# host groups (host groups with no host members) will cause Icinga to
+# exit with error on start up (or during a configuration check) or not.
+# It's useful to be able to assign services to empty hostgroups when
+# configuration files or pre-cached object files are distributed to
+# various pollers, or when the process of generating Icinga config is
+# automated, or when a set of services is slowly being phased out but
+# should be kept around.
+# The default behavior if the option is not present in the main
+# configuration file is for Icinga to exit with error if services are
+# associated with host groups that have no hosts associated with them.
+
+#allow_empty_hostgroup_assignment=0
+
+
# OBSESS OVER SERVICE CHECKS OPTION
-# This determines whether or not Nagios will obsess over service
+# This determines whether or not Icinga will obsess over service
# checks and run the ocsp_command defined below. Unless you're
# planning on implementing distributed monitoring, do not enable
# this option. Read the HTML docs for more information on
# 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
+# processed by Icinga. This command is executed only if the
# 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
# OBSESS OVER HOST CHECKS OPTION
-# This determines whether or not Nagios will obsess over host
+# This determines whether or not Icinga 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
# 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
+# processed by Icinga. 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
# TRANSLATE PASSIVE HOST CHECKS OPTION
-# This determines whether or not Nagios will translate
+# This determines whether or not Icinga will translate
# DOWN/UNREACHABLE passive host check results into their proper
-# state for this instance of Nagios. This option is useful
+# state for this instance of Icinga. This option is useful
# if you have distributed or failover monitoring setup. In
-# these cases your other Nagios servers probably have a different
+# these cases your other Icinga 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
+# this Icinga instance. Enabling this option will tell Icinga
# 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)
# PASSIVE HOST CHECKS ARE SOFT OPTION
-# This determines whether or not Nagios will treat passive host
+# This determines whether or not Icinga 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.
# ORPHANED HOST/SERVICE CHECK OPTIONS
-# These options determine whether or not Nagios will periodically
+# These options determine whether or not Icinga 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
+# SERVICE CHECK TIMEOUT STATE
+# This setting determines the state Icinga will report when a
+# service check times out meaning it does not respond within
+# service_check_timeout seconds. The default is set to Unknown
+# and not Critical.
+# Valid settings are:
+# c - Critical
+# u - Unknown (default)
+# w - Warning
+# o - OK
+
+service_check_timeout_state=u
+
+
+
# SERVICE FRESHNESS CHECK OPTION
-# This option determines whether or not Nagios will periodically
+# This option determines whether or not Icinga will periodically
# check the "freshness" of service results. Enabling this option
# is useful for ensuring passive checks are received in a timely
# manner.
# SERVICE FRESHNESS CHECK INTERVAL
-# This setting determines how often (in seconds) Nagios will
+# This setting determines how often (in seconds) Icinga will
# check the "freshness" of service check results. If you have
# disabled service freshness checking, this option has no effect.
# HOST FRESHNESS CHECK OPTION
-# This option determines whether or not Nagios will periodically
+# This option determines whether or not Icinga will periodically
# check the "freshness" of host results. Enabling this option
# is useful for ensuring passive checks are received in a timely
# manner.
# HOST FRESHNESS CHECK INTERVAL
-# This setting determines how often (in seconds) Nagios will
+# This setting determines how often (in seconds) Icinga will
# check the "freshness" of host check results. If you have
# disabled host freshness checking, this option has no effect.
# ADDITIONAL FRESHNESS THRESHOLD LATENCY
-# This setting determines the number of seconds that Nagios
+# This setting determines the number of seconds that Icinga
# will add to any host and service freshness thresholds that
# it calculates (those not explicitly specified by the user).
# FLAP DETECTION OPTION
-# This option determines whether or not Nagios will try
+# This option determines whether or not Icinga will try
# and detect hosts and services that are "flapping".
# Flapping occurs when a host or service changes between
-# states too frequently. When Nagios detects that a
+# states too frequently. When Icinga detects that a
# host or service is flapping, it will temporarily suppress
# notifications for that host/service until it stops
# flapping. Flap detection is very experimental, so read
# TIMEZONE OFFSET
# This option is used to override the default timezone that this
-# instance of Nagios runs in. If not specified, Nagios will use
+# instance of Icinga runs in. If not specified, Icinga 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/">
+# <Directory "/usr/local/icinga/sbin/">
# SetEnv TZ "Australia/Brisbane"
# ...
# </Directory>
# 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.
+# Icinga with embedded Perl support, this option has no effect.
-p1_file=/usr/lib/nagios3/p1.pl
+p1_file=/usr/lib/icinga/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
+# will be enabled during runtime. This option has no effect if Icinga
# has not been compiled with support for embedded Perl.
+# This option is intentionally disabled by default, because embedded
+# perl can cause memory leaks and make Icinga unstable if not properly
+# used.
+# Only enable this setting when you really know what you are doing!
# 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
+# This option determines whether or not Icinga 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
+# EVENT HANDLERS FOR STALKED HOSTS/SERVICES
+# Allow running event handlers for stalked hosts/services in order
+# to forward to external systems.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_event_handlers_for_hosts=0
+stalking_event_handlers_for_services=0
+
+
+
+# NOTIFICATIONS FOR STALKED HOSTS/SERVICES
+# Allow notifications for stalked hosts/services globally
+# for all contacts in order to notify about a stalking
+# alert.
+# Values: 0 = disabled (default), 1 = enabled
+
+stalking_notifications_for_hosts=0
+stalking_notifications_for_services=0
+
+
+
# ILLEGAL OBJECT NAME CHARACTERS
# This option allows you to specify illegal characters that cannot
# be used in host names, service descriptions, or names of other
# 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
+# Icinga never uses these values itself, but you can access them by
# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification
# commands.
# DAEMON CORE DUMP OPTION
-# This option determines whether or not Nagios is allowed to create
+# This option determines whether or not Icinga 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. Enabling this option doesn't guarantee that
# 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.
+# This option determines whether or not Icinga will take some shortcuts
+# which can save on memory and CPU usage in large Icinga installations.
# Read the documentation for more information on the benefits/tradeoffs
# of enabling this option.
# Values: 1 - Enabled tweaks
# ENABLE ENVIRONMENT MACROS
-# This option determines whether or not Nagios will make all standard
+# This option determines whether or not Icinga 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
+# 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
+# Keep in mind that various addons/plugins will require this setting
+# to be enabled (e.g. check_oracle_health) for special usage.
+# Values: 1 - Enable environment variable macros
+# 0 - Disable environment variable macros (default)
enable_environment_macros=1
# CHILD PROCESS MEMORY OPTION
-# This option determines whether or not Nagios will free memory in
+# This option determines whether or not Icinga 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.
# CHILD PROCESS FORKING BEHAVIOR
-# This option determines how Nagios will fork child processes
+# This option determines how Icinga 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
# Value: 1 - Child processes fork() twice
# 0 - Child processes fork() just once
-child_processes_fork_twice=0
+#child_processes_fork_twice=1
# 1 = More detailed
# 2 = Very detailed
-debug_verbosity=1
+debug_verbosity=2
# DEBUG FILE
-# This option determines where Nagios should write debugging information.
+# This option determines where Icinga should write debugging information.
-debug_file=/var/lib/nagios3/nagios.debug
+debug_file=/var/log/icinga/icinga.debug
# 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.
+# get out of control when debugging Icinga.
+
+# 100M
+max_debug_file_size=100000000
+
-max_debug_file_size=1000000
+# EVENT PROFILING
+# This option enables or disables event profiling for stats of event counts
+# and time taken for events. Option can't be used on Solaris with gcc3.
+# Values: 0 - disabled
+# 1 - enabled
+event_profiling_enabled=0
projects / mirror / dsa-nagios.git / blobdiff