[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] HTTP response time test
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] HTTP response time test
- From: Ralph Mitchell <ralphmitchell (at) gmail.com>
- Date: Fri, 27 Feb 2009 10:46:39 -0600
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=cbRtjeiilXlsgxfLf1moLflKSVT83YJ27Ck1Y2HcgfQ=; b=VNrPW7nK1d7pw3u7OjxKJLYpX7NJm6MffIdd5TuCNxadU4l/ON8I4ro1zJ+If3RyfA GpstZatx28UDEU5lvXLhD/ugQ4Tq5koFRfPiYkcvIB1h+vs9izk650GhTJoyXgyDlRXw 6fjJOOcasu3ZSVAKOfB8eNRTntKnw8pntBkUs=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=hRDmUkCKLSK9gcbZBfAGvO1FdImpWo7zb1kJwv34+jS/Jllhfy1WRQHLyt9Nc2x8kU P7DaZTyJByajzzcyO/QLkF7iNh49i/iFjZ7dbZu8CZUAnl1sLgWMekdEfa2bRdylTFqn PnXItw2N5m6NujjvV118MLwsA8n1yYzt8jwzY=
- References: <D305723103FCAF4D995BD70F9DC9ABFF850779 (at) unam-exch1.unameits.com> <EF3D0825670B0F498B6B5C93AD760C8A04E224BF (at) vcommail3.voicecom.com> <49A79C32.4010700 (at) unil.ch> <961092e10902270647n16e0f94cha518709c4727b0c9 (at) mail.gmail.com> <9B3FA700-2633-4483-A4AB-52C4DA5F12F1 (at) hands4christ.org>
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
>
>
>