From 68e454488b10cc9e7d5b809909fcfbc9e338acfa Mon Sep 17 00:00:00 2001 From: Alex Dehnert Date: Sat, 27 May 2023 06:35:33 +0000 Subject: [PATCH] More nagios4 updates --- cgi.cfg | 154 +++++++----- commands.cfg | 58 ----- conf.d/contacts_nagios2.cfg | 46 ---- conf.d/generic-host_nagios2.cfg | 19 -- conf.d/generic-service_nagios2.cfg | 29 --- conf.d/host-gateway_nagios3.cfg | 2 +- conf.d/localhost_nagios2.cfg | 59 ----- conf.d/nrpe.cfg | 1 + conf.d/services_nagios2.cfg | 26 --- conf.d/timeperiods_nagios2.cfg | 50 ---- local.d/adehnert-host.cfg | 1 + local.d/virunga.cfg | 2 +- nagios.cfg | 360 ++++++++++++++++------------- objects/commands.cfg | 6 + objects/contacts.cfg | 11 +- 15 files changed, 310 insertions(+), 514 deletions(-) delete mode 100644 commands.cfg delete mode 100644 conf.d/contacts_nagios2.cfg delete mode 100644 conf.d/generic-host_nagios2.cfg delete mode 100644 conf.d/generic-service_nagios2.cfg delete mode 100644 conf.d/localhost_nagios2.cfg delete mode 100644 conf.d/services_nagios2.cfg delete mode 100644 conf.d/timeperiods_nagios2.cfg diff --git a/cgi.cfg b/cgi.cfg index 1d6cc30..cd540b5 100644 --- a/cgi.cfg +++ b/cgi.cfg @@ -1,6 +1,7 @@ ################################################################# # -# CGI.CFG - Sample CGI Configuration File for Nagios +# CGI.CFG - Sample CGI Configuration File for Nagios +# # ################################################################# @@ -10,7 +11,7 @@ # The CGIs will read the main and host config files for any other # data they might need. -main_config_file=/etc/nagios3/nagios.cfg +main_config_file=/etc/nagios4/nagios.cfg @@ -19,7 +20,7 @@ main_config_file=/etc/nagios3/nagios.cfg # value is used to locate the logo images needed by the statusmap # and statuswrl CGIs. -physical_html_path=/usr/share/nagios3/htdocs +physical_html_path=/usr/share/nagios4/htdocs @@ -31,7 +32,7 @@ physical_html_path=/usr/share/nagios3/htdocs # http://www.myhost.com/nagios, this value should be '/nagios' # (without the quotes). -url_html_path=/nagios3 +url_html_path=/nagios4 @@ -53,28 +54,12 @@ show_context_help=1 use_pending_states=1 -# NAGIOS PROCESS CHECK COMMAND -# This is the full path and filename of the program used to check -# the status of the Nagios process. It is used only by the CGIs -# and is completely optional. However, if you don't use it, you'll -# see warning messages in the CGIs about the Nagios process -# not running and you won't be able to execute any commands from -# the web interface. The program should follow the same rules -# as plugins; the return codes are the same as for the plugins, -# it should have timeout protection, it should output something -# to STDIO, etc. -# -# Note: The command line for the check_nagios plugin below may -# have to be tweaked a bit, as different versions of the plugin -# use different command line arguments/syntaxes. - -nagios_check_command=/usr/lib/nagios/plugins/check_nagios /var/cache/nagios3/status.dat 5 '/usr/sbin/nagios3' # AUTHENTICATION USAGE -# This option controls whether or not the CGIs will use any +# This option controls whether or not the CGIs will use any # authentication when displaying host and service information, as -# well as committing commands to Nagios for processing. +# well as committing commands to Nagios for processing. # # Read the HTML documentation to learn how the authorization works! # @@ -102,7 +87,6 @@ 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 @@ -116,7 +100,7 @@ use_ssl_authentication=0 # 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 @@ -166,7 +150,6 @@ authorized_for_system_commands=nagiosadmin # you choose to not use authorization). You may use an asterisk (*) # to authorize any user who has authenticated to the web server. - authorized_for_all_services=nagiosadmin authorized_for_all_hosts=nagiosadmin @@ -175,9 +158,9 @@ authorized_for_all_hosts=nagiosadmin # 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 +# 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. @@ -196,27 +179,25 @@ authorized_for_all_host_commands=nagiosadmin - # STATUSMAP BACKGROUND IMAGE -# This option allows you to specify an image to be used as a +# 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/nagios/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. +# (uncompressed) but ONLY IF YOU WILL USE THE LEGACY MAP EXCLUSIVELY, +# 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). +# a background color instead (to make it look pretty). # Defaults to white: (R,G,B) = (255,255,255). #color_transparency_index_r=255 @@ -225,20 +206,33 @@ authorized_for_all_host_commands=nagiosadmin - # 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: +# not use this option, the default for the legacy map is to use +# user-defined coordinates and the default for the new map is "6" +# (Circular Balloon). +# Valid options for the legacy map are as follows: # 0 = User-defined coordinates # 1 = Depth layers -# 2 = Collapsed tree -# 3 = Balanced tree -# 4 = Circular -# 5 = Circular (Marked Up) +# 2 = Collapsed tree +# 3 = Balanced tree +# 4 = Circular +# 5 = Circular (Marked Up) +# Valid options for the new map are as follows: +# 0 = User-defined coordinates +# 1 = Depth Layers (Horizontal) +# 2 = Collapsed tree (Horizontal) +# 3 = Balanced tree (Horizontal) +# 4 = DON'T USE +# 5 = Circular Markup +# 6 = Circular Balloon +# 7 = Balanced tree (Vertical) +# 8 = Collapsed tree (Vertical) +# 9 = Depth Layers (Vertical) +# 10 = Force Map -default_statusmap_layout=5 +#default_statusmap_layout=6 @@ -257,7 +251,7 @@ default_statuswrl_layout=4 # STATUSWRL INCLUDE -# This option allows you to include your own objects in the +# 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/nagios/share). @@ -283,19 +277,29 @@ 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). +# of various CGIs (status, statusmap, extinfo, and outages). refresh_rate=90 + + +# PAGE TOUR +# Enable page tour for helpful tips and tricks on various pages + +#enable_page_tour=1 + + + # DEFAULT PAGE LIMIT -# This option allows you to specify the default number of results +# This option allows you to specify the default number of results # displayed on the status.cgi. This number can be adjusted from # within the UI after the initial page load. Setting this to 0 -# will show all results. +# will show all results. result_limit=100 + # ESCAPE HTML TAGS # This option determines whether HTML tags in host and service # status output is escaped in the web interface. If enabled, @@ -305,7 +309,6 @@ escape_html_tags=1 - # SOUND OPTIONS # These options allow you to specify an optional audio file # that should be played in your browser window when there are @@ -333,7 +336,7 @@ escape_html_tags=1 # URL TARGET FRAMES -# These options determine the target frames in which notes and +# These options determine the target frames in which notes and # action URLs will open. action_url_target=_blank @@ -341,10 +344,9 @@ 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 +# This option determines whether users can change the author name +# when submitting comments, scheduling downtime. If disabled, the # author names will be locked into their contact name, as defined in Nagios. # Values: 0 = allow editing author names # 1 = lock author names (disallow editing) @@ -353,7 +355,6 @@ lock_author_names=1 - # SPLUNK INTEGRATION OPTIONS # These options allow you to enable integration with Splunk # in the web interface. If enabled, you'll be presented with @@ -368,10 +369,55 @@ lock_author_names=1 #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/ +# NAVIGATION BAR SEARCH OPTIONS +# The following options allow to configure the navbar search. Default +# is to search for hostnames. With enabled navbar_search_for_addresses, +# the navbar search queries IP addresses as well. It's also possible +# to enable search for aliases by setting navbar_search_for_aliases=1. + +navbar_search_for_addresses=1 +navbar_search_for_aliases=1 + + + +# DEFAULTS FOR CHECKBOXES FOR ACKNOWLEDGEMENTS +# Enabling ack_no_sticky will default the "Sticky Acknowledgement" to +# be unchecked. +# Enabling ack_no_send will default the "Send Notification" to +# be unchecked. + +#ack_no_sticky=0 +#ack_no_send=0 + + + +# SHOW ONLY HARD STATES IS TACTICAL OVERVIEW +# This option controls whether only HARD states are counted on the +# Tactical Overview, or if both HARD and SOFT states are counted. +# Set to 1 to show only HARD states. Defaults to 0 (HARD+SOFT). + +#tac_cgi_hard_only=0 + + + +# COMMAND COMMENTS +# These options control whether or not comments are required, optional, +# or not allowed for specific commands. The format for each line is: +# cmd-name=req,def-comment +# +# cmd-name is "CMT_" plus a command such as ADD_HOST_COMMENT +# req 0 = not allowed, 1 = optional, 2 = required +# def-comment optional default comment that will be put in the input field +# +# The following examples override the default comment requirements in +# some way. + +#CMT_ADD_HOST_COMMENT=1 +#CMT_ACKNOWLEDGE_HOST_PROBLEM=2,"Problem is being looked into" +#CMT_SCHEDULE_SVC_CHECK=1 +#CMT_SCHEDULE_HOST_DOWNTIME=0 diff --git a/commands.cfg b/commands.cfg deleted file mode 100644 index 8726eba..0000000 --- a/commands.cfg +++ /dev/null @@ -1,58 +0,0 @@ -############################################################################### -# COMMANDS.CFG - SAMPLE COMMAND DEFINITIONS FOR NAGIOS -############################################################################### - - -################################################################################ -# NOTIFICATION COMMANDS -################################################################################ - - -# 'notify-host-by-email' command definition -define command{ - command_name notify-host-by-email - command_line /usr/bin/printf "%b" "***** Nagios *****\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" "***** Nagios *****\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$ - } - - - - - -################################################################################ -# HOST CHECK COMMANDS -################################################################################ - -# On Debian, check-host-alive is being defined from within the -# nagios-plugins-basic package - -################################################################################ -# PERFORMANCE DATA COMMANDS -################################################################################ - - -# '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/lib/nagios3/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/lib/nagios3/service-perfdata.out - } - - -define command{ - command_name check_jabber - # Sadly, check_tcp.c / check_jabber has no starttls support, so we can't check the cert - command_line /usr/lib/nagios/plugins/check_jabber -H '$HOSTADDRESS$' - } - diff --git a/conf.d/contacts_nagios2.cfg b/conf.d/contacts_nagios2.cfg deleted file mode 100644 index 8fb38df..0000000 --- a/conf.d/contacts_nagios2.cfg +++ /dev/null @@ -1,46 +0,0 @@ -############################################################################### -# contacts.cfg -############################################################################### - - - -############################################################################### -############################################################################### -# -# CONTACTS -# -############################################################################### -############################################################################### - -# In this simple config file, a single contact will receive all alerts. - -define contact{ - contact_name root - alias Root - service_notification_period 24x7 - host_notification_period 24x7 - service_notification_options w,u,c,r - host_notification_options d,r - service_notification_commands notify-service-by-email - host_notification_commands notify-host-by-email - email root@localhost - } - - - -############################################################################### -############################################################################### -# -# 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 Nagios Administrators - members adehnert-pub-zephyr - } diff --git a/conf.d/generic-host_nagios2.cfg b/conf.d/generic-host_nagios2.cfg deleted file mode 100644 index e6d96ac..0000000 --- a/conf.d/generic-host_nagios2.cfg +++ /dev/null @@ -1,19 +0,0 @@ -# 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 - check_command check-host-alive - max_check_attempts 10 - notification_interval 0 - notification_period 24x7 - notification_options d,u,r - contact_groups admins - register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE! - } diff --git a/conf.d/generic-service_nagios2.cfg b/conf.d/generic-service_nagios2.cfg deleted file mode 100644 index a46cfcb..0000000 --- a/conf.d/generic-service_nagios2.cfg +++ /dev/null @@ -1,29 +0,0 @@ -# generic service template definition -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 - notification_interval 0 ; Only send notifications on status change by default. - is_volatile 0 - check_period 24x7 - normal_check_interval 2 - retry_check_interval 1 - max_check_attempts 4 - notification_period 24x7 - notification_options w,u,c,r - contact_groups admins - - __CHECK_CERT_EXPIRY_DAYS 14 - - register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE! - } diff --git a/conf.d/host-gateway_nagios3.cfg b/conf.d/host-gateway_nagios3.cfg index ba2c352..f541049 100644 --- a/conf.d/host-gateway_nagios3.cfg +++ b/conf.d/host-gateway_nagios3.cfg @@ -3,5 +3,5 @@ define host { host_name gateway alias Default Gateway address 18.18.208.1 - use generic-host + use generic-switch } diff --git a/conf.d/localhost_nagios2.cfg b/conf.d/localhost_nagios2.cfg deleted file mode 100644 index 27dbb4b..0000000 --- a/conf.d/localhost_nagios2.cfg +++ /dev/null @@ -1,59 +0,0 @@ -# A simple configuration file for monitoring the local host -# This can serve as an example for configuring other servers; -# Custom services specific to this host are added here, but services -# defined in nagios2-common_services.cfg may also apply. -# - -define host{ - use generic-host ; Name of host template to use - host_name localhost - alias localhost - address 127.0.0.1 - } - -# 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 generic-service ; Name of service template to use - host_name localhost - service_description Disk Space - check_command check_all_disks!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 generic-service ; Name of service template to use - host_name localhost - service_description Current Users - check_command check_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 processes. - -define service{ - use generic-service ; Name of service template to use - host_name localhost - service_description Total Processes - check_command check_procs!250!400 - } - - - -# Define a service to check the load on the local machine. - -define service{ - use generic-service ; Name of service template to use - host_name localhost - service_description Current Load - check_command check_load!5.0!4.0!3.0!10.0!6.0!4.0 - } diff --git a/conf.d/nrpe.cfg b/conf.d/nrpe.cfg index a7123b0..a2d58d8 100644 --- a/conf.d/nrpe.cfg +++ b/conf.d/nrpe.cfg @@ -6,6 +6,7 @@ define hostgroup { define service { name nrpe-service use generic-service + register 0 } define service { diff --git a/conf.d/services_nagios2.cfg b/conf.d/services_nagios2.cfg deleted file mode 100644 index af3d4fe..0000000 --- a/conf.d/services_nagios2.cfg +++ /dev/null @@ -1,26 +0,0 @@ -# check that web services are running -define service { - hostgroup_name http-servers - service_description HTTP - check_command check_http - use generic-service - notification_interval 0 ; set > 0 if you want to be renotified -} - -# check that ssh services are running -define service { - hostgroup_name ssh-servers - service_description SSH - check_command check_ssh - use generic-service - notification_interval 0 ; set > 0 if you want to be renotified -} - -# check that ping-only hosts are up -define service { - hostgroup_name ping-servers - service_description PING - check_command check_ping!100.0,20%!500.0,60% - use generic-service - notification_interval 0 ; set > 0 if you want to be renotified -} diff --git a/conf.d/timeperiods_nagios2.cfg b/conf.d/timeperiods_nagios2.cfg deleted file mode 100644 index 55ecf9d..0000000 --- a/conf.d/timeperiods_nagios2.cfg +++ /dev/null @@ -1,50 +0,0 @@ -############################################################################### -# timeperiods.cfg -############################################################################### - -# 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 - } - -# Here is a slightly friendlier period during work hours -define timeperiod{ - timeperiod_name workhours - alias Standard 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 - } - -# The complement of workhours -define timeperiod{ - timeperiod_name nonworkhours - alias Non-Work Hours - sunday 00:00-24:00 - monday 00:00-09:00,17:00-24:00 - tuesday 00:00-09:00,17:00-24:00 - wednesday 00:00-09:00,17:00-24:00 - thursday 00:00-09:00,17:00-24:00 - friday 00:00-09:00,17:00-24:00 - saturday 00:00-24:00 - } - -# This one is a favorite: never :) -define timeperiod{ - timeperiod_name never - alias Never - } - -# end of file diff --git a/local.d/adehnert-host.cfg b/local.d/adehnert-host.cfg index 47be1be..44db200 100644 --- a/local.d/adehnert-host.cfg +++ b/local.d/adehnert-host.cfg @@ -2,6 +2,7 @@ define host{ name adehnert-host use generic-host notification_interval 240 + max_check_attempts 5 register 0 } diff --git a/local.d/virunga.cfg b/local.d/virunga.cfg index 794a0ac..01700bf 100644 --- a/local.d/virunga.cfg +++ b/local.d/virunga.cfg @@ -23,7 +23,7 @@ define service { define command{ command_name check_vault_seal - command_line /etc/nagios3/conf.d/check_vault.py check_vault vault.dehnerts.com + command_line /etc/nagios4/conf.d/check_vault.py check_vault vault.dehnerts.com } define service { diff --git a/nagios.cfg b/nagios.cfg index 99bbe45..adc4a27 100644 --- a/nagios.cfg +++ b/nagios.cfg @@ -1,6 +1,6 @@ ############################################################################## # -# NAGIOS.CFG - Sample Main Config File for Nagios +# NAGIOS.CFG - Sample Main Config File for Nagios # # ############################################################################## @@ -8,25 +8,23 @@ # LOG FILE # This is the main log file where service and host events are logged -# for historical purposes. This should be the first option specified +# for historical purposes. This should be the first option specified # in the config file!!! -log_file=/var/log/nagios3/nagios.log - -# Commands definitions -cfg_file=/etc/nagios3/commands.cfg +log_file=/var/log/nagios4/nagios.log # Debian also defaults to using the check commands defined by the debian -# nagios-plugins package +# monitoring-plugins package cfg_dir=/etc/nagios-plugins/config -# Debian uses by default a configuration directory where nagios3-common, +# Debian uses by default a configuration directory where nagios4-common, # other packages and the local admin can dump or link configuration # files into. -cfg_dir=/etc/nagios3/conf.d +cfg_dir=/etc/nagios4/conf.d + # Site-specific config -cfg_dir=/etc/nagios3/local.d +cfg_dir=/etc/nagios4/local.d # OBJECT CONFIGURATION FILE(S) # These are the object configuration files in which you define hosts, @@ -35,41 +33,44 @@ cfg_dir=/etc/nagios3/local.d # if you wish (as shown below), or keep them all in a single config file. # You can specify individual object config files as shown below: -#cfg_file=/etc/nagios3/objects/commands.cfg -#cfg_file=/etc/nagios3/objects/contacts.cfg -#cfg_file=/etc/nagios3/objects/timeperiods.cfg -#cfg_file=/etc/nagios3/objects/templates.cfg +cfg_file=/etc/nagios4/objects/commands.cfg +cfg_file=/etc/nagios4/objects/contacts.cfg +cfg_file=/etc/nagios4/objects/timeperiods.cfg +cfg_file=/etc/nagios4/objects/templates.cfg + +# Definitions for monitoring the local (Linux) host +cfg_file=/etc/nagios4/objects/localhost.cfg # Definitions for monitoring a Windows machine -#cfg_file=/etc/nagios3/objects/windows.cfg +#cfg_file=/etc/nagios4/objects/windows.cfg # Definitions for monitoring a router/switch -#cfg_file=/etc/nagios3/objects/switch.cfg +#cfg_file=/etc/nagios4/objects/switch.cfg # Definitions for monitoring a network printer -#cfg_file=/etc/nagios3/objects/printer.cfg +#cfg_file=/etc/nagios4/objects/printer.cfg # You can also tell Nagios to process all config files (with a .cfg # extension) in a particular directory by using the cfg_dir # directive as shown below: -#cfg_dir=/etc/nagios3/servers -#cfg_dir=/etc/nagios3/printers -#cfg_dir=/etc/nagios3/switches -#cfg_dir=/etc/nagios3/routers +#cfg_dir=/etc/nagios4/servers +#cfg_dir=/etc/nagios4/printers +#cfg_dir=/etc/nagios4/switches +#cfg_dir=/etc/nagios4/routers # OBJECT CACHE FILE # This option determines where object definitions are cached when -# Nagios starts/restarts. The CGIs read object definitions from +# Nagios starts/restarts. The CGIs read object definitions from # this cache file (rather than looking at the object config files # directly) in order to prevent inconsistencies that can occur # when the config files are modified after Nagios starts. -object_cache_file=/var/cache/nagios3/objects.cache +object_cache_file=/var/lib/nagios4/objects.cache @@ -80,12 +81,12 @@ object_cache_file=/var/cache/nagios3/objects.cache # file. You can then start Nagios with the -u option to have it read # object definitions from this precached file, rather than the standard # object configuration files (see the cfg_file and cfg_dir options above). -# Using a precached object file can speed up the time needed to (re)start +# Using a precached object file can speed up the time needed to (re)start # the Nagios process if you've got a large and/or complex configuration. # Read the documentation section on optimizing Nagios to find our more # about how this feature works. -precached_object_file=/var/lib/nagios3/objects.precache +precached_object_file=/var/lib/nagios4/objects.precache @@ -98,7 +99,7 @@ precached_object_file=/var/lib/nagios3/objects.precache # defined as macros in this file and restrictive permissions (600) # can be placed on this file. -resource_file=/etc/nagios3/resource.cfg +resource_file=/etc/nagios4/resource.cfg @@ -108,13 +109,13 @@ resource_file=/etc/nagios3/resource.cfg # The contents of the status file are deleted every time Nagios # restarts. -status_file=/var/cache/nagios3/status.dat +status_file=/var/lib/nagios4/status.dat # STATUS FILE UPDATE INTERVAL # This option determines the frequency (in seconds) that -# Nagios will periodically dump program, host, and +# Nagios will periodically dump program, host, and # service status data. status_update_interval=10 @@ -122,7 +123,7 @@ status_update_interval=10 # NAGIOS USER -# This determines the effective user that Nagios should run as. +# This determines the effective user that Nagios should run as. # You can either supply a username or a UID. nagios_user=nagios @@ -130,7 +131,7 @@ nagios_user=nagios # NAGIOS GROUP -# This determines the effective group that Nagios should run as. +# This determines the effective group that Nagios should run as. # You can either supply a group name or a GID. nagios_group=nagios @@ -139,9 +140,9 @@ nagios_group=nagios # EXTERNAL COMMAND OPTION # This option allows you to specify whether or not Nagios should check -# for external commands (in the command file defined below). By default -# Nagios will *not* check for external commands, just to be on the -# cautious side. If you want to be able to use the CGI command interface +# for external commands (in the command file defined below). +# By default Nagios will check for external commands. +# 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 @@ -149,45 +150,24 @@ check_external_commands=0 -# EXTERNAL COMMAND CHECK INTERVAL -# This is the interval at which Nagios should check for external commands. -# This value works of the interval_length you specify later. If you leave -# that at its default value of 60 (seconds), a value of 1 here will cause -# Nagios to check for external commands every minute. If you specify a -# number followed by an "s" (i.e. 15s), this will be interpreted to mean -# actual seconds rather than a multiple of the interval_length variable. -# Note: In addition to reading the external command file at regularly -# scheduled intervals, Nagios will also check for external commands after -# event handlers are executed. -# NOTE: Setting this value to -1 causes Nagios to check the external -# command file as often as possible. - -#command_check_interval=15s -command_check_interval=-1 - - - # EXTERNAL COMMAND FILE # This is the file that Nagios checks for external command requests. # It is also where the command CGI will write commands that are submitted # 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 +# 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. # Debian Users: In case you didn't read README.Debian yet, _NOW_ is the # time to do it. -command_file=/var/lib/nagios3/rw/nagios.cmd +command_file=/var/lib/nagios4/rw/nagios.cmd -# EXTERNAL COMMAND BUFFER SLOTS -# This settings is used to tweak the number of items or "slots" that -# the Nagios daemon should allocate to the buffer that holds incoming -# external commands before they are processed. As external commands -# are processed by the daemon, they are removed from the buffer. +# QUERY HANDLER INTERFACE +# This is the socket that is created for the Query Handler interface -external_command_buffer_slots=4096 +#query_socket=/var/lib/nagios4/rw/nagios.qh @@ -195,7 +175,7 @@ external_command_buffer_slots=4096 # This is the lockfile that Nagios will use to store its PID number # in when it is running in daemon mode. -lock_file=/var/run/nagios3/nagios3.pid +lock_file=/var/run/nagios4/nagios4.pid @@ -205,7 +185,7 @@ lock_file=/var/run/nagios3/nagios3.pid # is created, used, and deleted throughout the time that Nagios is # running. -temp_file=/var/cache/nagios3/nagios.tmp +temp_file=/var/lib/nagios4/nagios.tmp @@ -231,7 +211,7 @@ event_broker_options=-1 # This directive is used to specify an event broker module that should # by loaded by Nagios 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. +# the module at startup are separated from the module path by a space. # #!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! # WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING !!! WARNING @@ -243,7 +223,8 @@ event_broker_options=-1 # # The correct/safe way of updating a module is by using one of these methods: # 1. Shutdown Nagios, replace the module file, restart Nagios -# 2. Delete the original module file, move the new module file into place, restart Nagios +# 2. Delete the original module file, move the new module file into place, +# restart Nagios # # Example: # @@ -268,10 +249,10 @@ log_rotation_method=d # LOG ARCHIVE PATH -# This is the directory where archived (rotated) log files should be +# This is the directory where archived (rotated) log files should be # placed (assuming you've chosen to do log rotation). -log_archive_path=/var/log/nagios3/archives +log_archive_path=/var/log/nagios4/archives @@ -328,6 +309,15 @@ log_initial_states=0 +# CURRENT STATES LOGGING OPTION +# If you don't want Nagios to log all current host and service states +# after log has been rotated to the main log file, you can disable this +# option by setting this value to 0. Default value is 1. + +log_current_states=1 + + + # EXTERNAL COMMANDS LOGGING OPTION # If you don't want Nagios to log external commands, set this value # to 0. If external commands should be logged, set this value to 1. @@ -431,7 +421,7 @@ max_host_check_spread=30 # MAXIMUM CONCURRENT SERVICE CHECKS -# This option allows you to specify the maximum number of +# 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 @@ -453,7 +443,7 @@ 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 +# check result reaper event will be allowed to run before # returning control back to Nagios so it can perform other # duties. @@ -467,16 +457,16 @@ max_check_result_reaper_time=30 # service checks that have not yet been processed. # # Note: Make sure that only one instance of Nagios has access -# to this directory! +# to this directory! -check_result_path=/var/lib/nagios3/spool/checkresults +check_result_path=/var/lib/nagios4/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 +# 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 @@ -538,14 +528,14 @@ enable_predictive_service_dependency_checks=1 # SOFT STATE DEPENDENCIES -# This option determines whether or not Nagios will use soft state -# information when checking host and service dependencies. Normally -# Nagios will only use the latest hard host or service state when +# This option determines whether or not Nagios will use soft state +# information when checking host and service dependencies. Normally +# Nagios will only use the latest hard host or service state when # checking dependencies. If you want it to use the latest state (regardless -# of whether its a soft or hard state type), enable this option. +# 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 +# 0 = Don't use soft state dependencies (default) +# 1 = Use soft state dependencies soft_state_dependencies=0 @@ -563,7 +553,7 @@ soft_state_dependencies=0 # This option determines whether or not Nagios 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. +# the monitoring server. # WARNING: THIS IS AN EXPERIMENTAL FEATURE - IT CAN DEGRADE # PERFORMANCE, RATHER THAN INCREASE IT, IF USED IMPROPERLY @@ -597,14 +587,6 @@ auto_rescheduling_window=180 -# SLEEP TIME -# This is the number of seconds to sleep between checking for system -# events and service checks that need to be run. - -sleep_time=0.25 - - - # TIMEOUT VALUES # These options control how much time Nagios will allow various # types of commands to execute before killing them off. Options @@ -618,6 +600,7 @@ host_check_timeout=30 event_handler_timeout=30 notification_timeout=30 ocsp_timeout=5 +ochp_timeout=5 perfdata_timeout=5 @@ -626,7 +609,7 @@ perfdata_timeout=5 # This setting determines whether or not Nagios will save state # information for services and hosts before it shuts down. Upon # startup Nagios will reload all saved service and host state -# information before starting to monitor. This is useful for +# information before starting to monitor. This is useful for # maintaining long-term data on state statistics, etc, but will # slow Nagios down a bit when it (re)starts. Since its only # a one-time penalty, I think its well worth the additional @@ -638,13 +621,13 @@ retain_state_information=1 # STATE RETENTION FILE # This is the file that Nagios should use to store host and -# service state information before it shuts down. The state +# service state information before it shuts down. The state # information in this file is also read immediately prior to # starting to monitor the network when Nagios is restarted. # This file is used only if the retain_state_information # variable is set to 1. -state_retention_file=/var/lib/nagios3/retention.dat +state_retention_file=/var/lib/nagios4/retention.dat @@ -661,7 +644,7 @@ retention_update_interval=60 # USE RETAINED PROGRAM STATE -# This setting determines whether or not Nagios will set +# This setting determines whether or not Nagios 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 @@ -688,7 +671,7 @@ use_retained_scheduling_info=1 # program restarts. # # The values of the masks are bitwise ANDs of values specified -# by the "MODATTR_" definitions found in include/common.h. +# 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... @@ -732,19 +715,19 @@ interval_length=60 # enable this option to ensure that you stay on top of the latest critical # patches to Nagios. Nagios is critical to you - make sure you keep it in # good shape. Nagios will check once a day for new updates. Data collected -# by Nagios Enterprises from the update check is processed in accordance -# with our privacy policy - see http://api.nagios.org for details. +# by Nagios Enterprises from the update check is processed in accordance +# with our privacy policy - see https://api.nagios.org for details. check_for_updates=1 # BARE UPDATE CHECK -# This option deterines what data Nagios will send to api.nagios.org when -# it checks for updates. By default, Nagios will send information on the +# This option determines what data Nagios will send to api.nagios.org when +# it checks for updates. By default, Nagios will send information on the # current version of Nagios you have installed, as well as an indicator as # to whether this was a new installation or not. Nagios Enterprises uses -# this data to determine the number of users running specific version of +# this data to determine the number of users running specific version of # Nagios. Enable this option if you do not want this information to be sent. bare_update_check=0 @@ -764,7 +747,7 @@ use_aggressive_host_checking=0 # SERVICE CHECK EXECUTION OPTION # This determines whether or not Nagios will actively execute -# service checks when it initially starts. If this option is +# service checks when it initially starts. If this option is # disabled, checks are not actively made, but Nagios can still # receive and process passive check results that come in. Unless # you're implementing redundant hosts or have a special need for @@ -786,7 +769,7 @@ accept_passive_service_checks=1 # HOST CHECK EXECUTION OPTION # This determines whether or not Nagios will actively execute -# host checks when it initially starts. If this option is +# host checks when it initially starts. If this option is # disabled, checks are not actively made, but Nagios can still # receive and process passive check results that come in. Unless # you're implementing redundant hosts or have a special need for @@ -843,7 +826,7 @@ process_performance_data=0 # These commands are run after every host and service check is # performed. These commands are executed only if the # enable_performance_data option (above) is set to 1. The command -# argument is the short name of a command definition that you +# 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. @@ -857,8 +840,8 @@ process_performance_data=0 # Performance data is only written to these files if the # enable_performance_data option (above) is set to 1. -#host_perfdata_file=/tmp/host-perfdata -#service_perfdata_file=/tmp/service-perfdata +#host_perfdata_file=/var/lib/nagios4/host-perfdata +#service_perfdata_file=/var/lib/nagios4/service-perfdata @@ -880,7 +863,7 @@ process_performance_data=0 # 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. +# likely want the default append ("a") mode. #host_perfdata_file_mode=a #service_perfdata_file_mode=a @@ -909,7 +892,7 @@ process_performance_data=0 # HOST AND SERVICE PERFORMANCE DATA PROCESS EMPTY RESULTS -# THese options determine wether the core will process empty perfdata +# These options determine whether 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 @@ -935,7 +918,7 @@ obsess_over_services=0 # OBSESSIVE COMPULSIVE SERVICE PROCESSOR COMMAND # This is the command that is run for every service check that is # processed by Nagios. This command is executed only if the -# obsess_over_services option (above) is set to 1. The command +# obsess_over_services option (above) is set to 1. The command # argument is the short name of a command definition that you # define in your host configuration file. Read the HTML docs for # more information on implementing distributed monitoring. @@ -959,7 +942,7 @@ obsess_over_hosts=0 # OBSESSIVE COMPULSIVE HOST PROCESSOR COMMAND # This is the command that is run for every host check that is # processed by Nagios. This command is executed only if the -# obsess_over_hosts option (above) is set to 1. The command +# 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. @@ -998,9 +981,9 @@ passive_host_checks_are_soft=0 # ORPHANED HOST/SERVICE CHECK OPTIONS -# These options determine whether or not Nagios will periodically +# These options determine whether or not Nagios will periodically # check for orphaned host service checks. Since service checks are -# not rescheduled until the results of their previous execution +# 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 @@ -1084,9 +1067,9 @@ additional_freshness_latency=15 # FLAP DETECTION OPTION # This option determines whether or not Nagios will try -# and detect hosts and services that are "flapping". +# and detect hosts and services that are "flapping". # Flapping occurs when a host or service changes between -# states too frequently. When Nagios detects that a +# states too frequently. When Nagios 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 @@ -1130,7 +1113,7 @@ date_format=iso8601 # 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 +# will also need to alter the Apache directives for the CGI path # to include your timezone. Example: # # @@ -1143,37 +1126,6 @@ date_format=iso8601 - -# P1.PL FILE LOCATION -# This value determines where the p1.pl perl script (used by the -# embedded Perl interpreter) is located. If you didn't compile -# Nagios with embedded Perl support, this option has no effect. - -p1_file=/usr/lib/nagios3/p1.pl - - - -# EMBEDDED PERL INTERPRETER OPTION -# This option determines whether or not the embedded Perl interpreter -# will be enabled during runtime. This option has no effect if Nagios -# has not been compiled with support for embedded Perl. -# Values: 0 = disable interpreter, 1 = enable interpreter - -enable_embedded_perl=1 - - - -# EMBEDDED PERL USAGE OPTION -# This option determines whether or not Nagios will process Perl plugins -# 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 - - - # 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 @@ -1190,10 +1142,12 @@ illegal_object_name_chars=`~!$%^&*|'"<>?,()= # host check commands. # The following macros are stripped of the characters you specify: # $HOSTOUTPUT$ +# $LONGHOSTOUTPUT$ # $HOSTPERFDATA$ # $HOSTACKAUTHOR$ # $HOSTACKCOMMENT$ # $SERVICEOUTPUT$ +# $LONGSERVICEOUTPUT$ # $SERVICEPERFDATA$ # $SERVICEACKAUTHOR$ # $SERVICEACKCOMMENT$ @@ -1214,7 +1168,7 @@ use_regexp_matching=0 # "TRUE" REGULAR EXPRESSION MATCHING -# This option controls whether or not "true" regular expression +# 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 @@ -1233,8 +1187,8 @@ use_true_regexp_matching=0 # using the $ADMINEMAIL$ and $ADMINPAGER$ macros in your notification # commands. -admin_email=root@localhost -admin_pager=pageroot@localhost +admin_email=nagios@localhost +admin_pager=pagenagios@localhost @@ -1267,13 +1221,16 @@ use_large_installation_tweaks=0 # This option determines whether or not Nagios will make all standard # macros available as environment variables when host/service checks # and system commands (event handlers, notifications, etc.) are -# executed. Enabling this option can cause performance issues in -# large installations, as it will consume a bit more memory and (more -# importantly) consume more CPU. -# Values: 1 - Enable environment variable macros (default) -# 0 - Disable environment variable macros +# executed. +# Enabling this is a very bad idea for anything but very small setups, +# as it means plugins, notification scripts and eventhandlers may run +# out of environment space. It will also cause a significant increase +# in CPU- and memory usage and drastically reduce the number of checks +# you can run. +# Values: 1 - Enable environment variable macros +# 0 - Disable environment variable macros (default) -enable_environment_macros=1 +enable_environment_macros=0 @@ -1308,21 +1265,24 @@ enable_environment_macros=1 # 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 +# 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 +# 4096 = Interprocess communication +# 8192 = Scheduling +# 16384 = Workers debug_level=0 @@ -1341,7 +1301,7 @@ debug_verbosity=1 # DEBUG FILE # This option determines where Nagios should write debugging information. -debug_file=/var/log/nagios3/nagios.debug +debug_file=/var/log/nagios4/nagios.debug @@ -1355,3 +1315,73 @@ debug_file=/var/log/nagios3/nagios.debug max_debug_file_size=1000000 + +# Should we allow hostgroups to have no hosts, we default this to off since +# that was the old behavior + +allow_empty_hostgroup_assignment=0 + + + +# Normally worker count is dynamically allocated based on 1.5 * number of cpu's +# with a minimum of 4 workers. This value will override the defaults + +#check_workers=3 + + + +# DISABLE SERVICE CHECKS WHEN HOST DOWN +# This option will disable all service checks if the host is not in an UP state +# +# While desirable in some environments, enabling this value can distort report +# values as the expected quantity of checks will not have been performed + +#host_down_disable_service_checks=0 + + + +# SET SERVICE/HOST STATUS WHEN SERVICE CHECK SKIPPED +# These options will allow you to set the status of a service when its +# service check is skipped due to one of three reasons: +# 1) failed dependency check; 2) parent's status; 3) host not up +# Number 3 can only happen if 'host_down_disable_service_checks' above +# is set to 1. +# Valid values for the service* options are: +# -1 Do not change the service status (default - same as before 4.4) +# 0 Set the service status to STATE_OK +# 1 Set the service status to STATE_WARNING +# 2 Set the service status to STATE_CRITICAL +# 3 Set the service status to STATE_UNKNOWN +# The host_skip_check_dependency_status option will allow you to set the +# status of a host when itscheck is skipped due to a failed dependency check. +# Valid values for the host_skip_check_dependency_status are: +# -1 Do not change the service status (default - same as before 4.4) +# 0 Set the host status to STATE_UP +# 1 Set the host status to STATE_DOWN +# 2 Set the host status to STATE_UNREACHABLE +# We may add one or more statuses in the future. + +#service_skip_check_dependency_status=-1 +#service_skip_check_parent_status=-1 +#service_skip_check_host_down_status=-1 +#host_skip_check_dependency_status=-1 + + + +# LOAD CONTROL OPTIONS +# To get current defaults based on your system, issue this command to +# the query handler: +# echo -e '@core loadctl\0' | nc -U /usr/local/nagios/var/rw/nagios.qh +# +# Please note that used incorrectly these options can induce enormous latency. +# +# loadctl_options: +# jobs_max The maximum amount of jobs to run at one time +# jobs_min The minimum amount of jobs to run at one time +# jobs_limit The maximum amount of jobs the current load lets us run +# backoff_limit The minimum backoff_change +# backoff_change # of jobs to remove from jobs_limit when backing off +# rampup_limit Minimum rampup_change +# rampup_change # of jobs to add to jobs_limit when ramping up + +#loadctl_options=jobs_max=100;backoff_limit=10;rampup_change=5 diff --git a/objects/commands.cfg b/objects/commands.cfg index b4dbbec..9b57177 100644 --- a/objects/commands.cfg +++ b/objects/commands.cfg @@ -290,3 +290,9 @@ 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/lib/nagios4/service-perfdata.out } + +define command{ + command_name check_jabber + # Sadly, check_tcp.c / check_jabber has no starttls support, so we can't check the cert + command_line /usr/lib/nagios/plugins/check_jabber -H '$HOSTADDRESS$' + } diff --git a/objects/contacts.cfg b/objects/contacts.cfg index 3c7a0bc..8bc1931 100644 --- a/objects/contacts.cfg +++ b/objects/contacts.cfg @@ -43,9 +43,8 @@ define contact { # 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 Nagios Administrators - members nagiosadmin -} +define contactgroup{ + contactgroup_name admins + alias Nagios Administrators + members adehnert-pub-zephyr + } -- 2.34.1