On 02/22/2011 03:13 AM, Yueh-Hung Liu wrote: > because at any moment in physical, not all checks will be performed, > therefore Nagios only knows the "previous" average latency and the > latency of services which have just finished. > Nagios won't keep the latency of checks in somewhere so it has to > calculate the "present" average latency right after each check while > it has the newest latency of that check in hand. > you can see the formula that while the total latency is restored, the > number of checks will be decreased by 1, that means the latency of the > check just finished will be added to calculate new average latency. > this method can make sure the average latency is "dynamical" and "real time". >
This makes absolutely no sense for the nagiostats program though, which only reads the status.log file and parses the data found there in order to print it just once. -- Andreas Ericsson [email protected] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. ------------------------------------------------------------------------------ Index, Search & Analyze Logs and other IT data in Real-Time with Splunk Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. Free Software Download: http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ 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
