Nagios service latency on Service (1000+)

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of sunchai (gillnaldo : sun)
> Sent: Tuesday, September 04, 2007 9:27 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Nagios service latency on Service (1000+)


> HOST SCHEDULING INFORMATION
> ---------------------------
> Total hosts:                     170
> Total scheduled hosts:           170
> Host inter-check delay method:   NONE
> Host inter-check delay:          0.00 sec
> Max host check spread:           5 min
> First scheduled check:           Tue Sep  4 21:09:17 2007
> Last scheduled check:            Tue Sep  4 21:09:17 2007
> 
> SERVICE SCHEDULING INFORMATION
> -------------------------------
> Total services:                     1084
> Total scheduled services:           1084
> Service inter-check delay method:   NONE
> Inter-check delay:                  0.00 sec
> Interleave factor method:           SMART
> Average services per host:          6.38
> Service interleave factor:          7
> Max service check spread:           5 min
> First scheduled check:              Tue Sep  4 21:09:17 2007
> Last scheduled check:               Tue Sep  4 21:09:17 2007
> 
> 
> CHECK PROCESSING INFORMATION
> ----------------------------
> Service check reaper interval:      3 sec
> Max concurrent service checks:      Unlimited
> 
> 
> PERFORMANCE SUGGESTIONS
> -----------------------
> * Host checks might be scheduled too closely together - consider
> increasing 'check_interval' option for your hosts

Unless you have exceptional circumstances, you should have no scheduled
host checks. Nagios will stop _all_ other processing while hosts are
being checked. Marked increase in check latency is a known result of
scheduling host checks. Nagios contains logic to automagically schedule
host checks on an as-needed basis.

http://nagios.sourceforge.net/docs/2_0/xodtemplate.html#host

"check_interval: 	NOTE: Do NOT enable regularly scheduled checks
of a host unless you absolutely need to! Host checks are already
performed on-demand when necessary, so there are few times when
regularly scheduled checks would be needed. Regularly scheduled host
checks can negatively impact performance - see the performance tuning
tips for more information. This directive is used to define the number
of "time units" between regularly scheduled checks of the host. Unless
you've changed the interval_length directive from the default value of
60, this number will mean minutes. More information on this value can be
found in the check scheduling documentation."

http://nagios.sourceforge.net/docs/2_0/checkscheduling.html#host_checks

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null