This means that we should use an inter-check delay of 0.3 seconds when spacing out the initial host checks. Given that information, we realize that (on average) we need to re-check 1,000 hosts every 300 seconds. That means the average check interval for all hosts is 300 seconds (300,000 / 1,000).
The total check_interval of all hosts is 5,000 (1,000 * 5) which means the total check interval for all hosts is 300,000 (5,000 * 60). Say you have 1,000 hosts that each have a check interval of 5 minutes. total host check interval = (total check_interval of all hosts) * (nagios.cfg check_interval).average check interval for all hosts = (total host check interval) / (total number of hosts).host inter-check delay = (average check interval for all hosts) / (total number of hosts).When using the "smart" setting of the host_inter_check_delay_method or service_inter_check_delay_method variables, Nagios will calculate an inter-check delay value by using the following calculations: This documentation will discuss how the "smart" calculation works, as this is the setting you will want to use for normal operation. By giving a value to the host_inter_check_delay_method or service_inter_check_delay_method variables in the main config file, you can modify how this delay is calculated. The spacing between consecutive checks is called the inter-check delay. Nagios does not start monitoring anything when this argument is used.Īs mentioned before, Nagios attempts to equalize the load placed on the machine that is running Nagios by equally spacing out initial checks. Because this option will overwrite the status log, you should not use it when another copy of Nagios is running. Doing so will display basic scheduling information (inter-check delay, interleave factor, first and last check time, etc) and will create a new status log that shows the exact time that all services are initially scheduled. Note: If you want to view the initial check scheduling information, start Nagios using the -s command line option. Hopefully the initial scheduling will keep the load on the local and remote hosts fairly balanced as time goes by. At least we try to get things off to a good start. Reasons for this include the fact that objects are not all checked at the same interval, some objects take longer to execute than others, host and/or service problems can alter the timing of one or more checks, etc. Both the inter-check delay and interleave functions are discussed below.Įven though checks are initially scheduled to balance the load on both the local and remote hosts, things will eventually give in to the ensuing chaos and be a bit random. The spacing of checks (also known as the inter-check delay) is used to minimize/equalize the load on the local host running Nagios and the interleaving is used to minimize/equalize load imposed on remote hosts. This is done by spacing the initial checks out, as well as interleaving them. When Nagios (re)starts, it will attempt to schedule the initial check of all objects in a manner that will minimize the load imposed on the local and remote hosts.
0 kommentar(er)
