diff options
| author | Waldemar Brodkorb <wbx@openadk.org> | 2014-04-26 09:53:28 +0200 |
|---|---|---|
| committer | Waldemar Brodkorb <wbx@openadk.org> | 2014-04-26 09:56:01 +0200 |
| commit | 1aacea2738c291c5e144ad1913c3ed6cca9f87db (patch) | |
| tree | f8a39f8d250a1a8bc1e56a3607b59231281f1927 /package/icinga/src/etc | |
| parent | 5bdd93287770808c4100008b8b0b39c1a55bf098 (diff) | |
use XZ tarballs as default
Diffstat (limited to 'package/icinga/src/etc')
| -rw-r--r-- | package/icinga/src/etc/icinga/cgi.cfg | 653 | ||||
| -rw-r--r-- | package/icinga/src/etc/icinga/cgiauth.cfg | 8 | ||||
| -rw-r--r-- | package/icinga/src/etc/icinga/icinga.cfg | 1484 | ||||
| -rw-r--r-- | package/icinga/src/etc/icinga/mrtg.cfg | 180 | ||||
| -rw-r--r-- | package/icinga/src/etc/icinga/objects/commands.cfg | 250 | ||||
| -rw-r--r-- | package/icinga/src/etc/icinga/objects/contacts.cfg | 53 | ||||
| -rw-r--r-- | package/icinga/src/etc/icinga/objects/localhost.cfg | 167 | ||||
| -rw-r--r-- | package/icinga/src/etc/icinga/objects/notifications.cfg | 132 | ||||
| -rw-r--r-- | package/icinga/src/etc/icinga/objects/printer.cfg | 83 | ||||
| -rw-r--r-- | package/icinga/src/etc/icinga/objects/switch.cfg | 111 | ||||
| -rw-r--r-- | package/icinga/src/etc/icinga/objects/templates.cfg | 188 | ||||
| -rw-r--r-- | package/icinga/src/etc/icinga/objects/timeperiods.cfg | 92 | ||||
| -rw-r--r-- | package/icinga/src/etc/icinga/objects/windows.cfg | 143 | ||||
| -rw-r--r-- | package/icinga/src/etc/icinga/resource.cfg | 32 |
14 files changed, 0 insertions, 3576 deletions
diff --git a/package/icinga/src/etc/icinga/cgi.cfg b/package/icinga/src/etc/icinga/cgi.cfg deleted file mode 100644 index 35057eb75..000000000 --- a/package/icinga/src/etc/icinga/cgi.cfg +++ /dev/null @@ -1,653 +0,0 @@ -################################################################# -# -# 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. -# -# -# <varname>=<sound_file> -# -# 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 <TITLE>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 deleted file mode 100644 index 705852959..000000000 --- a/package/icinga/src/etc/icinga/cgiauth.cfg +++ /dev/null @@ -1,8 +0,0 @@ -#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 deleted file mode 100644 index a95462293..000000000 --- a/package/icinga/src/etc/icinga/icinga.cfg +++ /dev/null @@ -1,1484 +0,0 @@ -############################################################################## -# -# 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. The command -# argument is the short name of a command definition that you -# define in your host configuration file. Read the HTML docs for -# more information on implementing distributed monitoring. - -#ochp_command=somecommand - - - -# TRANSLATE PASSIVE HOST CHECKS OPTION -# This determines whether or not Icinga will translate -# DOWN/UNREACHABLE passive host check results into their proper -# state for this instance of Icinga. This option is useful -# if you have distributed or failover monitoring setup. In -# 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 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) - -translate_passive_host_checks=0 - - - -# PASSIVE HOST CHECKS ARE SOFT OPTION -# 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. -# Values: 0 = passive checks are HARD, 1 = passive checks are SOFT - -passive_host_checks_are_soft=0 - - - -# ORPHANED HOST/SERVICE CHECK OPTIONS -# These options determine whether or not 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 -# checks may never get rescheduled. A similar situation exists for -# host checks, although the exact scheduling details differ a bit -# from service checks. Orphaned checks seem to be a rare -# problem and should not happen under normal circumstances. -# If you have problems with service checks never getting -# rescheduled, make sure you have orphaned service checks enabled. -# Values: 1 = enable checks, 0 = disable checks - -check_for_orphaned_services=1 -check_for_orphaned_hosts=1 - - - -# 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 Icinga will periodically -# check the "freshness" of service results. Enabling this option -# is useful for ensuring passive checks are received in a timely -# manner. -# Values: 1 = enabled freshness checking, 0 = disable freshness checking - -check_service_freshness=1 - - - -# SERVICE FRESHNESS CHECK INTERVAL -# 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. - -service_freshness_check_interval=60 - - - -# HOST FRESHNESS CHECK OPTION -# 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. -# Values: 1 = enabled freshness checking, 0 = disable freshness checking - -check_host_freshness=0 - - - -# HOST FRESHNESS CHECK INTERVAL -# 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. - -host_freshness_check_interval=60 - - - - -# ADDITIONAL FRESHNESS THRESHOLD LATENCY -# 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). - -additional_freshness_latency=15 - - - - -# FLAP DETECTION OPTION -# 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 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 -# the HTML documentation before enabling this feature! -# Values: 1 = enable flap detection -# 0 = disable flap detection (default) - -enable_flap_detection=1 - - - -# FLAP DETECTION THRESHOLDS FOR HOSTS AND SERVICES -# Read the HTML documentation on flap detection for -# an explanation of what this option does. This option -# has no effect if flap detection is disabled. - -low_service_flap_threshold=5.0 -high_service_flap_threshold=20.0 -low_host_flap_threshold=5.0 -high_host_flap_threshold=20.0 - - - -# DATE FORMAT OPTION -# This option determines how short dates are displayed. Valid options -# include: -# us (MM-DD-YYYY HH:MM:SS) -# euro (DD-MM-YYYY HH:MM:SS) -# iso8601 (YYYY-MM-DD HH:MM:SS) -# strict-iso8601 (YYYY-MM-DDTHH:MM:SS) -# - -date_format=us - - - - -# TIMEZONE OFFSET -# This option is used to override the default timezone that this -# 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/icinga/sbin/"> -# SetEnv TZ "Australia/Brisbane" -# ... -# </Directory> - -#use_timezone=US/Mountain -#use_timezone=Australia/Brisbane - - - - -# 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 -# Icinga with embedded Perl support, this option has no effect. - -p1_file=/usr/lib/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 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=0 - - - -# EMBEDDED PERL USAGE OPTION -# 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 -# information on how this option works. - -use_embedded_perl_implicitly=1 - - - -# 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 -# object types. - -illegal_object_name_chars=`~!$%^&*|'"<>?,()= - - - -# ILLEGAL MACRO OUTPUT CHARACTERS -# This option allows you to specify illegal characters that are -# stripped from macros before being used in notifications, event -# handlers, etc. This DOES NOT affect macros used in service or -# host check commands. -# The following macros are stripped of the characters you specify: -# $HOSTOUTPUT$ -# $HOSTPERFDATA$ -# $HOSTACKAUTHOR$ -# $HOSTACKCOMMENT$ -# $SERVICEOUTPUT$ -# $SERVICEPERFDATA$ -# $SERVICEACKAUTHOR$ -# $SERVICEACKCOMMENT$ - -illegal_macro_output_chars=`~$&|'"<> - - - -# REGULAR EXPRESSION MATCHING -# This option controls whether or not regular expression matching -# takes place in the object config files. Regular expression -# matching is used to match host, hostgroup, service, and service -# group names/descriptions in some fields of various object types. -# Values: 1 = enable regexp matching, 0 = disable regexp matching - -use_regexp_matching=0 - - - -# "TRUE" REGULAR EXPRESSION MATCHING -# This option controls whether or not "true" regular expression -# matching takes place in the object config files. This option -# only has an effect if regular expression matching is enabled -# (see above). If this option is DISABLED, regular expression -# matching only occurs if a string contains wildcard characters -# (* and ?). If the option is ENABLED, regexp matching occurs -# all the time (which can be annoying). -# Values: 1 = enable true matching, 0 = disable true matching - -use_true_regexp_matching=0 - - - -# ADMINISTRATOR EMAIL/PAGER ADDRESSES -# The email and pager address of a global administrator (likely you). -# Icinga never uses these values itself, but you can access them by -# using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification -# commands. - -admin_email=icinga@localhost -admin_pager=pageicinga@localhost - - - -# DAEMON CORE DUMP OPTION -# 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 -# a core file will be produced, but that's just life... -# Values: 1 - Allow core dumps -# 0 - Do not allow core dumps (default) - -daemon_dumps_core=0 - - - -# LARGE INSTALLATION TWEAKS OPTION -# 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 -# 0 - Disable tweaks (default) - -use_large_installation_tweaks=0 - - - -# ENABLE ENVIRONMENT MACROS -# 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 -# large installations, as it will consume a bit more memory and (more -# importantly) consume more CPU. -# 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=0 - - - -# CHILD PROCESS MEMORY OPTION -# 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. -# Value: 1 - Free memory in child processes -# 0 - Do not free memory in child processes - -#free_child_process_memory=1 - - - -# CHILD PROCESS FORKING BEHAVIOR -# This option determines how 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 -# save a great deal on CPU usage (in large installs), so you might -# want to consider using this. If you specify a value here, it will -# program defaults. -# Value: 1 - Child processes fork() twice -# 0 - Child processes fork() just once - -#child_processes_fork_twice=1 - - - -# DEBUG LEVEL -# This option determines how much (if any) debugging information will -# be written to the debug file. OR values together to log multiple -# types of information. -# Values: -# -1 = Everything -# 0 = Nothing -# 1 = Functions -# 2 = Configuration -# 4 = Process information -# 8 = Scheduled events -# 16 = Host/service checks -# 32 = Notifications -# 64 = Event broker -# 128 = External commands -# 256 = Commands -# 512 = Scheduled downtime -# 1024 = Comments -# 2048 = Macros - -debug_level=0 - - - -# DEBUG VERBOSITY -# This option determines how verbose the debug log out will be. -# Values: 0 = Brief output -# 1 = More detailed -# 2 = Very detailed - -debug_verbosity=1 - - - -# DEBUG FILE -# This option determines where Icinga should write debugging information. - -debug_file=/var/icinga.debug - - - -# MAX DEBUG FILE SIZE -# This option determines the maximum size (in bytes) of the debug file. If -# the file grows larger than this size, it will be renamed with a .old -# extension. If a file already exists with a .old extension it will -# automatically be deleted. This helps ensure your disk space usage doesn't -# get out of control when debugging Icinga. - -# 100M -max_debug_file_size=100000000 - - - -# 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 diff --git a/package/icinga/src/etc/icinga/mrtg.cfg b/package/icinga/src/etc/icinga/mrtg.cfg deleted file mode 100644 index bcec12731..000000000 --- a/package/icinga/src/etc/icinga/mrtg.cfg +++ /dev/null @@ -1,180 +0,0 @@ -################################################################### -# MRTG Graphs: Icinga Statistics -# -# You can add the following entries to your MRTG config file to -# begin graphing several Icinga statistics which can be useful for -# debugging and trending purposes. The icingastats binary (which is -# included as part of the Icinga distribution) is used to generate -# the data. -################################################################### - -# Service Latency and Execution Time -Target[icinga-a]: `/usr/bin/icingastats --mrtg --data=AVGACTSVCLAT,AVGACTSVCEXT,PROGRUNTIME,ICINGAVERPID` -MaxBytes[icinga-a]: 100000 -Title[icinga-a]: Average Service Check Latency and Execution Time -PageTop[icinga-a]: <H1>Average Service Check Latency and Execution Time</H1> -Options[icinga-a]: growright,gauge,nopercent -YLegend[icinga-a]: Milliseconds -ShortLegend[icinga-a]: -LegendI[icinga-a]: Latency: -LegendO[icinga-a]: Execution Time: -Legend1[icinga-a]: Latency -Legend2[icinga-a]: Execution Time -Legend3[icinga-a]: Maximal 5 Minute Latency -Legend4[icinga-a]: Maximal 5 Minute Execution Time - - -# Service Percent State Change -Target[icinga-b]: `/usr/bin/icingastats --mrtg --data=AVGACTSVCPSC,AVGPSVSVCPSC,PROGRUNTIME,ICINGAVERPID` -MaxBytes[icinga-b]: 100 -Title[icinga-b]: Average Service State Change -PageTop[icinga-b]: <H1>Average Service State Change</H1> -Options[icinga-b]: growright,gauge,nopercent -YLegend[icinga-b]: Percent -ShortLegend[icinga-b]: -LegendI[icinga-b]: Active Check % Change: -LegendO[icinga-b]: Passive Check % Change: -Legend1[icinga-b]: State Change -Legend2[icinga-b]: State Change -Legend3[icinga-b]: Maximal 5 Minute State Change -Legend4[icinga-b]: Maximal 5 Minute State Change - - -# Host Latency and Execution Time -Target[icinga-c]: `/usr/bin/icingastats --mrtg --data=AVGACTHSTLAT,AVGACTHSTEXT,PROGRUNTIME,ICINGAVERPID` -MaxBytes[icinga-c]: 100000 -Title[icinga-c]: Average Host Check Latency and Execution Time -PageTop[icinga-c]: <H1>Average Host Check Latency and Execution Time</H1> -Options[icinga-c]: growright,gauge,nopercent -YLegend[icinga-c]: Milliseconds -ShortLegend[icinga-c]: -LegendI[icinga-c]: Latency: -LegendO[icinga-c]: Execution Time: -Legend1[icinga-c]: Latency -Legend2[icinga-c]: Execution Time -Legend3[icinga-c]: Maximal 5 Minute Latency -Legend4[icinga-c]: Maximal 5 Minute Execution Time - - -# Host Percent State Change -Target[icinga-d]: `/usr/bin/icingastats --mrtg --data=AVGACTHSTPSC,AVGPSVHSTPSC,PROGRUNTIME,ICINGAVERPID` -MaxBytes[icinga-d]: 100 -Title[icinga-d]: Average Host State Change -PageTop[icinga-d]: <H1>Average Host State Change</H1> -Options[icinga-d]: growright,gauge,nopercent -YLegend[icinga-d]: Percent -ShortLegend[icinga-d]: -LegendI[icinga-d]: Active Check % Change: -LegendO[icinga-d]: Passive Check % Change: -Legend1[icinga-d]: State Change -Legend2[icinga-d]: State Change -Legend3[icinga-d]: Maximal 5 Minute State Change -Legend4[icinga-d]: Maximal 5 Minute State Change - - -# Hosts/Services Actively Checked -Target[icinga-e]: `/usr/bin/icingastats --mrtg --data=NUMHSTACTCHK5M,NUMSVCACTCHK5M,PROGRUNTIME,ICINGAVERPID` -MaxBytes[icinga-e]: 7000 -Title[icinga-e]: Hosts/Services Actively Checked -PageTop[icinga-e]: <H1>Hosts/Services Actively Checked</H1> -Options[icinga-e]: growright,gauge,nopercent -YLegend[icinga-e]: Total -ShortLegend[icinga-e]: -LegendI[icinga-e]: Hosts: -LegendO[icinga-e]: Services: - - -# Hosts/Services Passively Checked -Target[icinga-f]: `/usr/bin/icingastats --mrtg --data=NUMHSTPSVCHK5M,NUMSVCPSVCHK5M,PROGRUNTIME,ICINGAVERPID` -MaxBytes[icinga-f]: 7000 -Title[icinga-f]: Hosts/Services Passively Checked -PageTop[icinga-f]: <H1>Hosts/Services Passively Checked</H1> -Options[icinga-f]: growright,gauge,nopercent -YLegend[icinga-f]: Total -ShortLegend[icinga-f]: -LegendI[icinga-f]: Hosts: -LegendO[icinga-f]: Services: - - -# Used/Avail External Command Buffers -Target[icinga-g]: `/usr/bin/icingastats --mrtg --data=TOTCMDBUF,USEDCMDBUF,PROGRUNTIME,ICINGAVERPID` -MaxBytes[icinga-g]: 7000 -Title[icinga-g]: External Command Buffers -PageTop[icinga-g]: <H1>External Command Buffers</H1> -Options[icinga-g]: growright,gauge,nopercent -YLegend[icinga-g]: Buffers -ShortLegend[icinga-g]: -LegendI[icinga-g]: Total: -LegendO[icinga-g]: Used: - - -# Active Host Checks -Target[icinga-i]: `/usr/bin/icingastats --mrtg --data=NUMSACTHSTCHECKS5M,NUMOACTHSTCHECKS5M,PROGRUNTIME,ICINGAVERPID` -MaxBytes[icinga-i]: 7000 -Title[icinga-i]: Active Host Checks -PageTop[icinga-i]: <H1>Active Host Checks</H1> -Options[icinga-i]: growright,gauge,nopercent -YLegend[icinga-i]: Checks -ShortLegend[icinga-i]: -LegendI[icinga-i]: Scheduled Checks: -LegendO[icinga-i]: On-Demand Checks: - - -# Active Service Checks -Target[icinga-j]: `/usr/bin/icingastats --mrtg --data=NUMSACTSVCCHECKS5M,NUMOACTSVCCHECKS5M,PROGRUNTIME,ICINGAVERPID` -MaxBytes[icinga-j]: 7000 -Title[icinga-j]: Active Service Checks -PageTop[icinga-j]: <H1>Active Service Checks</H1> -Options[icinga-j]: growright,gauge,nopercent -YLegend[icinga-j]: Checks -ShortLegend[icinga-j]: -LegendI[icinga-j]: Scheduled Checks: -LegendO[icinga-j]: On-Demand Checks: - - -# Passive Host/Service Checks -Target[icinga-k]: `/usr/bin/icingastats --mrtg --data=NUMPSVHSTCHECKS5M,NUMPSVSVCCHECKS5M,PROGRUNTIME,ICINGAVERPID` -MaxBytes[icinga-k]: 7000 -Title[icinga-k]: Passive Host/Service Checks -PageTop[icinga-k]: <H1>Passive Host/Service Checks</H1> -Options[icinga-k]: growright,gauge,nopercent -YLegend[icinga-k]: Checks -ShortLegend[icinga-k]: -LegendI[icinga-k]: Host Checks: -LegendO[icinga-k]: Service Checks: - - -# Cached Host/Service Checks -Target[icinga-l]: `/usr/bin/icingastats --mrtg --data=NUMCACHEDHSTCHECKS5M,NUMCACHEDSVCCHECKS5M,PROGRUNTIME,ICINGAVERPID` -MaxBytes[icinga-l]: 7000 -Title[icinga-l]: Cached Host/Service Checks -PageTop[icinga-l]: <H1>Cached Host/Service Checks</H1> -Options[icinga-l]: growright,gauge,nopercent -YLegend[icinga-l]: Checks -ShortLegend[icinga-l]: -LegendI[icinga-l]: Host Checks: -LegendO[icinga-l]: Service Checks: - - -# External Commands -Target[icinga-m]: `/usr/bin/icingastats --mrtg --data=NUMEXTCMDS5M,0,PROGRUNTIME,ICINGAVERPID` -MaxBytes[icinga-m]: 7000 -Title[icinga-m]: External Commands -PageTop[icinga-m]: <H1>External Commands</H1> -Options[icinga-m]: growright,gauge,nopercent -YLegend[icinga-m]: Commands -ShortLegend[icinga-m]: -LegendI[icinga-m]: Commands: -LegendO[icinga-m]: - - -# Parallel/Service Host Checks -Target[icinga-n]: `/usr/bin/icingastats --mrtg --data=NUMPARHSTCHECKS5M,NUMSERHSTCHECKS5M,PROGRUNTIME,ICINGAVERPID` -MaxBytes[icinga-n]: 7000 -Title[icinga-n]: Parallel/Serial Host Checks -PageTop[icinga-n]: <H1>Parallel/Serial Host Checks</H1> -Options[icinga-n]: growright,gauge,nopercent -YLegend[icinga-n]: Checks -ShortLegend[icinga-n]: -LegendI[icinga-n]: Parallel Checks: -LegendO[icinga-n]: Serial Checks: diff --git a/package/icinga/src/etc/icinga/objects/commands.cfg b/package/icinga/src/etc/icinga/objects/commands.cfg deleted file mode 100644 index 5f29d7115..000000000 --- a/package/icinga/src/etc/icinga/objects/commands.cfg +++ /dev/null @@ -1,250 +0,0 @@ -############################################################################### -# COMMANDS.CFG - SAMPLE COMMAND DEFINITIONS FOR ICINGA -# -# NOTES: This config file provides you with some example command definitions -# that you can reference in host, service, and contact definitions. -# -# You don't need to keep commands in a separate file from your other -# object definitions. This has been done just to make things easier to -# understand. -# -############################################################################### - - -################################################################################ -# -# SAMPLE NOTIFICATION COMMANDS -# -# These are some example notification commands. They may or may not work on -# your system without modification. As an example, some systems will require -# you to use "/usr/bin/mailx" instead of "/usr/bin/mail" in the commands below. -# -################################################################################ - - -# 'notify-host-by-email' command definition -define command{ - command_name notify-host-by-email - command_line /usr/bin/printf "%b" "***** Icinga *****\n\nNotification Type: $NOTIFICATIONTYPE$\nHost: $HOSTNAME$\nState: $HOSTSTATE$\nAddress: $HOSTADDRESS$\nInfo: $HOSTOUTPUT$\n\nDate/Time: $LONGDATETIME$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Host Alert: $HOSTNAME$ is $HOSTSTATE$ **" $CONTACTEMAIL$ - } - -# 'notify-service-by-email' command definition -define command{ - command_name notify-service-by-email - command_line /usr/bin/printf "%b" "***** Icinga *****\n\nNotification Type: $NOTIFICATIONTYPE$\n\nService: $SERVICEDESC$\nHost: $HOSTALIAS$\nAddress: $HOSTADDRESS$\nState: $SERVICESTATE$\n\nDate/Time: $LONGDATETIME$\n\nAdditional Info:\n\n$SERVICEOUTPUT$\n" | /usr/bin/mail -s "** $NOTIFICATIONTYPE$ Service Alert: $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ **" $CONTACTEMAIL$ - } - - - - - -################################################################################ -# -# SAMPLE HOST CHECK COMMANDS -# -################################################################################ - - -# This command checks to see if a host is "alive" by pinging it -# The check must result in a 100% packet loss or 5 second (5000ms) round trip -# average time to produce a critical error. -# Note: Five ICMP echo packets are sent (determined by the '-p 5' argument) - -# 'check-host-alive' command definition -define command{ - command_name check-host-alive - command_line $USER1$/check_ping -H $HOSTADDRESS$ -w 3000.0,80% -c 5000.0,100% -p 5 - } - - - - -################################################################################ -# -# SAMPLE SERVICE CHECK COMMANDS -# -# These are some example service check commands. They may or may not work on -# your system, as they must be modified for your plugins. See the HTML -# documentation on the plugins for examples of how to configure command definitions. -# -# NOTE: The following 'check_local_...' functions are designed to monitor -# various metrics on the host that Icinga is running on (i.e. this one). -################################################################################ - -# 'check_local_disk' command definition -#define command{ -# command_name check_local_disk -# command_line $USER1$/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$ -# } - - -# 'check_local_load' command definition -define command{ - command_name check_local_load - command_line $USER1$/check_load -w $ARG1$ -c $ARG2$ - } - - -# 'check_local_procs' command definition -#define command{ -# command_name check_local_procs -# command_line $USER1$/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$ -# } - - -# 'check_local_users' command definition -define command{ - command_name check_local_users - command_line $USER1$/check_users -w $ARG1$ -c $ARG2$ - } - - -# 'check_local_swap' command definition -define command{ - command_name check_local_swap - command_line $USER1$/check_swap -w $ARG1$ -c $ARG2$ - } - - -# 'check_local_mrtgtraf' command definition -define command{ - command_name check_local_mrtgtraf - command_line $USER1$/check_mrtgtraf -F $ARG1$ -a $ARG2$ -w $ARG3$ -c $ARG4$ -e $ARG5$ - } - - -################################################################################ -# NOTE: The following 'check_...' commands are used to monitor services on -# both local and remote hosts. -################################################################################ - -# 'check_ftp' command definition -define command{ - command_name check_ftp - command_line $USER1$/check_ftp -H $HOSTADDRESS$ $ARG1$ - } - - -# 'check_hpjd' command definition -define command{ - command_name check_hpjd - command_line $USER1$/check_hpjd -H $HOSTADDRESS$ $ARG1$ - } - - -# 'check_snmp' command definition -define command{ - command_name check_snmp - command_line $USER1$/check_snmp -H $HOSTADDRESS$ $ARG1$ - } - - -# 'check_http' command definition -define command{ - command_name check_http - command_line $USER1$/check_http -I $HOSTADDRESS$ $ARG1$ - } - - -# 'check_ssh' command definition -define command{ - command_name check_ssh - command_line $USER1$/check_ssh $ARG1$ $HOSTADDRESS$ - } - - -# 'check_dhcp' command definition -define command{ - command_name check_dhcp - command_line $USER1$/check_dhcp $ARG1$ - } - - -# 'check_ping' command definition -define command{ - command_name check_ping - command_line $USER1$/check_ping -H $HOSTADDRESS$ -w $ARG1$ -c $ARG2$ -p 5 - } - - -# 'check_pop' command definition -define command{ - command_name check_pop - command_line $USER1$/check_pop -H $HOSTADDRESS$ $ARG1$ - } - - -# 'check_imap' command definition -define command{ - command_name check_imap - command_line $USER1$/check_imap -H $HOSTADDRESS$ $ARG1$ - } - - -# 'check_smtp' command definition -define command{ - command_name check_smtp - command_line $USER1$/check_smtp -H $HOSTADDRESS$ $ARG1$ - } - - -# 'check_tcp' command definition -define command{ - command_name check_tcp - command_line $USER1$/check_tcp -H $HOSTADDRESS$ -p $ARG1$ $ARG2$ - } - - -# 'check_udp' command definition -define command{ - command_name check_udp - command_line $USER1$/check_udp -H $HOSTADDRESS$ -p $ARG1$ $ARG2$ - } - - -# 'check_nt' command definition -define command{ - command_name check_nt - command_line $USER1$/check_nt -H $HOSTADDRESS$ -p 12489 -v $ARG1$ $ARG2$ - } - - -# 'check_dummy' command definition -define command{ - command_name check_dummy - command_line $USER1$/check_dummy $ARG1$ - } - -# 'check_icinga_startup_delay' command definition -define command { - command_name check_icinga_startup_delay - command_line $USER1$/check_dummy 0 "Icinga started with $$(($EVENTSTARTTIME$-$PROCESSSTARTTIME$)) seconds delay | delay=$$(($EVENTSTARTTIME$-$PROCESSSTARTTIME$))" -} - - -################################################################################ -# -# SAMPLE PERFORMANCE DATA COMMANDS -# -# These are sample performance data commands that can be used to send performance -# data output to two text files (one for hosts, another for services). If you -# plan on simply writing performance data out to a file, consider using the -# host_perfdata_file and service_perfdata_file options in the main config file. -# -################################################################################ - - -# 'process-host-perfdata' command definition -define command{ - command_name process-host-perfdata - command_line /usr/bin/printf "%b" "$LASTHOSTCHECK$\t$HOSTNAME$\t$HOSTSTATE$\t$HOSTATTEMPT$\t$HOSTSTATETYPE$\t$HOSTEXECUTIONTIME$\t$HOSTOUTPUT$\t$HOSTPERFDATA$\n" >> /var/host-perfdata.out - } - - -# 'process-service-perfdata' command definition -define command{ - command_name process-service-perfdata - command_line /usr/bin/printf "%b" "$LASTSERVICECHECK$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICESTATE$\t$SERVICEATTEMPT$\t$SERVICESTATETYPE$\t$SERVICEEXECUTIONTIME$\t$SERVICELATENCY$\t$SERVICEOUTPUT$\t$SERVICEPERFDATA$\n" >> /var/service-perfdata.out - } - - diff --git a/package/icinga/src/etc/icinga/objects/contacts.cfg b/package/icinga/src/etc/icinga/objects/contacts.cfg deleted file mode 100644 index 4fda02f83..000000000 --- a/package/icinga/src/etc/icinga/objects/contacts.cfg +++ /dev/null @@ -1,53 +0,0 @@ -############################################################################### -# CONTACTS.CFG - SAMPLE CONTACT/CONTACTGROUP DEFINITIONS -# -# NOTES: This config file provides you with some example contact and contact -# group definitions that you can reference in host and service -# definitions. -# -# You don't need to keep these definitions in a separate file from your -# other object definitions. This has been done just to make things -# easier to understand. -# -############################################################################### - - - -############################################################################### -############################################################################### -# -# CONTACTS -# -############################################################################### -############################################################################### - -# Just one contact defined by default - the Icinga admin (that's you) -# This contact definition inherits a lot of default values from the 'generic-contact' -# template which is defined elsewhere. - -define contact{ - contact_name icingaadmin ; Short name of user - use generic-contact ; Inherit default values from generic-contact template (defined above) - alias Icinga Admin ; Full name of user - - email icinga@localhost ; <<***** CHANGE THIS TO YOUR EMAIL ADDRESS ****** - } - - - -############################################################################### -############################################################################### -# -# CONTACT GROUPS -# -############################################################################### -############################################################################### - -# We only have one contact in this simple configuration file, so there is -# no need to create more than one contact group. - -define contactgroup{ - contactgroup_name admins - alias Icinga Administrators - members icingaadmin - } diff --git a/package/icinga/src/etc/icinga/objects/localhost.cfg b/package/icinga/src/etc/icinga/objects/localhost.cfg deleted file mode 100644 index 9dc4c4da9..000000000 --- a/package/icinga/src/etc/icinga/objects/localhost.cfg +++ /dev/null @@ -1,167 +0,0 @@ -############################################################################### -# LOCALHOST.CFG - SAMPLE OBJECT CONFIG FILE FOR MONITORING THIS MACHINE -# -# NOTE: This config file is intended to serve as an *extremely* simple -# example of how you can create configuration entries to monitor -# the local (Linux) machine. -# -############################################################################### - - - - -############################################################################### -############################################################################### -# -# HOST DEFINITION -# -############################################################################### -############################################################################### - -# Define a host for the local machine - -define host{ - use linux-server ; Name of host template to use - ; This host definition will inherit all variables that are defined - ; in (or inherited by) the linux-server host template definition. - host_name localhost - alias localhost - address 127.0.0.1 - } - - - -############################################################################### -############################################################################### -# -# HOST GROUP DEFINITION -# -############################################################################### -############################################################################### - -# Define an optional hostgroup for Linux machines - -define hostgroup{ - hostgroup_name linux-servers ; The name of the hostgroup - alias Linux Servers ; Long name of the group - members localhost ; Comma separated list of hosts that belong to this group - } - - - -############################################################################### -############################################################################### -# -# SERVICE DEFINITIONS -# -############################################################################### -############################################################################### - - -# Define a service to "ping" the local machine - -define service{ - use local-service ; Name of service template to use - host_name localhost - service_description PING - check_command check_ping!100.0,20%!500.0,60% - } - - -# Define a service to check the disk space of the root partition -# on the local machine. Warning if < 20% free, critical if -# < 10% free space on partition. - -define service{ - use local-service ; Name of service template to use - host_name localhost - service_description Root Partition - check_command check_local_disk!20%!10%!/ - } - - - -# Define a service to check the number of currently logged in -# users on the local machine. Warning if > 20 users, critical -# if > 50 users. - -define service{ - use local-service ; Name of service template to use - host_name localhost - service_description Current Users - check_command check_local_users!20!50 - } - - -# Define a service to check the number of currently running procs -# on the local machine. Warning if > 250 processes, critical if -# > 400 users. - -define service{ - use local-service ; Name of service template to use - host_name localhost - service_description Total Processes - check_command check_local_procs!250!400!RSZDT - } - - - -# Define a service to check the load on the local machine. - -define service{ - use local-service ; Name of service template to use - host_name localhost - service_description Current Load - check_command check_local_load!5.0,4.0,3.0!10.0,6.0,4.0 - } - - - -# Define a service to check the swap usage the local machine. -# Critical if less than 10% of swap is free, warning if less than 20% is free - -define service{ - use local-service ; Name of service template to use - host_name localhost - service_description Swap Usage - check_command check_local_swap!20!10 - } - - - -# Define a service to check SSH on the local machine. -# Disable notifications for this service by default, as not all users may have SSH enabled. - -define service{ - use local-service ; Name of service template to use - host_name localhost - service_description SSH - check_command check_ssh - notifications_enabled 0 - } - - - -# Define a service to check HTTP on the local machine. -# Disable notifications for this service by default, as not all users may have HTTP enabled. - -define service{ - use local-service ; Name of service template to use - host_name localhost - service_description HTTP - check_command check_http - notifications_enabled 0 - } - - -# Define a service to check current startup delay of the Icinga core daemon. -# Disable notifications for this service by default, as no thresholds are defined. - -define service{ - use local-service ; Name of service template to use - host_name localhost - service_description Icinga Startup Delay - check_command check_icinga_startup_delay - notifications_enabled 0 - } - diff --git a/package/icinga/src/etc/icinga/objects/notifications.cfg b/package/icinga/src/etc/icinga/objects/notifications.cfg deleted file mode 100644 index 25819a82b..000000000 --- a/package/icinga/src/etc/icinga/objects/notifications.cfg +++ /dev/null @@ -1,132 +0,0 @@ -############################################################################### -# NOTIFICATIONS.CFG - SAMPLE NOTIFICATION COMMAND DEFINITIONS FOR ICINGA -# -# NOTES: This config file provides you with some example notification definitions -# that you can reference in host, service, and contact definitions. -# -# You don't need to keep commands in a separate file from your other -# object definitions. This has been done just to make things easier to -# understand. -# -# These are some advanced notification commands. They may or may not work on -# your system without modification. As an example, some systems will require -# you to use "/usr/bin/mailx" instead of "/usr/bin/mail" in the commands below. -# -# Furthermore, make sure to replace ICINGAHOST with the appropriate host name -# if used in any notification as url. -# -# Notifications are using the macros quite a lot. Watch out for your own in the -# official docs: http://docs.icinga.org/latest/en/macrolist.html -# -# Those notification commands need to be assigned to the contacts/contactgroups -# as host_notification_commands and service_notification_commands as comma -# separated list. -# -################################################################################ - - -################################################################################ -# NOTIFICATIONS BY EMAIL -# -# The idea is to add more information to the ascii-only email. This includes -# notes_url, display_name, comment+author. -# subject -# $NOTIFICATIONTYPE$ - $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ -# body -# $SHORTDATETIME$ - Info: -# -# $SERVICEOUTPUT$ -# -# $NOTIFICATIONTYPE$ - Service $SERVICEDESC$ on Host $HOSTALIAS$ is $SERVICESTATE$ -# -# (Address: $HOSTADDRESS$, Displayname: $SERVICEDISPLAYNAME$) -# -# Notes: $NOTIFICATIONAUTHOR$ $NOTIFICATIONCOMMENT$ -# $SERVICENOTESURL$ -# -# Url: -# http://ICINGAHOST/icinga/cgi-bin/status.cgi?host=$HOSTNAME$ -################################################################################ - - -# 'notify-host-by-email-advanced' command definition -define command{ - command_name notify-host-by-email-advanced - command_line /usr/bin/printf "%b" "$SHORTDATETIME$ - Info:\n\n$HOSTOUTPUT$\n\n$NOTIFICATIONTYPE$ - Host $HOSTNAME$ is $HOSTSTATE$\n\n(Address: $HOSTADDRESS$ Displayname: $HOSTDISPLAYNAME$)\n\nNotes: $NOTIFICATIONAUTHOR$ $NOTIFICATIONCOMMENT$\n$HOSTNOTESURL$\n\nUrl:\nhttp://ICINGAHOST/icinga/cgi-bin/extinfo.cgi?type=1&host=$HOSTNAME$\n\n" | /usr/bin/mail -s "$NOTIFICATIONTYPE$ - $HOSTNAME$ is $HOSTSTATE$" $CONTACTEMAIL$ - } - -# 'notify-service-by-email-advanced' command definition -define command{ - command_name notify-service-by-email-advanced - command_line /usr/bin/printf "%b" "$SHORTDATETIME$ - Info:\n\n$SERVICEOUTPUT$\n\n$NOTIFICATIONTYPE$ - Service $SERVICEDESC$ on Host $HOSTALIAS$ is $SERVICESTATE$\n\n(Address: $HOSTADDRESS$ Displayname: $SERVICEDISPLAYNAME$)\n\nNotes: $NOTIFICATIONAUTHOR$ $NOTIFICATIONCOMMENT$\n$SERVICENOTESURL$\n\nUrl:\nhttp://ICINGAHOST/icinga/cgi-bin/status.cgi?host=$HOSTNAME$\n\n" | /usr/bin/mail -s "$NOTIFICATIONTYPE$ - $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$" $CONTACTEMAIL$ - } - - -################################################################################ -# NOTIFICATIONS BY JABBER (XMPP) -# -# http://www.gridpp.ac.uk/wiki/Nagios_jabber_notification -# check contrib/notifications/notify_via_jabber for the script and copy it to -# $USER1$ location (check resource.cfg) -# -# Hint: make sure to define 'pager' as contact attribute! Alternatively, replace -# $CONTACTPAGER$ with $CONTACTADDRESS1$ and use 'address1' attribute instead. -################################################################################ - -define command { - command_name notify-service-by-jabber - command_line $USER1$/notify_via_jabber $CONTACTPAGER$ "$SHORTDATETIME$ - Info: $SERVICEOUTPUT$ | $NOTIFICATIONTYPE$ - Service $SERVICEDESC$ on Host $HOSTALIAS$ is $SERVICESTATE$ | (Address: $HOSTADDRESS$ Displayname: $SERVICEDISPLAYNAME$) | Notes: $NOTIFICATIONAUTHOR$ $NOTIFICATIONCOMMENT$ $SERVICENOTESURL$ | Url: http://ICINGAHOST/icinga/cgi-bin/status.cgi?host=$HOSTNAME$" - } - -define command { - command_name notify-host-by-jabber - command_line $USER1$notify_via_jabber $CONTACTPAGER$ "$SHORTDATETIME$ - Info: $HOSTOUTPUT$ | $NOTIFICATIONTYPE$ - Host $HOSTNAME$ is $HOSTSTATE$ | (Address: $HOSTADDRESS$ Displayname: $HOSTDISPLAYNAME$) | Notes: $NOTIFICATIONAUTHOR$ $NOTIFICATIONCOMMENT$ $HOSTNOTESURL$ | Url: http://ICINGAHOST/icinga/cgi-bin/extinfo.cgi?type=1&host=$HOSTNAME$" - } - - -################################################################################ -# NOTIFICATIONS BY TWITTER -# -# https://wiki.icinga.org/display/howtos/notify+via+Twitter -################################################################################ - -define command { - command_name notify-host-by-twitter - command_line $USER1$/eventhandler_twitter.php -t "HOST" -h "$HOSTALIAS$" -s "$HOSTSTATE$" -o "$HOSTOUTPUT$" -} - -define command { - command_name notify-service-by-twitter - command_line $USER1$/eventhandler_twitter.php -t "SERVICE" -h "$HOSTALIAS$" -s "$SERVICESTATE$" -d "$SERVICEDESC$" -o "$SERVICEOUTPUT$" -} - - -################################################################################ -# NOTIFICATIONS BY SMS -# -# First off, you need either a local sms service, or an sms gateway. Besides -# an applicable plugin interacting the that api and integrated as notification -# command. Below is only the command example. -################################################################################ - - -define command { - command_name notify-host-by-sms - command_line /usr/bin/printf "%b" "$NOTIFICATIONTYPE$ - $HOSTNAME$ is $HOSTSTATE$ $SHORTDATETIME$ - Info:\n\n$HOSTOUTPUT$\n\n($HOSTADDRESS$)" | $USER1$/notify_via_sms $CONTACTPAGER$ - } - - -define command { - command_name notify-service-by-sms - command_line /usr/bin/printf "%b" "$NOTIFICATIONTYPE$ - $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$ $SHORTDATETIME$ - Info:\n\n$SERVICEOUTPUT$\n\n($HOSTADDRESS$)" | $USER1$/notify_via_sms $CONTACTPAGER$ - } - - - -################################################################################ -# MORE NOTIFICATION POSSIBILITIES -# -# NoMa: https://www.netways.org/projects/noma/ -# IRCBot: http://www.vanheusden.com/nagircbot/ -################################################################################ - diff --git a/package/icinga/src/etc/icinga/objects/printer.cfg b/package/icinga/src/etc/icinga/objects/printer.cfg deleted file mode 100644 index 815b55fdb..000000000 --- a/package/icinga/src/etc/icinga/objects/printer.cfg +++ /dev/null @@ -1,83 +0,0 @@ -############################################################################### -# PRINTER.CFG - SAMPLE CONFIG FILE FOR MONITORING A NETWORK PRINTER -# -# NOTES: This config file assumes that you are using the sample configuration -# files that get installed with the Icinga quickstart guide. -# -############################################################################### - - - - -############################################################################### -############################################################################### -# -# HOST DEFINITIONS -# -############################################################################### -############################################################################### - -# Define a host for the printer we'll be monitoring -# Change the host_name, alias, and address to fit your situation - -define host{ - use generic-printer ; Inherit default values from a template - host_name hplj2605dn ; The name we're giving to this printer - alias HP LaserJet 2605dn ; A longer name associated with the printer - address 192.168.1.30 ; IP address of the printer - hostgroups network-printers ; Host groups this printer is associated with - } - - - - -############################################################################### -############################################################################### -# -# HOST GROUP DEFINITIONS -# -############################################################################### -############################################################################### - -# A hostgroup for network printers - -define hostgroup{ - hostgroup_name network-printers ; The name of the hostgroup - alias Network Printers ; Long name of the group - } - - - - -############################################################################### -############################################################################### -# -# SERVICE DEFINITIONS -# -############################################################################### -############################################################################### - -# Create a service for monitoring the status of the printer -# Change the host_name to match the name of the host you defined above -# If the printer has an SNMP community string other than "public", change the check_command directive to reflect that - -define service{ - use generic-service ; Inherit values from a template - host_name hplj2605dn ; The name of the host the service is associated with - service_description Printer Status ; The service description - check_command check_hpjd!-C public ; The command used to monitor the service - normal_check_interval 10 ; Check the service every 10 minutes under normal conditions - retry_check_interval 1 ; Re-check the service every minute until its final/hard state is determined - } - - -# Create a service for "pinging" the printer occassionally. Useful for monitoring RTA, packet loss, etc. - -define service{ - use generic-service - host_name hplj2605dn - service_description PING - check_command check_ping!3000.0,80%!5000.0,100% - normal_check_interval 10 - retry_check_interval 1 - } diff --git a/package/icinga/src/etc/icinga/objects/switch.cfg b/package/icinga/src/etc/icinga/objects/switch.cfg deleted file mode 100644 index d19aaedb2..000000000 --- a/package/icinga/src/etc/icinga/objects/switch.cfg +++ /dev/null @@ -1,111 +0,0 @@ -############################################################################### -# SWITCH.CFG - SAMPLE CONFIG FILE FOR MONITORING A SWITCH -# -# NOTES: This config file assumes that you are using the sample configuration -# files that get installed with the Icinga quickstart guide. -# -############################################################################### - - - - -############################################################################### -############################################################################### -# -# HOST DEFINITIONS -# -############################################################################### -############################################################################### - -# Define the switch that we'll be monitoring - -define host{ - use generic-switch ; Inherit default values from a template - host_name linksys-srw224p ; The name we're giving to this switch - alias Linksys SRW224P Switch ; A longer name associated with the switch - address 192.168.1.253 ; IP address of the switch - hostgroups switches ; Host groups this switch is associated with - } - - - - -############################################################################### -############################################################################### -# -# HOST GROUP DEFINITIONS -# -############################################################################### -############################################################################### - -# Create a new hostgroup for switches - -define hostgroup{ - hostgroup_name switches ; The name of the hostgroup - alias Network Switches ; Long name of the group - } - - - - -############################################################################### -############################################################################### -# -# SERVICE DEFINITIONS -# -############################################################################### -############################################################################### - -# Create a service to PING to switch - -define service{ - use generic-service ; Inherit values from a template - host_name linksys-srw224p ; The name of the host the service is associated with - service_description PING ; The service description - check_command check_ping!200.0,20%!600.0,60% ; The command used to monitor the service - normal_check_interval 5 ; Check the service every 5 minutes under normal conditions - retry_check_interval 1 ; Re-check the service every minute until its final/hard state is determined - } - - -# Monitor uptime via SNMP - -define service{ - use generic-service ; Inherit values from a template - host_name linksys-srw224p - service_description Uptime - check_command check_snmp!-C public -o sysUpTime.0 - } - - - -# Monitor Port 1 status via SNMP - -define service{ - use generic-service ; Inherit values from a template - host_name linksys-srw224p - service_description Port 1 Link Status - check_command check_snmp!-C public -o ifOperStatus.1 -r 1 -m RFC1213-MIB - } - - - -# Monitor bandwidth via MRTG logs - -define service{ - use generic-service ; Inherit values from a template - host_name linksys-srw224p - service_description Port 1 Bandwidth Usage - check_command check_local_mrtgtraf!/var/lib/mrtg/192.168.1.253_1.log!AVG!1000000,1000000!5000000,5000000!10 - } - - - - - - - - - - - diff --git a/package/icinga/src/etc/icinga/objects/templates.cfg b/package/icinga/src/etc/icinga/objects/templates.cfg deleted file mode 100644 index 68c32336f..000000000 --- a/package/icinga/src/etc/icinga/objects/templates.cfg +++ /dev/null @@ -1,188 +0,0 @@ -############################################################################### -# TEMPLATES.CFG - SAMPLE OBJECT TEMPLATES -# -# NOTES: This config file provides you with some example object definition -# templates that are refered by other host, service, contact, etc. -# definitions in other config files. -# -# You don't need to keep these definitions in a separate file from your -# other object definitions. This has been done just to make things -# easier to understand. -# -############################################################################### - - - -############################################################################### -############################################################################### -# -# CONTACT TEMPLATES -# -############################################################################### -############################################################################### - -# Generic contact definition template - This is NOT a real contact, just a template! - -define contact{ - name generic-contact ; The name of this contact template - service_notification_period 24x7 ; service notifications can be sent anytime - host_notification_period 24x7 ; host notifications can be sent anytime - service_notification_options w,u,c,r,f,s ; send notifications for all service states, flapping events, and scheduled downtime events - host_notification_options d,u,r,f,s ; send notifications for all host states, flapping events, and scheduled downtime events - service_notification_commands notify-service-by-email ; send service notifications via email - host_notification_commands notify-host-by-email ; send host notifications via email - register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL CONTACT, JUST A TEMPLATE! - } - - - - -############################################################################### -############################################################################### -# -# HOST TEMPLATES -# -############################################################################### -############################################################################### - -# Generic host definition template - This is NOT a real host, just a template! - -define host{ - name generic-host ; The name of this host template - notifications_enabled 1 ; Host notifications are enabled - event_handler_enabled 1 ; Host event handler is enabled - flap_detection_enabled 1 ; Flap detection is enabled - failure_prediction_enabled 1 ; Failure prediction is enabled - process_perf_data 1 ; Process performance data - retain_status_information 1 ; Retain status information across program restarts - retain_nonstatus_information 1 ; Retain non-status information across program restarts - notification_period 24x7 ; Send host notifications at any time - register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE! - } - - -# Linux host definition template - This is NOT a real host, just a template! - -define host{ - name linux-server ; The name of this host template - use generic-host ; This template inherits other values from the generic-host template - check_period 24x7 ; By default, Linux hosts are checked round the clock - check_interval 5 ; Actively check the host every 5 minutes - retry_interval 1 ; Schedule host check retries at 1 minute intervals - max_check_attempts 10 ; Check each Linux host 10 times (max) - check_command check-host-alive ; Default command to check Linux hosts - notification_period workhours ; Linux admins hate to be woken up, so we only notify during the day - ; Note that the notification_period variable is being overridden from - ; the value that is inherited from the generic-host template! - notification_interval 120 ; Resend notifications every 2 hours - notification_options d,u,r ; Only send notifications for specific host states - contact_groups admins ; Notifications get sent to the admins by default - register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE! - } - - - -# Windows host definition template - This is NOT a real host, just a template! - -define host{ - name windows-server ; The name of this host template - use generic-host ; Inherit default values from the generic-host template - check_period 24x7 ; By default, Windows servers are monitored round the clock - check_interval 5 ; Actively check the server every 5 minutes - retry_interval 1 ; Schedule host check retries at 1 minute intervals - max_check_attempts 10 ; Check each server 10 times (max) - check_command check-host-alive ; Default command to check if servers are "alive" - notification_period 24x7 ; Send notification out at any time - day or night - notification_interval 30 ; Resend notifications every 30 minutes - notification_options d,r ; Only send notifications for specific host states - contact_groups admins ; Notifications get sent to the admins by default - hostgroups windows-servers ; Host groups that Windows servers should be a member of - register 0 ; DONT REGISTER THIS - ITS JUST A TEMPLATE - } - - -# We define a generic printer template that can be used for most printers we monitor - -define host{ - name generic-printer ; The name of this host template - use generic-host ; Inherit default values from the generic-host template - check_period 24x7 ; By default, printers are monitored round the clock - check_interval 5 ; Actively check the printer every 5 minutes - retry_interval 1 ; Schedule host check retries at 1 minute intervals - max_check_attempts 10 ; Check each printer 10 times (max) - check_command check-host-alive ; Default command to check if printers are "alive" - notification_period workhours ; Printers are only used during the workday - notification_interval 30 ; Resend notifications every 30 minutes - notification_options d,r ; Only send notifications for specific host states - contact_groups admins ; Notifications get sent to the admins by default - register 0 ; DONT REGISTER THIS - ITS JUST A TEMPLATE - } - - -# Define a template for switches that we can reuse -define host{ - name generic-switch ; The name of this host template - use generic-host ; Inherit default values from the generic-host template - check_period 24x7 ; By default, switches are monitored round the clock - check_interval 5 ; Switches are checked every 5 minutes - retry_interval 1 ; Schedule host check retries at 1 minute intervals - max_check_attempts 10 ; Check each switch 10 times (max) - check_command check-host-alive ; Default command to check if routers are "alive" - notification_period 24x7 ; Send notifications at any time - notification_interval 30 ; Resend notifications every 30 minutes - notification_options d,r ; Only send notifications for specific host states - contact_groups admins ; Notifications get sent to the admins by default - register 0 ; DONT REGISTER THIS - ITS JUST A TEMPLATE - } - - - - -############################################################################### -############################################################################### -# -# SERVICE TEMPLATES -# -############################################################################### -############################################################################### - -# Generic service definition template - This is NOT a real service, just a template! - -define service{ - name generic-service ; The 'name' of this service template - active_checks_enabled 1 ; Active service checks are enabled - passive_checks_enabled 1 ; Passive service checks are enabled/accepted - parallelize_check 1 ; Active service checks should be parallelized (disabling this can lead to major performance problems) - obsess_over_service 1 ; We should obsess over this service (if necessary) - check_freshness 0 ; Default is to NOT check service 'freshness' - notifications_enabled 1 ; Service notifications are enabled - event_handler_enabled 1 ; Service event handler is enabled - flap_detection_enabled 1 ; Flap detection is enabled - failure_prediction_enabled 1 ; Failure prediction is enabled - process_perf_data 1 ; Process performance data - retain_status_information 1 ; Retain status information across program restarts - retain_nonstatus_information 1 ; Retain non-status information across program restarts - is_volatile 0 ; The service is not volatile - check_period 24x7 ; The service can be checked at any time of the day - max_check_attempts 3 ; Re-check the service up to 3 times in order to determine its final (hard) state - normal_check_interval 10 ; Check the service every 10 minutes under normal conditions - retry_check_interval 2 ; Re-check the service every two minutes until a hard state can be determined - contact_groups admins ; Notifications get sent out to everyone in the 'admins' group - notification_options w,u,c,r ; Send notifications about warning, unknown, critical, and recovery events - notification_interval 60 ; Re-notify about service problems every hour - notification_period 24x7 ; Notifications can be sent out at any time - register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE! - } - - -# Local service definition template - This is NOT a real service, just a template! - -define service{ - name local-service ; The name of this service template - use generic-service ; Inherit default values from the generic-service definition - max_check_attempts 4 ; Re-check the service up to 4 times in order to determine its final (hard) state - normal_check_interval 5 ; Check the service every 5 minutes under normal conditions - retry_check_interval 1 ; Re-check the service every minute until a hard state can be determined - register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE! - } - diff --git a/package/icinga/src/etc/icinga/objects/timeperiods.cfg b/package/icinga/src/etc/icinga/objects/timeperiods.cfg deleted file mode 100644 index 35e862768..000000000 --- a/package/icinga/src/etc/icinga/objects/timeperiods.cfg +++ /dev/null @@ -1,92 +0,0 @@ -############################################################################### -# TIMEPERIODS.CFG - SAMPLE TIMEPERIOD DEFINITIONS -# -# NOTES: This config file provides you with some example timeperiod definitions -# that you can reference in host, service, contact, and dependency -# definitions. -# -# You don't need to keep timeperiods in a separate file from your other -# object definitions. This has been done just to make things easier to -# understand. -# -############################################################################### - - - -############################################################################### -############################################################################### -# -# TIME PERIODS -# -############################################################################### -############################################################################### - -# This defines a timeperiod where all times are valid for checks, -# notifications, etc. The classic "24x7" support nightmare. :-) -define timeperiod{ - timeperiod_name 24x7 - alias 24 Hours A Day, 7 Days A Week - sunday 00:00-24:00 - monday 00:00-24:00 - tuesday 00:00-24:00 - wednesday 00:00-24:00 - thursday 00:00-24:00 - friday 00:00-24:00 - saturday 00:00-24:00 - } - - -# 'workhours' timeperiod definition -define timeperiod{ - timeperiod_name workhours - alias Normal Work Hours - monday 09:00-17:00 - tuesday 09:00-17:00 - wednesday 09:00-17:00 - thursday 09:00-17:00 - friday 09:00-17:00 - } - - -# 'none' timeperiod definition -define timeperiod{ - timeperiod_name none - alias No Time Is A Good Time - } - - -# Some U.S. holidays -# Note: The timeranges for each holiday are meant to *exclude* the holidays from being -# treated as a valid time for notifications, etc. You probably don't want your pager -# going off on New Year's. Although you're employer might... :-) -define timeperiod{ - name us-holidays - timeperiod_name us-holidays - alias U.S. Holidays - - january 1 00:00-00:00 ; New Years - monday -1 may 00:00-00:00 ; Memorial Day (last Monday in May) - july 4 00:00-00:00 ; Independence Day - monday 1 september 00:00-00:00 ; Labor Day (first Monday in September) - thursday 4 november 00:00-00:00 ; Thanksgiving (4th Thursday in November) - december 25 00:00-00:00 ; Christmas - } - - -# This defines a modified "24x7" timeperiod that covers every day of the -# year, except for U.S. holidays (defined in the timeperiod above). -define timeperiod{ - timeperiod_name 24x7_sans_holidays - alias 24x7 Sans Holidays - - use us-holidays ; Get holiday exceptions from other timeperiod - - sunday 00:00-24:00 - monday 00:00-24:00 - tuesday 00:00-24:00 - wednesday 00:00-24:00 - thursday 00:00-24:00 - friday 00:00-24:00 - saturday 00:00-24:00 - } - diff --git a/package/icinga/src/etc/icinga/objects/windows.cfg b/package/icinga/src/etc/icinga/objects/windows.cfg deleted file mode 100644 index c3b917852..000000000 --- a/package/icinga/src/etc/icinga/objects/windows.cfg +++ /dev/null @@ -1,143 +0,0 @@ -############################################################################### -# WINDOWS.CFG - SAMPLE CONFIG FILE FOR MONITORING A WINDOWS MACHINE -# -# NOTES: This config file assumes that you are using the sample configuration -# files that get installed with the Icinga quickstart guide. -# -############################################################################### - - - - -############################################################################### -############################################################################### -# -# HOST DEFINITIONS -# -############################################################################### -############################################################################### - -# Define a host for the Windows machine we'll be monitoring -# Change the host_name, alias, and address to fit your situation - -define host{ - use windows-server ; Inherit default values from a template - host_name winserver ; The name we're giving to this host - alias My Windows Server ; A longer name associated with the host - address 192.168.1.2 ; IP address of the host - } - - - - -############################################################################### -############################################################################### -# -# HOST GROUP DEFINITIONS -# -############################################################################### -############################################################################### - - -# Define a hostgroup for Windows machines -# All hosts that use the windows-server template will automatically be a member of this group - -define hostgroup{ - hostgroup_name windows-servers ; The name of the hostgroup - alias Windows Servers ; Long name of the group - } - - - - -############################################################################### -############################################################################### -# -# SERVICE DEFINITIONS -# -############################################################################### -############################################################################### - - -# Create a service for monitoring the version of NSCLient++ that is installed -# Change the host_name to match the name of the host you defined above - -define service{ - use generic-service - host_name winserver - service_description NSClient++ Version - check_command check_nt!CLIENTVERSION - } - - - -# Create a service for monitoring the uptime of the server -# Change the host_name to match the name of the host you defined above - -define service{ - use generic-service - host_name winserver - service_description Uptime - check_command check_nt!UPTIME - } - - - -# Create a service for monitoring CPU load -# Change the host_name to match the name of the host you defined above - -define service{ - use generic-service - host_name winserver - service_description CPU Load - check_command check_nt!CPULOAD!-l 5,80,90 - } - - - -# Create a service for monitoring memory usage -# Change the host_name to match the name of the host you defined above - -define service{ - use generic-service - host_name winserver - service_description Memory Usage - check_command check_nt!MEMUSE!-w 80 -c 90 - } - - - -# Create a service for monitoring C:\ disk usage -# Change the host_name to match the name of the host you defined above - -define service{ - use generic-service - host_name winserver - service_description C:\ Drive Space - check_command check_nt!USEDDISKSPACE!-l c -w 80 -c 90 - } - - - -# Create a service for monitoring the W3SVC service -# Change the host_name to match the name of the host you defined above - -define service{ - use generic-service - host_name winserver - service_description W3SVC - check_command check_nt!SERVICESTATE!-d SHOWALL -l W3SVC - } - - - -# Create a service for monitoring the Explorer.exe process -# Change the host_name to match the name of the host you defined above - -define service{ - use generic-service - host_name winserver - service_description Explorer - check_command check_nt!PROCSTATE!-d SHOWALL -l Explorer.exe - } - diff --git a/package/icinga/src/etc/icinga/resource.cfg b/package/icinga/src/etc/icinga/resource.cfg deleted file mode 100644 index d8f3e1473..000000000 --- a/package/icinga/src/etc/icinga/resource.cfg +++ /dev/null @@ -1,32 +0,0 @@ -########################################################################### -# -# RESOURCE.CFG - Sample Resource File for Icinga -# -# You can define $USERx$ macros in this file, which can in turn be used -# in command definitions in your host config file(s). $USERx$ macros are -# useful for storing sensitive information such as usernames, passwords, -# etc. They are also handy for specifying the path to plugins and -# event handlers - if you decide to move the plugins or event handlers to -# a different directory in the future, you can just update one or two -# $USERx$ macros, instead of modifying a lot of command definitions. -# -# The CGIs will not attempt to read the contents of resource files, so -# you can set restrictive permissions (600 or 660) on them. -# -# Icinga supports up to 32 $USERx$ macros ($USER1$ through $USER32$) -# -# Resource files may also be used to store configuration directives for -# external data sources like MySQL... -# -########################################################################### - -# Sets $USER1$ to be the path to the plugins -$USER1$=/usr/libexec - -# Sets $USER2$ to be the path to event handlers -#$USER2$=/usr/libexec/eventhandlers - -# Store some usernames and passwords (hidden from the CGIs) -#$USER3$=someuser -#$USER4$=somepassword - |