On Jan 30, 2008 3:35 AM, Buchan Milne <bgmilne at staff.telkomsa.net> wrote:
On Wednesday 30 January 2008 11:17:41 Anna Jonna Armannsdottir wrote:
On þri, 2008-01-29 at 17:03 -0600, Ralph Mitchell wrote:
I've got a few instances of
a.b.c.d www.server.com # http://www.server.com/and the http column shows up just fine, including the time the test took and a nice graph.
The question I was just asked is, is it possible to specify "max response time", so that if the time shown is greater than N seconds I get a red flag?? I don't see a way to set that in the man pages for either bb-hosts or hobbit-client.cfg.
There is the possibility to use a per host test e.g.:
a.b.c.d www.server.com # http://www.server.com/ badhttp-06-0000-2359:3:5:8 badhttp-12345-2200-0659:3:5:8 badhttp-12345-0700-2159:1:2:3
This specifies the number of times the test has to be yellow or red, in order to actually siglal yellow or red (to the alert module- correct me if i am wrong here).
I suggest that this may be seen as your time N (in seconds) given by T*yellow and T*red . T is the time between tests or retests.
In the working hours, I get a warning if http is down for T*2 or more, and an alert if it is down for T*3 minutes or more.
Some clarification may be called for here.
The beauty of this, is that it can be configured per time of day or day of the week as is done in the example. BTW. I am actually using this. :)
But, it doesn't allow you to change the timeout (e.g., http server 1 with slow application always takes 30 seconds to give content back, but http server 2 must respond in less than 5 seconds to meet SLA) before the test is considered to have failed.
Yep, that's what I've been asked for. It's not exactly a timeout, because that implies abandoning the connection. The server could still be responsive, but slow - i.e. alive and talking to the public, while still being in breach of SLA.
Ralph Mitchell