From 79f8f9c199a30524b5636c00e86fc8f179caf6f2 Mon Sep 17 00:00:00 2001 From: Waldemar Brodkorb Date: Sat, 3 Dec 2011 12:21:37 +0100 Subject: add icinga core --- package/icinga/Makefile | 29 + package/icinga/files/icinga.init | 35 + package/icinga/files/icinga.postinst | 6 + package/icinga/patches/patch-configure | 20 + package/icinga/patches/patch-configure.orig | 11 + package/icinga/src/etc/icinga/cgi.cfg | 653 +++++++++ package/icinga/src/etc/icinga/cgiauth.cfg | 8 + package/icinga/src/etc/icinga/icinga.cfg | 1484 ++++++++++++++++++++ package/icinga/src/etc/icinga/mrtg.cfg | 180 +++ package/icinga/src/etc/icinga/objects/commands.cfg | 250 ++++ package/icinga/src/etc/icinga/objects/contacts.cfg | 53 + .../icinga/src/etc/icinga/objects/localhost.cfg | 167 +++ .../src/etc/icinga/objects/notifications.cfg | 132 ++ package/icinga/src/etc/icinga/objects/printer.cfg | 83 ++ package/icinga/src/etc/icinga/objects/switch.cfg | 111 ++ .../icinga/src/etc/icinga/objects/templates.cfg | 188 +++ .../icinga/src/etc/icinga/objects/timeperiods.cfg | 92 ++ package/icinga/src/etc/icinga/objects/windows.cfg | 143 ++ package/icinga/src/etc/icinga/resource.cfg | 32 + 19 files changed, 3677 insertions(+) create mode 100644 package/icinga/Makefile create mode 100644 package/icinga/files/icinga.init create mode 100644 package/icinga/files/icinga.postinst create mode 100644 package/icinga/patches/patch-configure create mode 100644 package/icinga/patches/patch-configure.orig create mode 100644 package/icinga/src/etc/icinga/cgi.cfg create mode 100644 package/icinga/src/etc/icinga/cgiauth.cfg create mode 100644 package/icinga/src/etc/icinga/icinga.cfg create mode 100644 package/icinga/src/etc/icinga/mrtg.cfg create mode 100644 package/icinga/src/etc/icinga/objects/commands.cfg create mode 100644 package/icinga/src/etc/icinga/objects/contacts.cfg create mode 100644 package/icinga/src/etc/icinga/objects/localhost.cfg create mode 100644 package/icinga/src/etc/icinga/objects/notifications.cfg create mode 100644 package/icinga/src/etc/icinga/objects/printer.cfg create mode 100644 package/icinga/src/etc/icinga/objects/switch.cfg create mode 100644 package/icinga/src/etc/icinga/objects/templates.cfg create mode 100644 package/icinga/src/etc/icinga/objects/timeperiods.cfg create mode 100644 package/icinga/src/etc/icinga/objects/windows.cfg create mode 100644 package/icinga/src/etc/icinga/resource.cfg diff --git a/package/icinga/Makefile b/package/icinga/Makefile new file mode 100644 index 000000000..96d439e45 --- /dev/null +++ b/package/icinga/Makefile @@ -0,0 +1,29 @@ +# This file is part of the OpenADK project. OpenADK is copyrighted +# material, please see the LICENCE file in the top-level directory. + +include $(TOPDIR)/rules.mk + +PKG_NAME:= icinga +PKG_VERSION:= 1.6.1 +PKG_RELEASE:= 1 +PKG_MD5SUM:= 7b32e589235dd74ea020f12cbc90ec31 +PKG_DESCR:= network monitoring +PKG_SECTION:= net +PKG_DEPENDS:= mini-sendmail +PKG_URL:= http://www.icinga.org/ +PKG_SITES:= ${MASTER_SITE_SOURCEFORGE:=icinga/1.6.1/} + +include $(TOPDIR)/mk/package.mk + +$(eval $(call PKG_template,ICINGA,icinga,$(PKG_VERSION)-${PKG_RELEASE},${PKG_DEPENDS},${PKG_DESCR},${PKG_SECTION})) + +CONFIGURE_ARGS+= --sysconfdir=/etc/icinga + +icinga-install: + $(INSTALL_DIR) $(IDIR_ICINGA)/etc + $(CP) ./src/etc/icinga $(IDIR_ICINGA)/etc + $(INSTALL_DIR) $(IDIR_ICINGA)/usr/bin + $(INSTALL_BIN) $(WRKINST)/usr/bin/icinga \ + $(IDIR_ICINGA)/usr/bin + +include ${TOPDIR}/mk/pkg-bottom.mk diff --git a/package/icinga/files/icinga.init b/package/icinga/files/icinga.init new file mode 100644 index 000000000..239175ff2 --- /dev/null +++ b/package/icinga/files/icinga.init @@ -0,0 +1,35 @@ +#!/bin/sh +#PKG icinga +#INIT 80 +. /etc/rc.conf + +case $1 in +autostop) ;; +autostart) + test x"${icinga:-NO}" = x"NO" && exit 0 + exec sh $0 start + ;; +start) + [ -d /var/run/icinga ] || mkdir -p /var/run/icinga + [ -d /var/rw ] || mkdir -p /var/rw + [ -d /var/spool/checkresults ] || mkdir -p /var/spool/checkresults + touch /var/log/icinga.log + chown icinga:icinga /var/log/icinga.log + chown icinga:icinga /var/run/icinga + chown icinga:icinga /var/spool/checkresults + chown icinga:icinga /var/rw + icinga -d /etc/icinga/icinga.cfg + ;; +stop) + kill $(pgrep -f /usr/bin/icinga) + ;; +restart) + sh $0 stop + sh $0 start + ;; +*) + echo "Usage: $0 {start | stop | restart}" + exit 1 + ;; +esac +exit $? diff --git a/package/icinga/files/icinga.postinst b/package/icinga/files/icinga.postinst new file mode 100644 index 000000000..c0df0e7ea --- /dev/null +++ b/package/icinga/files/icinga.postinst @@ -0,0 +1,6 @@ +#!/bin/sh +. $IPKG_INSTROOT/etc/functions.sh +add_rcconf icinga icinga NO +gid=$(get_next_gid) +add_group icinga $gid +add_user icinga $(get_next_uid) $gid /etc/icinga diff --git a/package/icinga/patches/patch-configure b/package/icinga/patches/patch-configure new file mode 100644 index 000000000..170349f85 --- /dev/null +++ b/package/icinga/patches/patch-configure @@ -0,0 +1,20 @@ +--- icinga-1.6.1.orig/configure 2011-12-02 14:53:23.000000000 +0100 ++++ icinga-1.6.1/configure 2011-12-02 23:44:13.000000000 +0100 +@@ -5154,7 +5154,7 @@ cat >>confdefs.h <<_ACEOF + #define DEFAULT_NAGIOS_GROUP "$icinga_grp" + _ACEOF + +-INSTALL_OPTS="-o $icinga_user -g $icinga_grp" ++#INSTALL_OPTS="-o $icinga_user -g $icinga_grp" + + + +@@ -5232,7 +5232,7 @@ fi + + + +-INSTALL_OPTS_WEB="-o $web_user -g $web_group" ++#INSTALL_OPTS_WEB="-o $web_user -g $web_group" + + + diff --git a/package/icinga/patches/patch-configure.orig b/package/icinga/patches/patch-configure.orig new file mode 100644 index 000000000..c27f5b420 --- /dev/null +++ b/package/icinga/patches/patch-configure.orig @@ -0,0 +1,11 @@ +--- icinga-1.6.1.orig/configure 2011-12-02 14:53:23.000000000 +0100 ++++ icinga-1.6.1/configure 2011-12-02 23:41:56.000000000 +0100 +@@ -5154,7 +5154,7 @@ cat >>confdefs.h <<_ACEOF + #define DEFAULT_NAGIOS_GROUP "$icinga_grp" + _ACEOF + +-INSTALL_OPTS="-o $icinga_user -g $icinga_grp" ++#INSTALL_OPTS="-o $icinga_user -g $icinga_grp" + + + diff --git a/package/icinga/src/etc/icinga/cgi.cfg b/package/icinga/src/etc/icinga/cgi.cfg new file mode 100644 index 000000000..35057eb75 --- /dev/null +++ b/package/icinga/src/etc/icinga/cgi.cfg @@ -0,0 +1,653 @@ +################################################################# +# +# CGI.CFG - Sample CGI Configuration File for Icinga +# +################################################################# + + +# MAIN CONFIGURATION FILE +# This tells the CGIs where to find your main configuration file. +# The CGIs will read the main and host config files for any other +# data they might need. + +main_config_file=/etc/icinga/icinga.cfg + + +# ATTRIBUTE BASED AUTHORIZATION FILE +# This option will include a file defining authroization based on +# attributes. + +#authorization_config_file=/etc/icinga/cgiauth.cfg + + +# PHYSICAL HTML PATH +# This is the path where the HTML files for Icinga reside. This +# value is used to locate the logo images needed by the statusmap +# and statuswrl CGIs. + +physical_html_path=/usr/share + + + +# URL HTML PATH +# This is the path portion of the URL that corresponds to the +# physical location of the Icinga HTML files (as defined above). +# This value is used by the CGIs to locate the online documentation +# and graphics. If you access the Icinga pages with an URL like +# http://www.myhost.com/icinga, this value should be '/icinga' +# (without the quotes). + +url_html_path=/icinga + + + +# URL STYLESHEETS PATH +# This option allows to define an url stylesheet path other than the +# default ($url_html_path/stylesheets). This will be useful when +# adding custom stylesheets in another location. +# If not set, the default location will be used. + +url_stylesheets_path=/icinga/stylesheets + + + +# HTTP CHARSET +# This defines charset that is sent with HTTP headers. + +http_charset=utf-8 + + + +# CONTEXT-SENSITIVE HELP +# This option determines whether or not a context-sensitive +# help icon will be displayed for most of the CGIs. +# Values: 0 = disables context-sensitive help +# 1 = enables context-sensitive help + +show_context_help=0 + + + +# HIGHLIGHT TABLE ROWS +# This option allows you to define if table rows in status.cgi +# will be highlighted or not. +# Values: 0 = disables row highlighting +# 1 = enables row highlighting + +highlight_table_rows=1 + + + +# 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 + + +# Logging + +# USE LOGGING +# If you want to log information from cgi's (e.g. all submitted commands) +# then set this option to 1, default is 0 (off). +# WARNING: +# This log is highly experimental and changes may occure without notice. Use at your own risk!! + +use_logging=0 + + +# CGI LOG FILE +# This is the cgi log file for information about what users are doing. +# At the moment only submitted commands from cmd.cgi will be logged. + +cgi_log_file=/usr/share/log/icinga-cgi.log + + +# CGI LOG ROTATION METHOD +# This is the log rotation method that should be used to rotate +# the cgi log file. Values are as follows.. +# n = None - don't rotate the log +# h = Hourly rotation (top of the hour) +# d = Daily rotation (midnight every day) +# w = Weekly rotation (midnight on Saturday evening) +# m = Monthly rotation (midnight last day of month) + +cgi_log_rotation_method=d + + +# CGI LOG ARCHIVE PATH +# This is the directory where archived (rotated) cgi log files should be +# placed (assuming you've chosen to do log rotation). + +cgi_log_archive_path=/usr/share/log + + +# FORCE COMMENT +# This option forces the users of to comment every action they perform. +# The comments get logged into cgi log file. This option only has effect +# if logging is switched on. See option "use_logging" +# Default is 0 (off), to activate it set it to 1 (on). + +enforce_comments_on_actions=0 + + +# FIRST DAY OF WEEK +# Here you can set if your week starts on sunday or monday. +# Default is 0 (Sunday), set it to 1 if your week start monday. + +first_day_of_week=0 + + +# AUTHENTICATION USAGE +# This option controls whether or not the CGIs will use any +# authentication when displaying host and service information, as +# well as committing commands to Icinga for processing. +# +# Read the HTML documentation to learn how the authorization works! +# +# NOTE: It is a really *bad* idea to disable authorization, unless +# you plan on removing the command CGI (cmd.cgi)! Failure to do +# so will leave you wide open to kiddies messing with Icinga and +# possibly hitting you with a denial of service attack by filling up +# your drive by continuously writing to your command file! +# +# Setting this value to 0 will cause the CGIs to *not* use +# authentication (bad idea), while any other value will make them +# use the authentication functions (the default). + +use_authentication=1 + + + + +# x509 CERT AUTHENTICATION +# When enabled, this option allows you to use x509 cert (SSL) +# authentication in the CGIs. This is an advanced option and should +# not be enabled unless you know what you're doing. + +use_ssl_authentication=0 + + + + +# DEFAULT USER +# Setting this variable will define a default user name that can +# access pages without authentication. This allows people within a +# secure domain (i.e., behind a firewall) to see the current status +# without authenticating. You may want to use this to avoid basic +# authentication if you are not using a secure server since basic +# authentication transmits passwords in the clear. +# +# Important: Do not define a default username unless you are +# running a secure web server and are sure that everyone who has +# access to the CGIs has been authenticated in some manner! If you +# define this variable, anyone who has not authenticated to the web +# server will inherit all rights you assign to this user! + +#default_user_name=guest + + + +# SYSTEM/PROCESS INFORMATION ACCESS +# This option is a comma-delimited list of all usernames that +# have access to viewing the Icinga process information as +# provided by the Extended Information CGI (extinfo.cgi). By +# default, *no one* has access to this unless you choose to +# not use authorization. You may use an asterisk (*) to +# authorize any user who has authenticated to the web server. +# Alternatively you can specify contactgroups too, starting +# with Icinga 1.5.0 + +authorized_for_system_information=icingaadmin +#authorized_contactgroup_for_system_information= + + +# CONFIGURATION INFORMATION ACCESS +# This option is a comma-delimited list of all usernames that +# can view ALL configuration information (hosts, commands, etc). +# By default, users can only view configuration information +# for the hosts and services they are contacts for. You may use +# an asterisk (*) to authorize any user who has authenticated +# to the web server. +# Alternatively you can specify contactgroups too, starting +# with Icinga 1.5.0 + +authorized_for_configuration_information=icingaadmin +#authorized_contactgroup_for_configuration_information= + + +# RAW COMMANDLINE CONFIGURATION INFORMATION ACCESS +# This option is a comma-delimited list of all usernames that +# can view a command in config command expander as icinga would +# execute it. To resolve all MACROS it is necessary to allow +# read access to the web server for resource.cfg . +# CAUTION: $USERXX$ vars and custom vars can contain sensitive +# data. +# Alternatively you can specify contactgroups too. + +authorized_for_full_command_resolution=icingaadmin +#authorized_contactgroup_for_full_command_resolution= + + +# SYSTEM/PROCESS COMMAND ACCESS +# This option is a comma-delimited list of all usernames that +# can issue shutdown and restart commands to Icinga via the +# command CGI (cmd.cgi). Users in this list can also change +# the program mode to active or standby. By default, *no one* +# has access to this unless you choose to not use authorization. +# You may use an asterisk (*) to authorize any user who has +# authenticated to the web server. +# Alternatively you can specify contactgroups too, starting +# with Icinga 1.5.0 + +authorized_for_system_commands=icingaadmin +#authorized_contactgroup_for_system_commands= + + +# GLOBAL HOST/SERVICE VIEW ACCESS +# These two options are comma-delimited lists of all usernames that +# can view information for all hosts and services that are being +# monitored. By default, users can only view information +# for hosts or services that they are contacts for (unless you +# you choose to not use authorization). You may use an asterisk (*) +# to authorize any user who has authenticated to the web server. +# Alternatively you can specify contactgroups too, starting +# with Icinga 1.5.0 + + +authorized_for_all_services=icingaadmin +authorized_for_all_hosts=icingaadmin +#authorized_contactgroup_for_all_services= +#authorized_contactgroup_for_all_hosts= + + +# GLOBAL HOST/SERVICE COMMAND ACCESS +# These two options are comma-delimited lists of all usernames that +# can issue host or service related commands via the command +# CGI (cmd.cgi) for all hosts and services that are being monitored. +# By default, users can only issue commands for hosts or services +# that they are contacts for (unless you you choose to not use +# authorization). You may use an asterisk (*) to authorize any +# user who has authenticated to the web server. +# Alternatively you can specify contactgroups too, starting +# with Icinga 1.5.0 + +authorized_for_all_service_commands=icingaadmin +authorized_for_all_host_commands=icingaadmin +#authorized_contactgroup_for_all_service_commands= +#authorized_contactgroup_for_all_host_commands= + + +# READ-ONLY USERS +# A comma-delimited list of usernames that have read-only rights in +# the CGIs. This will block any service or host commands normally shown +# on the extinfo CGI pages. It will also block comments from being shown +# to read-only users. +# Alternatively you can specify contactgroups too, starting +# with Icinga 1.5.0 + +#authorized_for_read_only=user1,user2 +#authorized_contactgroup_for_read_only= + + +# SHOW ALL SERVICES THE HOST IS AUTHORIZED FOR +# By default, a user can see all services on a host, if the user is +# authorized as contact for the host only. By disabling this option, +# the user must be an authorized contact for the service too in order +# to view it. +# Values: 0 - disabled, user must be authorized for services too +# 1 - enabled, user can view all services on authorized host + +show_all_services_host_is_authorized_for=1 + + +# SHOW PARTIAL HOSTGROUPS +# By default, a user only sees a hostgroup and the hosts within it if +# they are an authorized contact for all of the hosts of the group. By +# enabling this option hostgroups will show a partial listing of hosts +# the user is an authorized contact for in the hostgroups. +# Values: 0 - disabled, user only sees full hostgroups (default) +# 1 - enabled, user sees partial hostgroups + +show_partial_hostgroups=0 + + +# STATUSMAP BACKGROUND IMAGE +# This option allows you to specify an image to be used as a +# background in the statusmap CGI. It is assumed that the image +# resides in the HTML images path (i.e. /usr/local/icinga/share/images). +# This path is automatically determined by appending "/images" +# to the path specified by the 'physical_html_path' directive. +# Note: The image file may be in GIF, PNG, JPEG, or GD2 format. +# However, I recommend that you convert your image to GD2 format +# (uncompressed), as this will cause less CPU load when the CGI +# generates the image. + +#statusmap_background_image=smbackground.gd2 + + + + +# STATUSMAP TRANSPARENCY INDEX COLOR +# These options set the r,g,b values of the background color used the statusmap CGI, +# so normal browsers that can't show real png transparency set the desired color as +# a background color instead (to make it look pretty). +# Defaults to white: (R,G,B) = (255,255,255). + +#color_transparency_index_r=255 +#color_transparency_index_g=255 +#color_transparency_index_b=255 + + + + +# DEFAULT STATUSMAP LAYOUT METHOD +# This option allows you to specify the default layout method +# the statusmap CGI should use for drawing hosts. If you do +# not use this option, the default is to use user-defined +# coordinates. Valid options are as follows: +# 0 = User-defined coordinates +# 1 = Depth layers +# 2 = Collapsed tree +# 3 = Balanced tree +# 4 = Circular +# 5 = Circular (Marked Up) + +default_statusmap_layout=5 + + + +# DEFAULT STATUSWRL LAYOUT METHOD +# This option allows you to specify the default layout method +# the statuswrl (VRML) CGI should use for drawing hosts. If you +# do not use this option, the default is to use user-defined +# coordinates. Valid options are as follows: +# 0 = User-defined coordinates +# 2 = Collapsed tree +# 3 = Balanced tree +# 4 = Circular + +default_statuswrl_layout=4 + + + +# STATUSWRL INCLUDE +# This option allows you to include your own objects in the +# generated VRML world. It is assumed that the file +# resides in the HTML path (i.e. /usr/local/icinga/share). + +#statuswrl_include=myworld.wrl + + + +# PING SYNTAX +# This option determines what syntax should be used when +# attempting to ping a host from the WAP interface (using +# the statuswml CGI. You must include the full path to +# the ping binary, along with all required options. The +# $HOSTADDRESS$ macro is substituted with the address of +# the host before the command is executed. +# Please note that the syntax for the ping binary is +# notorious for being different on virtually ever *NIX +# OS and distribution, so you may have to tweak this to +# work on your system. + +ping_syntax=/bin/ping -n -U -c 5 $HOSTADDRESS$ + + + +# REFRESH RATE +# This option allows you to specify the refresh rate in seconds +# of various CGIs (status, statusmap, extinfo, and outages). + +refresh_rate=90 + + + +# ESCAPE HTML TAGS +# This option determines whether HTML tags in host and service +# status output is escaped in the web interface. If enabled, +# your plugin output will not be able to contain clickable links. + +escape_html_tags=1 + + + +# PERSISTENT ACKNOWLEDGEMENT COMMENTS +# This options determines whether the initial state of the +# checkbox "Persistent Comment:" for service and host problem +# acknowledgements is checked or unchecked + +persistent_ack_comments=0 + + +# SOUND OPTIONS +# These options allow you to specify an optional audio file +# that should be played in your browser window when there are +# problems on the network. The audio files are used only in +# the status CGI. Only the sound for the most critical problem +# will be played. Order of importance (higher to lower) is as +# follows: unreachable hosts, down hosts, critical services, +# warning services, and unknown services. If there are no +# visible problems, the sound file optionally specified by +# 'normal_sound' variable will be played. +# +# +# = +# +# Note: All audio files must be placed in the /media subdirectory +# under the HTML path (i.e. /usr/local/icinga/share/media/). + +#host_unreachable_sound=hostdown.wav +#host_down_sound=hostdown.wav +#service_critical_sound=critical.wav +#service_warning_sound=warning.wav +#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. Default is main frame. + +action_url_target=main +notes_url_target=main +#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 Icinga. +# Values: 0 = allow editing author names +# 1 = lock author names (disallow editing) + +lock_author_names=1 + + + +# DEFAULT DOWNTIME DURATION +# This option defines the default duration (in seconds) of fixed and +# flexible downtimes. Default is 7200 seconds (2 hours). + +default_downtime_duration=7200 + + + +# DEFAULT EXPIRING ACKNOWLEDGEMENT DURATION +# This option defines the default duration (in seconds) of a expiring +# acknowledgement. Default is 86400 seconds (1 day). + +default_expiring_acknowledgement_duration=86400 + + + +# SHOW LONG PLUGIN OUTPUT IN STATUS OPTION +# This option allows you to specify the length of status information +# in output of status.cgi. If you set the value to 1 it shows the +# full plugin output instead of the first line only. +# Default value is 0. + +status_show_long_plugin_output=0 + + + +# SHOW ONLY HARD STATES IN TAC OPTION +# This options allows you to specify if the tactical overview +# should only show hard states on hosts and services. +# By default disabled, all states will be shown. + +tac_show_only_hard_state=0 + + + +# SHOW CHILD HOSTS IN EXTINFO OPTION +# This Option allows you to specify if the extended host information +# cgi will show child hosts for the selected host. +# 0 = disabled +# 1 = only show immediate child hosts +# 2 = show immediate and all child hosts +# NOTE: Option 2 could be a real performance killer in +# large installations, so use with care. +# By default disabled, as this could be a performance killer. + +extinfo_show_child_hosts=0 + + + +# SUPPRESS MAINTENANCE DOWNTIME +# This options suppresses the state coloring of hosts and services +# that are in a scheduled downtime. It sets their coloring to gray, +# so they no longer draw extra attention to themselves, making it +# so only actual problems are the ones that stand out. +# By default it is disabled. + +suppress_maintenance_downtime=0 + + +# SHOW TAC INFORMATION IN TOP FRAME +# This options places tactical overview information in +# the top frame similar to the view that's in icinga-web. +# By default it is enabled. + +show_tac_header=1 + + +# SHOW PENDING IN TAC HEADER +# This options enables the display of pending counts in +# the tac header. If your display is less than 1024x768 +# and this is enabled, the tactical information may not +# fit well in the top frame. +# By default it is enabled. + +show_tac_header_pending=1 + + + +# SHOW INITIAL STATES IN SHOWLOG OPTION +# This options allows you to specify if initial states +# of hosts and services should be shown in showlog.cgi +# Note: This Option only works if the option +# "log_initial_states" in icinga.cfg is set to 1. +# By default it's enabled. Default is 0. + +#showlog_initial_states=0 + + + +# SHOW CURRENT STATES IN SHOWLOG OPTION +# This options allows you to specify if current states +# of hosts and services should be shown in showlog.cgi +# Note: This Option only works if the option +# "log_current_states" in icinga.cfg is set to 1. +# By default it's enabled. Default is 0. + +#showlog_current_states=0 + + + +# CSV DELIMITER +# This option determines the character which should act as +# delimiter. Default is ";". + +#csv_delimiter=; + + + +# CSV DATA ENCLOSURE +# This option determines the character which should act as +# data enclosure to wrap in the data. Default is "'". + +#csv_data_enclosure=' + + + +# TAB-FRIENDLY S +# Activating this option changes the <title> of status.cgi +# and extinfo.cgi when they refer to a single host, service, +# or group. They will then read: +# [Host] +# {HostGroup} +# ServiceDesc @ Host +# (ServiceGroup) +# These are easier to read and find if you use (many) tabs +# in your browser. +# Default is enabled. 0=disabled, 1=enabled + +tab_friendly_titles=1 + + +# SERVICE STATES TO ANNOTATE WITH CURRENT NOTIFICATION NO. +# Set this to an OR of the service state identifiers for +# which status.cgi should not only report "Attempts" (e.g., +# "3/3" for a HARD non-OK state with max_check_attempts=3) +# but also the current notification number ("(#0)" if no +# problem notification has been sent yet, etc.). This is +# helpful to identify services which switched between +# different non-OK states a lot, or services which have a +# first_notification_delay set and are "not yet officially" +# considered in trouble. +# Relevant values from include/statusdata.h (look them up +# *there* if you want to be *really* sure): +# #define SERVICE_PENDING 1 +# #define SERVICE_OK 2 +# #define SERVICE_WARNING 4 +# #define SERVICE_UNKNOWN 8 +# #define SERVICE_CRITICAL 16 +# You'll likely want to use add_notif_num_hard=0 (default) +# or add_notif_num_hard=28 (warn+crit+unknown). There's an +# add_notif_num_soft affecting services in a SOFT state +# for sake of completeness, too. + +#add_notif_num_hard=28 +#add_notif_num_soft=0 + + + +# 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/ + + + diff --git a/package/icinga/src/etc/icinga/cgiauth.cfg b/package/icinga/src/etc/icinga/cgiauth.cfg new file mode 100644 index 000000000..705852959 --- /dev/null +++ b/package/icinga/src/etc/icinga/cgiauth.cfg @@ -0,0 +1,8 @@ +#urn:your:name:testicinga:host1admin=switch1:PING:r +#urn:your:name:testicinga:host1admin=*:PING +#urn:your:name:testicinga:host1admin=localhost:PING +#urn:your:name:testicinga:host1admin=localhost:Swap Usage:r +#urn:your:name:testicinga:superadmin=*:*:w +#urn:your:name:testicinga:host1admin=@core-switches,@linux-servers:*:r +#urn:your:name:testicinga:host1admin=@core-routers,@core-switches:@LDAP:w +#urn:your:name:testicinga:host1admin=@core-routers,@core-switches,@linux-servers:@DNS:r diff --git a/package/icinga/src/etc/icinga/icinga.cfg b/package/icinga/src/etc/icinga/icinga.cfg new file mode 100644 index 000000000..a95462293 --- /dev/null +++ b/package/icinga/src/etc/icinga/icinga.cfg @@ -0,0 +1,1484 @@ +############################################################################## +# +# 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 +# in the config file!!! + +log_file=/var/log/icinga.log + + + +# 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/icinga/objects/commands.cfg +cfg_file=/etc/icinga/objects/contacts.cfg +cfg_file=/etc/icinga/objects/timeperiods.cfg +cfg_file=/etc/icinga/objects/templates.cfg + +# Definitions for monitoring the local (Linux) host +cfg_file=/etc/icinga/objects/localhost.cfg + +# Definitions for monitoring a Windows machine +#cfg_file=/etc/icinga/objects/windows.cfg + +# Definitions for monitoring a router/switch +#cfg_file=/etc/icinga/objects/switch.cfg + +# Definitions for monitoring a network printer +#cfg_file=/etc/icinga/objects/printer.cfg + +# Definitions for ido2db process checks +#cfg_file=/etc/icinga/objects/ido2db_check_proc.cfg + +# You can also tell Icinga 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/icinga/servers +#cfg_dir=/etc/icinga/printers +#cfg_dir=/etc/icinga/switches +#cfg_dir=/etc/icinga/routers + +# Definitions for broker modules like idoutils.cfg +cfg_dir=/etc/icinga/modules + + + +# OBJECT CACHE FILE +# This option determines where object definitions are cached when +# 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 Icinga starts. + +object_cache_file=/var/objects.cache + + + +# PRE-CACHED OBJECT FILE +# This options determines the location of the precached object file. +# 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 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 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/objects.precache + + + +# RESOURCE FILE +# This is an optional resource file that contains $USERx$ macro +# definitions. Multiple resource files can be specified by using +# multiple resource_file definitions. The CGIs will not attempt to +# read the contents of resource files, so information that is +# considered to be sensitive (usernames, passwords, etc) can be +# defined as macros in this file and restrictive permissions (600) +# can be placed on this file. + +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 Icinga +# restarts. + +status_file=/var/run/icinga/status.dat + + + +# STATUS FILE UPDATE INTERVAL +# This option determines the frequency (in seconds) that +# 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 + + + +# ICINGA USER +# This determines the effective user that Icinga should run as. +# You can either supply a username or a UID. + +icinga_user=icinga + + + +# ICINGA GROUP +# This determines the effective group that Icinga should run as. +# You can either supply a group name or a GID. + +icinga_group=icinga + + + +# EXTERNAL COMMAND OPTION +# This option allows you to specify whether or not Icinga should check +# for external commands (in the command file defined below). By default +# 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 + +check_external_commands=1 + + + +# EXTERNAL COMMAND CHECK INTERVAL +# 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 +# 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, Icinga will also check for external commands after +# event handlers are executed. +# NOTE: Setting this value to -1 causes Icinga to check the external +# command file as often as possible. + +#command_check_interval=15s +command_check_interval=-1 + + + +# EXTERNAL COMMAND FILE +# 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 +# directory level instead of on the file, as the file is deleted every +# time its contents are processed. + +command_file=/var/rw/icinga.cmd + + + +# EXTERNAL COMMAND BUFFER SLOTS +# This settings is used to tweak the number of items or "slots" that +# 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 Icinga will use to store its PID number +# in when it is running in daemon mode. + +lock_file=/var/icinga.lock + + + +# TEMP FILE +# 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 Icinga is +# running. + +temp_file=/var/icinga.tmp + + + +# TEMP PATH +# This is path where Icinga 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=-1 + + + +# EVENT BROKER MODULE(S) +# This directive is 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 Icinga or Icinga +# 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 Icinga... +# +# The correct/safe way of updating a module is by using one of these methods: +# 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: +# +# broker_module=<modulepath> [moduleargs] + +#broker_module=/somewhere/module1.o +#broker_module=/somewhere/module2.o arg1 arg2=3 debug=0 + +# Uncomment this to enable idomod.o +#broker_module=/usr/bin/idomod.o config_file=/etc/icinga/idomod.cfg + + + +# LOG ROTATION METHOD +# 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) +# d = Daily rotation (midnight every day) +# w = Weekly rotation (midnight on Saturday evening) +# m = Monthly rotation (midnight last day of month) + +log_rotation_method=d + + + +# LOG ARCHIVE PATH +# This is the directory where archived (rotated) log files should be +# placed (assuming you've chosen to do log rotation). + +log_archive_path=/var/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 FOR SYSLOG +# If you want messages logged to the syslog facility, as well as the +# 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. + +log_notifications=1 + + + +# SERVICE RETRY LOGGING OPTION +# If you don't want service check retries to be logged, set this value +# to 0. If retries should be logged, set the value to 1. + +log_service_retries=1 + + + +# HOST RETRY LOGGING OPTION +# If you don't want host check retries to be logged, set this value to +# 0. If retries should be logged, set the value to 1. + +log_host_retries=1 + + + +# EVENT HANDLER LOGGING OPTION +# If you don't want host and service event handlers to be logged, set +# this value to 0. If event handlers should be logged, set the value +# to 1. + +log_event_handlers=1 + + + +# INITIAL STATES LOGGING OPTION +# 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 +# statistics reporting, you do not need to enable this option. In +# this case, set the value to 0. + +log_initial_states=0 + + + +# 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 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 are logged. + +log_external_commands=1 + + + +# PASSIVE CHECKS LOGGING OPTION +# 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. + +log_passive_checks=1 + + + +# LOG EXTERNAL COMMAND USER - THIS WILL BE DEPRECATED!!! +# Future Icinga versions after 1.5 will ignore this config option, +# use the CGI logging feature instead (or any other logger/wrapper +# to the command pipe). +# +# This option allows you to enable the logging of the current user +# of external commands. +# The syntax will be CMD;username;cmdargs instead of CMD;cmdargs +# written to the logs, if the external application sends that +# correctly. +# Since this will break compatibility with existing log parsers, +# it is intentionally disabled by default. + +log_external_commands_user=0 + + + +# 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. +# The global event handler is executed immediately prior to the event +# handler that you have optionally specified in each host or +# service definition. 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. + +#global_host_event_handler=somecommand +#global_service_event_handler=somecommand + + + +# SERVICE INTER-CHECK DELAY METHOD +# 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. +# Using the dumb setting will cause all checks to be scheduled +# at the same time (with no delay between them)! This is not a +# good thing for production, but is useful when testing the +# parallelization functionality. +# n = None - don't use any delay between checks +# d = Use a "dumb" delay of 1 second between checks +# s = Use "smart" inter-check delay calculation +# x.xx = Use an inter-check delay of x.xx seconds + +service_inter_check_delay_method=s + + + +# MAXIMUM SERVICE CHECK SPREAD +# This variable determines the timeframe (in minutes) from the +# program start time that an initial check of all services should +# be completed. Default is 30 minutes. + +max_service_check_spread=30 + + + +# SERVICE CHECK INTERLEAVE FACTOR +# This variable determines how service checks are interleaved. +# 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 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 +# x = Use an interleave factor of x, where x is a +# number greater than or equal to 1. + +service_interleave_factor=s + + + +# HOST INTER-CHECK DELAY METHOD +# 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. +# Using the dumb setting will cause all checks to be scheduled +# at the same time (with no delay between them)! +# n = None - don't use any delay between checks +# d = Use a "dumb" delay of 1 second between checks +# s = Use "smart" inter-check delay calculation +# x.xx = Use an inter-check delay of x.xx seconds + +host_inter_check_delay_method=s + + + +# MAXIMUM HOST CHECK SPREAD +# This variable determines the timeframe (in minutes) from the +# program start time that an initial check of all hosts should +# be completed. Default is 30 minutes. + +max_host_check_spread=30 + + + +# MAXIMUM CONCURRENT SERVICE CHECKS +# This option allows you to specify the maximum number of +# service checks that can be run in parallel at any given time. +# Specifying a value of 1 for this variable essentially prevents +# any service checks from being parallelized. A value of 0 +# will not restrict the number of concurrent checks that are +# being executed. + +max_concurrent_checks=0 + + + +# HOST AND SERVICE CHECK REAPER FREQUENCY +# 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 Icinga so it can perform other +# duties. + +max_check_result_reaper_time=30 + + + + +# CHECK RESULT PATH +# 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 Icinga has access +# to this directory! + +check_result_path=/var/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 Icinga, 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 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. +# 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 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. +# 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 Icinga will use soft state +# information when checking host and service dependencies. Normally +# 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: +# 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 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 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. +# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE +# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY + +auto_reschedule_checks=0 + + + +# AUTO-RESCHEDULING INTERVAL +# 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. +# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE +# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY + +auto_rescheduling_interval=30 + + + +# AUTO-RESCHEDULING WINDOW +# This option determines the "window" of time (in seconds) that +# 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 +# enabled. Default is 180 seconds (3 minutes). +# WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE +# PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY + +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 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 +notification_timeout=30 +ocsp_timeout=5 +perfdata_timeout=5 + + + +# RETAIN STATE INFORMATION +# This setting determines whether or not Icinga will save state +# information for services and hosts before it shuts down. Upon +# 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 Icinga down a bit when it (re)starts. Since its only +# a one-time penalty, I think its well worth the additional +# startup delay. + +retain_state_information=1 + + + +# STATE RETENTION FILE +# 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 Icinga is restarted. +# This file is used only if the retain_state_information +# variable is set to 1. + +state_retention_file=/var/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/sync.dat + + + +# RETENTION DATA UPDATE INTERVAL +# This setting determines how often (in minutes) that Icinga +# will automatically save retention data during normal operation. +# 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. + +retention_update_interval=60 + + + +# USE RETAINED PROGRAM STATE +# 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 +# to 0. + +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 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 +# value to 1. If not, set this value to 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 Icinga 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 + + + +# INTERVAL LENGTH +# This is the seconds per unit interval as used in the +# host/contact/service configuration files. Setting this to 60 means +# that each interval is one minute long (60 seconds). Other settings +# have not been tested much, so your mileage is likely to vary... + +interval_length=60 + + + +# 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 +# enable the aggressive check option. Read the docs for more info +# on what aggressive host check is or check out the source code in +# base/checks.c + +use_aggressive_host_checking=0 + + + +# SERVICE CHECK EXECUTION OPTION +# 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 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! +# Values: 1 = enable checks, 0 = disable checks + +execute_service_checks=1 + + + +# PASSIVE SERVICE CHECK ACCEPTANCE OPTION +# 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 + +accept_passive_service_checks=1 + + + +# HOST CHECK EXECUTION OPTION +# 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 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! +# Values: 1 = enable checks, 0 = disable checks + +execute_host_checks=1 + + + +# PASSIVE HOST CHECK ACCEPTANCE OPTION +# 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 + +accept_passive_host_checks=1 + + + +# NOTIFICATIONS OPTION +# 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 + +enable_notifications=1 + + + +# EVENT HANDLER USE OPTION +# 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 + +enable_event_handlers=1 + + + +# PROCESS PERFORMANCE DATA OPTION +# 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 +# data will be processed using the service_perfdata_command (also +# defined below). Read the HTML docs for more information on +# performance data. +# Values: 1 = process performance data, 0 = do not process performance data + +process_performance_data=0 + + + +# 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 +# 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_perfdata_command=process-host-perfdata +#service_perfdata_command=process-service-perfdata + + + +# 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 +# process_performance_data option (above) is set to 1. + +#host_perfdata_file=/tmp/host-perfdata +#service_perfdata_file=/tmp/service-perfdata + + + +# HOST AND SERVICE PERFORMANCE DATA FILE TEMPLATES +# These options determine what data is written (and how) to the +# performance data files. The templates may contain macros, special +# characters (\t for tab, \r for carriage return, \n for newline) +# and plain text. A newline is automatically added after each write +# to the performance data file. Some examples of what you can do are +# shown below. + +#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. 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 AND SERVICE PERFORMANCE DATA FILE PROCESSING INTERVAL +# These options determine how often (in seconds) the host and service +# performance data files are processed using the commands defined +# 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 AND SERVICE PERFORMANCE DATA FILE PROCESSING COMMANDS +# These commands are used to periodically process the host and +# service performance data files. The interval at which the +# processing occurs is determined by the options above. + +#host_perfdata_file_processing_command=process-host-perfdata-file +#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. +# 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 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 +# implementing distributed monitoring. +# Values: 1 = obsess over services, 0 = do not obsess (default) + +obsess_over_services=0 + + + +# OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND +# This is the command that is run for every service check that is +# 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 +# more information on implementing distributed monitoring. + +#ocsp_command=somecommand + + + +# OBSESS OVER HOST CHECKS OPTION +# 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 +# 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 Icinga. This command is executed only if the +# obsess_over_hosts option (above) is set to 1.