--On Friday, November 11, 2005 10:47:39 +0100 GioiaBa <[EMAIL PROTECTED]>
wrote:
<SNIP>
period wd {Sat-Sund}
<SNIP>
last day, the Router service went down, so 'Ext' watching began to fail..
the problem is that the failure leght has been 1h 39 mintues !! and never
became Alert.. so no Alert has been sent for that hour.. this would be a
great problem, as the service we are monitoring is our Router
connectivity.. any ideas on the reason why this could happen ?
Was the failure on a Saturday or Sunday? Your period definition is for
weekends only. Perhaps you want 'period wd {Sun-Sat}'. Or simply an empty
period definition will match always.
..and we also need to monitor the responding time of the service..
I mean the service 'fails' only if the fping did not respond in xxminutes
.. I've read before how to do it, but I can't find it right now.. Any
help would be appreciated..
thank you very much
I'm not sure exactly what you're asking. If you want to control the
detection behavior of a single service test, look at the command line
options for the monitor scripts you're using. For example, fping.monitor
takes the command line options that you can use to control the ping timeout
behavior:
-r num retry "num" times for each host before reporting failure
-s num consider hosts which respond in over "num" msecs failures
-t num wait "num" msecs before sending retries
-David
David Nolan <*> [EMAIL PROTECTED]
curses: May you be forced to grep the termcap of an unclean yacc while
a herd of rogue emacs fsck your troff and vgrind your pathalias!
_______________________________________________
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
