Morning all,
One request on this matter that I'd like to suggest (perhaps in a
future release) is individual HTTP test timeout settings. My customer
needs to monitor a few external URL's that we rely on for various
things. One in particular has frequent problems.
So we upped the default timeout on bbtest-net to 20s, which helped
but it's still not really enough, and I'm reluctant to increase it
further the board for just one bad egg. If there's a workaround to
this particular problem, I'd be happy to hear suggestions.
Thanks and Regards,
Richard.
On 17 Nov 2006, at 08:14, Henrik Stoerner wrote:
On Thu, Nov 16, 2006 at 09:31:53AM -0600, James Wade wrote:
After adding the additional URL's, I started getting Timeouts across the board. If I look at the graph for old URL's, it shows the graph increasing at the same time I implemented all the new URL's yesterday. ie. I went from about 30 to 60 URL's.
By default, Hobbit runs lots of network tests in parallel. It has been seen that this can overwhelm either a server or some of your network infrastructure; or just generate enough traffic that packets are
dropped on their way to the Hobbit server.60 URL's aren't a whole lot, though.
Still, you can try lowering the number of concurrent tests that Hobbit performs. The "--concurrency=N" option for bbtest-net does that
(goes in hobbitlaunch.cfg). See the bbtest-net(1) man-page.Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Richard Leyton - richard at leyton.org http://www.leyton.org