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.
Thanks,
Ralph Mitchell
On Wednesday 30 January 2008 01:03:26 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.
Not per-test or per-host, it is a global timeout, which you can set as an option to bbtest-net, which is documented in bbtest-net's man page, just add it to the bbtest task in hobbitlaunch.cfg.
However, per-test or per-host or per-host-test timeout limits would be nice ....
Regards, Buchan
Hi,
Please let me know how to set the per-test or per-host or per-host-test timeout limits.
Thanks & Regards, Arunkumar
-----Original Message----- From: Buchan Milne [mailto:bgmilne at staff.telkomsa.net] Sent: Wednesday, January 30, 2008 2:08 PM To: hobbit at hswn.dk Cc: Ralph Mitchell Subject: Re: [hobbit] http network test
On Wednesday 30 January 2008 01:03:26 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.
Not per-test or per-host, it is a global timeout, which you can set as an option to bbtest-net, which is documented in bbtest-net's man page, just add it to the bbtest task in hobbitlaunch.cfg.
However, per-test or per-host or per-host-test timeout limits would be nice ....
Regards, Buchan
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
On Wednesday 30 January 2008 10:55:17 Thangappandi, Arun (Ge Money, consultant) wrote:
Hi,
Please let me know how to set the per-test or per-host or per-host-test timeout limits.
As implied by my previous reply, it is currently impossible. Please read the reply again.
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. :)
-- Kindest Regards, Anna Jonna Ármannsdóttir, %& A: Because people read from top to bottom. Unix System Aministration, Computing Services, %& Q: Why is top posting bad? University of Iceland.
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.
Regards, Buchan
Hi all,
why not consider urlplus.pl - http://www.trantor.org/theshire/doku.php/monitors:urlplus ?
Regards.
Massimo Morsiani Information Technology Dept.
Gilbarco S.p.a. via de' Cattani, 220/G 50145 Firenze, Italy tel: +39-055-30941 fax: +39-055-318603 email: massimo.morsiani at gilbarco.com web: http://www.gilbarco.it
-----Original Message----- From: Buchan Milne [mailto:bgmilne at staff.telkomsa.net] Sent: mercoledì 30 gennaio 2008 10.36 To: hobbit at hswn.dk Cc: Anna Jonna Armannsdottir Subject: Re: [hobbit] http network test
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.
Regards, Buchan
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
This message (including any attachments) contains confidential
and/or proprietary information intended only for the addressee.
Any unauthorized disclosure, copying, distribution or reliance on
the contents of this information is strictly prohibited and may
constitute a violation of law. If you are not the intended
recipient, please notify the sender immediately by responding to
this e-mail, and delete the message from your system. If you
have any questions about this e-mail please notify the sender
immediately.
On Jan 30, 2008 3:40 AM, Morsiani, Massimo <massimo.morsiani at gilbarco.com> wrote:
Hi all,
why not consider urlplus.pl - http://www.trantor.org/theshire/doku.php/monitors:urlplus ?
I'm already considering that, as it's substantially similar to the bash scripts I use right now. I'll probably have to write some scripts anyway, as they want to drill down several levels into the websites. I was just hoping that the simple grab-a-page-and-time-it requests could be handled by Hobbit.
Ralph Mitchell
On Wed, Jan 30, 2008 at 10:30 AM, Ralph Mitchell <ralphmitchell at gmail.com> wrote:
On Jan 30, 2008 3:40 AM, Morsiani, Massimo <massimo.morsiani at gilbarco.com> wrote:
Hi all,
why not consider urlplus.pl - http://www.trantor.org/theshire/doku.php/monitors:urlplus ?
Is that still the only option? There is no host specific timeout feature available yet?
I'm already considering that, as it's substantially similar to the bash scripts I use right now. I'll probably have to write some scripts anyway, as they want to drill down several levels into the websites. I was just hoping that the simple grab-a-page-and-time-it requests could be handled by Hobbit.
Ralph Mitchell
-- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
On Fri, Feb 6, 2009 at 3:34 PM, Asif Iqbal <vadud3 at gmail.com> wrote:
On Wed, Jan 30, 2008 at 10:30 AM, Ralph Mitchell <ralphmitchell at gmail.com> wrote:
On Jan 30, 2008 3:40 AM, Morsiani, Massimo < massimo.morsiani at gilbarco.com> wrote:
Hi all,
why not consider urlplus.pl - http://www.trantor.org/theshire/doku.php/monitors:urlplus ?
Is that still the only option? There is no host specific timeout feature available yet?
I don't think anything like that was introduced before December. I haven't followed development closely after that.
Ralph Mitchell
On mið, 2008-01-30 at 11:35 +0200, Buchan Milne wrote:
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.
Quite true. :) Maybe it is possible to create a timeouthttp similar to the badhttp specifier. I think the badhttp specifier interfaces to the alert module. I do not know the source well enough to know if the test module(s) already have an interface that might allow this.
-- Kær kveðja, Anna Jonna Ármannsdóttir, %& A: Because people read from top to bottom. Unix Kerfisstjórn, Reiknistofnun HÍ %& Q: Why is top posting bad?
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
participants (6)
-
annaj＠hi.is
-
arun.thangappandi＠ge.com
-
bgmilne＠staff.telkomsa.net
-
massimo.morsiani＠gilbarco.com
-
ralphmitchell＠gmail.com
-
vadud3＠gmail.com