<tt>nagios-devel-bounces@lists.sourceforge.net schrieb am 02.04.2008 14:55:15: > While I agree this particular info is missing, the active check latency > tells you how much you're lagging behind. As long as it's near 0 you're > OK, but when it starts to show big latencies (i.e. >30 seconds) even > keeps growing then you definitely have a problem. </tt> <tt>Yes I know. But the main point was, that the presented percentages</tt> <tt>are more or less useless. The check latency is by far the only real</tt> <tt>relevant information on that page. A fact, that makes the page seem</tt> <tt>to be broken by design to me.</tt> <tt> > Also note that service latency is not always a "server performance > problem". In Nagios 2.0, host checks are run serially so the time in > takes to run host checks can cause latency to grow up pretty fast, > especially when you start seeing hosts down. > > There's other reason for high latencies: perfdata commands, ocsd > commands, etc. Ideally you can avoid this by having Nagios write a file > or FIFO instead... There's many example out there. </tt> <tt>I do know, but that has actually nothing to do with my initial proposal ;)</tt> <tt>This thread was not meant for debugging my performance issues - especially</tt> <tt>since I already solved them last week. ^^ It is more or less just a reflection</tt> <tt>of the fact, that the Performance Info was just very useless for actually</tt> <tt>finding out infos about the performance.</tt> <tt>S</tt> <tt> </tt>-- Sascha Runschke Netzwerk- und Systemmanagement Telefon : +49 (201) 102-1879 Mobil : +49 (173) 5419665 Fax : +49 (201) 102-1102105 GFKL Financial Services AG Vorstand: Dr. Peter Jänsch (Vors.), Jürgen Baltes, Dr. Till Ergenzinger, Dr. Tom Haverkamp Vorsitzender des Aufsichtsrats: Dr. Georg F. Thoma Sitz: Limbecker Platz 1, 45127 Essen, Amtsgericht Essen, HRB 13522