OP#436 more controls
This commit is contained in:
@@ -120,210 +120,36 @@ retained_process_service_attribute_mask=<%= @ng_ret_proc_svc_attr_mask %>
|
||||
retained_contact_host_attribute_mask=<%= @ng_ret_contact_h_attr_mask %>
|
||||
retained_contact_service_attribute_mask=<%= @ng_ret_contact_s_attr_mask %>
|
||||
|
||||
|
||||
# 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
|
||||
|
||||
|
||||
|
||||
# CHECK FOR UPDATES
|
||||
# This option determines whether Nagios will automatically check to
|
||||
# see if new updates (releases) are available. It is recommend that you
|
||||
# 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 https://api.nagios.org for details.
|
||||
|
||||
check_for_updates=1
|
||||
|
||||
|
||||
|
||||
# BARE UPDATE CHECK
|
||||
# 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
|
||||
# Nagios. Enable this option if you do not want this information to be sent.
|
||||
|
||||
bare_update_check=0
|
||||
|
||||
|
||||
|
||||
# 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 Nagios will actively execute
|
||||
# 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
|
||||
# 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 Nagios 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 Nagios will actively execute
|
||||
# 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
|
||||
# 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 Nagios 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 Nagios 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 Nagios 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 Nagios 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
|
||||
# enable_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
|
||||
# enable_performance_data option (above) is set to 1.
|
||||
|
||||
#host_perfdata_file=/var/log/nagios/host-perfdata
|
||||
#service_perfdata_file=/var/log/nagios/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 default 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 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
|
||||
# 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
|
||||
|
||||
interval_length=<%= @ng_interval_length %>
|
||||
check_for_updates=<%= @ng_check_for_updates %>
|
||||
bare_update_check=<%= @ng_bare_update_check %>
|
||||
|
||||
use_aggressive_host_checking=<%= @ng_use_aggr_host_checking %>
|
||||
execute_service_checks=<%= @ng_execute_service_checks %>
|
||||
accept_passive_service_checks=<%= @ng_accept_pass_svc_checks %>
|
||||
execute_host_checks=<%= @ng_execute_host_checks %>
|
||||
accept_passive_host_checks=<%= @ng_accept_pass_host_checks %>
|
||||
|
||||
enable_notifications=<%= @ng_enable_notifications %>
|
||||
enable_event_handlers=<%= @ng_enable_event_handlers %>
|
||||
process_performance_data=<%= @ng_process_perf_data %>
|
||||
|
||||
<% if @ng_process_perf_data == '1' -%>
|
||||
host_perfdata_command=<%= @ng_host_perfdata_command %>
|
||||
service_perfdata_command=<%= @ng_svc_perfdata_command %>
|
||||
host_perfdata_file=<%= @ng_host_perfdata_file %>
|
||||
service_perfdata_file=<%= @ng_service_perfdata_file %>
|
||||
host_perfdata_file_template=<%= @ng_host_perfdata_template %>
|
||||
service_perfdata_file_template=<%= @ng_svc_perfdata_template %>
|
||||
host_perfdata_file_mode=<%= @ng_host_perfdata_file_mode %>
|
||||
service_perfdata_file_mode=<%= @ng_svc_perfdata_file_mode %>
|
||||
host_perfdata_file_processing_interval=<%= @ng_h_perfdata_proc_intval %>
|
||||
service_perfdata_file_processing_interval=<%= @ng_s_perfdata_proc_intval %>
|
||||
host_perfdata_file_processing_command=<%= @ng_h_perfdata_proc_cmd %>
|
||||
service_perfdata_file_processing_command=<%= @ng_s_perfdata_proc_cmd %>
|
||||
host_perfdata_process_empty_results=<%= @ng_h_perfdata_proc_e_res %>
|
||||
service_perfdata_process_empty_results=<%= @ng_s_perfdata_proc_e_res %>
|
||||
<% end -%>
|
||||
|
||||
# OBSESS OVER SERVICE CHECKS OPTION
|
||||
# This determines whether or not Nagios will obsess over service
|
||||
|
||||
Reference in New Issue
Block a user