Re: {bb} http content verification

[William Groombridge <billg@hebdomag.com>]

I use MRTG to graph the response time of one of my web sites.  It's not
linked to BB in any way, but I don't really care if it alerts me that the
response time is too long, because BB will probably notify me of a lost
HTTP: connection or a CPU load issue, which is usually allways the cause of
slow response time for my web sites.

I would be as well interested in making sure that the 'right' content is
coming from my web server, but in most cases, if its not delivering the
right content, the server status is generallly not 200 at that point anyway.

YT,  Bill

At 09:54 AM 1/29/99 +0000, you wrote:
>Hi!,
>
>> First I wanted to say "Thank you, Sean" for the great functionality that bb
>> provides :)))
>
>I second that totally :~) , thanks Sean.
>
>Re Tin's question about content verification, and in addition to it,
>does anyone have (or know of) a script that can be linked with BB that
>measures webserver response times? , ie a feature that allows you to see
>ups & downs in time taken to retrieve a given web page?
>
>Any suggestions gratefully received,
>
>Thanks
>
>Neil Holmes
>
>
>>> I'm curious if we can do content verification with it. Most of our
sites are
>>> dynamically built from databases and I'd like to know if the right content
>>> is showing. Any ideas ? I guessed it would be some modification of
>>> bb-network.sh ...but didn't have much time to dig deeper. Maybe you guys
>>> have experience with this.
>
>> Interesting.  The problem I could see here is twofold:
>
>> 1.    How do you know what's coming back is correct?
>> 2.    The current http tests don't return a whole page.
>
>> > In response to #1, I don't know how you could tell your sites
>> > are OK.  Simple logic would dictate that you 'grep' for some
>> > keyword, or something.  provided you can determine an OKness
>> > test, bb-network.sh has an HTTP test around line 365:
> 
>> I have a number of sites that I also need to make sure that the contents
>> are showing up ok.  With regard to #1 above, I would suggest taking a
>> snapshot of the page (with the wanted content), then do a "fuzzy" diff with
>> subsequent tests.  Something like a diff command that understands that we
>> only want to compare lines 3 through 15, then lines 20 through 30, ignoring
>> differences in the rest of the file.
> 
>> It might be possible to do this by writing a Perl wrapper around diff.
>> I'll take a crack at it when I get some time (yeah, right :-)).
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  Please send mail for the mailing list to: bb@taex001.tamu.edu
>  To [un]subscribe to this list, send e-mail to majordomo@taex001.tamu.edu
>     with [un]subscribe bb in the BODY of the message.
>  Please contact the mailing-list-owner as: bb-owner@taex001.tamu.edu
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  Please send mail for the mailing list to: bb@taex001.tamu.edu
  To [un]subscribe to this list, send e-mail to majordomo@taex001.tamu.edu
     with [un]subscribe bb in the BODY of the message.
  Please contact the mailing-list-owner as: bb-owner@taex001.tamu.edu