performance

[Neil]

I don't know now where if goofed up in services.cfg and nagios.cfg :( 

Look at my scheduling:
Host  Service  Last Check  Next Check  Active Checks Actions
dbsw805 Terminal Services - 3389/TCP 02-03-2004 13:54:02 02-03-2004 13:59:02 
ENABLED
gateway10-96-255-10 PING 02-03-2004 13:54:04 02-03-2004 13:59:04 ENABLED
gateway10.151.254.42 PING 02-03-2004 13:54:07 02-03-2004 13:59:07 ENABLED
gateway10.153.255.3 PING 02-03-2004 13:54:09 02-03-2004 13:59:09 ENABLED
gateway10.156.188.3 PING 02-03-2004 13:54:12 02-03-2004 13:59:12 ENABLED
gateway10.178.0.2 PING 02-03-2004 13:54:15 02-03-2004 13:59:15 ENABLED
gateway10.254.0.46 PING 02-03-2004 13:54:17 02-03-2004 13:59:17 ENABLED
gateway10.254.2.18 PING 02-03-2004 13:54:20 02-03-2004 13:59:20 ENABLED 

I now not able to monitor services in a minute. :( 

I'm still trying to find out what I modified. 

Skip Montanaro writes: 

> 
>     Neil> Monitoring Performance
>     Neil> Check Execution Time: 0 / 5 / 1.697 sec
>     Neil> Check Latency: 15 / 45 / 38.110 sec
>     Neil> # Active Checks: 109
>     Neil> # Passive Checks: 0  
> 
>     Neil> And if it's ok, can someone tell me what those values are?  
> 
> I don't know if it's okay or not (I sort of suspect not - big latencies are
> generally not good), but your latency numbers are much different than mine.
> Mine are 0 / 1 / 0.181 sec.  I have 513 active checks and no passive checks. 
> 
> -- 
> Skip Montanaro
> Got gigs? http://www.musi-cal.com/submit.html
> Got spam? http://spambayes.sf.net/
> skip at pobox.com
 


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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