> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of James > Sent: Wednesday, April 25, 2007 5:59 PM > To: [email protected] > Subject: [Nagios-users] nagios service check latency > > Ok i have a question about setting priority to service checks > > since i have a handful of service check checking clusters of servers i'd > like the priority of those service checks as high as for instance... > host checks > > as in they happen regularly and almost instantly without latency > > Now my service checks used to be REALLY high latency but i removed > unnecessary active checks on certain services. However my service checks > for my clusters are still latent by about 5 minutes. Is there anyway to > reduce this or just say that a certain service check should have zero > latency?
That is a really high latency and seems to imply either that you're starving nagios for resources or you're doing lots of host checks. How many hosts/services are you checking on what kind of hardware? Have you looked at the performance tuning documentation? For a benchmark, I have machines doing just over a thousand service checks every 5 minutes (mostly check_fping) with a max latency of under 5 seconds and average latency of 0.638 seconds at the moment. There's no way to tell nagios that certain service checks have a higher priority over others outside of normal_check_interval/retry_check_interval. The scheduler just automagically figures out what to do based on your config. -- 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 [email protected] 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
