Limit Service Check

Marc Powell marc at ena.com
Wed May 9 13:49:35 CEST 2007



> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of adi yesaya
> Sent: Wednesday, May 09, 2007 5:58 AM
> To: Nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Limit Service Check
> 
> Hi all,
> 
> I have 15 hosts and around 100 services running on each host. Is it
> possible to limit the service check of Nagios that it will only run 2
> service checks on one host in one point of time? If it is possible,
how is
> it done?

You don't really have that level of control over scheduling. You can
approximate it with service_interleave_factor but you aren't really
guaranteed a max number of concurrent checks per host...

http://nagios.sourceforge.net/docs/2_0/configmain.html#service_interleav
e_factor


> Another question is:
> If, for example, 1 service check fails, it will try out 4 times again
> before it announce the service as "warning". In this 4 time retry
period,
> will Nagios finish this retry check first then run the next scheduled
> service check or will nagios run the retry check and the next service
> check in parallel?

If you're talking about checks of the same service, nagios will not
return to normal check intervals for that service until
max_check_attempts is reached or the service returns an OK state. During
this time nagios will continue to process other service checks at their
normal_check_interval in parallel.

--
Marc

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
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