Nagios scheduling issues

Andreas Ericsson ae at op5.se
Thu Oct 28 10:21:45 CEST 2004


Edy Gasparini wrote:
> Guys,
> 
> Have got Nagios 1.2 running on RedHat Enterprise Linux 3 (RHEL3), with MySQL
> support/backend. With a small number of hosts/services (say <10), scheduling
> works as expected, based on check_interval values.
> 
> However, now I have 34 hosts and 760 service checks and the scheduling is
> screwed badly. Checks are being scheduled 60 mins or so apart (with
> check_interval = 2)
> 
> I originally had: 
> 
> inter_check_delay_method=s
> service_interleave_factor=s
> max_concurrent_checks=0
> 
> I've since changed from smart to set figures, as described in the Nagios
> doco, with no change.
> 
> Check latency is currently displaying 
> 
> 3206 / 3935 / 3635.479 sec
> 

Change the max_concurrent_checks value to 0. If your system load 
skyrockets, try setting it to 80 or so, or increase the check_interval 
for your services.

> Performance info says:
> <= 1 minute: 0 (0.0%) 
> <= 5 minutes: 28 (3.6%) 
> <= 15 minutes: 127 (16.5%) 
> <= 1 hour: 628 (81.5%) 
> 
> Does anyone have a guide on correctly tuning Nagios for large deployments?
> 

34 hosts and 760 service isn't exactly a very large deployment (although 
a pretty odd one, with +22 services on each monitored node). Go with the 
's' setting and let it figure out its own checking delays.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
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





More information about the Users mailing list