latency and parallelize check

[Johan Corsini]

Le Jeudi 27 Avril 2006 11:29, Sandeep Narasimha Murthy a écrit :
> Hi,
>
>
>
> I have a few questions regarding Latency and parallelize checks.
> Appreciate some help in this regard..
>
>
>
> 1. Latency: The average Latency value is 70.24 Seconds for all the
> services but I believe is way too high. I browsed the site
> (http://nagios.sourceforge.net/docs/2_0/tuning.html) but couldn't
> exactly figure out how to reduce this figure.  How do I go about
> reducing the Latency figure ?
>
>
>
>
>
> 2. Regarding Parallelize Check: (This directive is used to determine
> whether or not the service check can be parallelized. By default, all
> service checks are parallelized. Disabling parallel checks of services
> can result in serious performance problems.)
>
>
>
> From what I can understand, Parallelize check means that if I have a
> Service check configured to run every 3 minutes, and Nagios determines
> that even though the previous check launched 3 mins ago has still not
> finished it launches a new check !? Am I correct in this assumption ? If
> yes, how can Disabling this result in performance problems ? shouldn't
> it be viceversa ?

As far as I understand, Parallelize check means that Nagios can multiple 
different service checks at the same time...  So, if you have let say 100 
checks.  Without Parallelize check, Nagios would check the first one, wait 
for the result, then check the second one, wait, etc...  It means that if you 
got checks that are kinda slow, the time to check every service can be 
huge...  And even if the checks are fast, as soon as you got a lot of 
services, it will take some time anyway.



>
> 3. Finally, In a service configuration file, I have the following:
>
> Maximum Check Attempts:  5
>
> Normal Check Interval In Time-Units: 5
>
> Retry Check Interval In Time-Units: 3
>
>
>
> In the above, Shouldn't  the Normal Check Interval be Greater than
> Maximum Check Attempts  *  Retry Check Interval  ?

I do not see why it should...
With this configuration, nagios would, for a said service, perform one check 
every 5 minutes.  When it detects a problem, it would do the check once every 
3 minutes.  And after 5 "negative" checks, it would then consider the service 
in a "hard state", and issue appropriate actions (ie : sending alert mails).

> TIA,
> sg


Johan.



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
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