I was doing pretty much exactly that for my recently-ex employer.
There's a tool called 'curl' which is very good at getting web pages. You would do something like this in bash:
curl -s -S -L --max-time 5 -o /tmp/page.html http://server.domain.com/
if [ $? -ne 0 ]; then
# something went wrong. the return code tells the actual error
COLOR=red
MESSAGE="page fetch failed. curl error $?"
else
COLOR=green
MESSAGE="page fetch successful"
fi
then use server/bin/bb to send the report to the server. I generally saved the html somewhere in the web server's document tree, then added a link to the report so that Midrange Operations could click through and see the actual page the server returned.
Curl can also tell you how long the transaction took, which you could add to the report in a format that xymon could pick up for graphing.
Ralph Mitchell
On Fri, Feb 27, 2009 at 10:14 AM, Jason Hand <jason at hands4christ.org> wrote:
I cannot find anything mentioning if Hobbit/Xymon can test how long an HTTP or HTTPS page takes to respond and alert on that. In other words, if a site is in a hung state so that it still technically "responds" but it takes 5 seconds for the page to respond how does Hobbit/Xymon handle that? I want to make sure that if a site that we are monitoring takes longer than a couple of seconds to load we are alerted,
Do any of you do a test like that and how are you doing it?
Thanks, Jason
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk