Re: URL content checking [Vote]

[Jan-Henrik Haukeland]

Thanks for the +1 vote guys, and Michael's considerations are noted.
However we are going to add this feature and I can take the
implementation responsibility, unless someone else is very keen on doing
this? In that case I'll happily give it away :) If I'll end up doing it
then I cannot promise any release date as my schedule is tight as usual
and this is not high up on my priority list. Anyway sometime before Xmas
should be a reasonable estimate.

Addendum to the proposal sent in a previous mail. I think I'll go with
the original short-form I suggested which is simply. 

check URL http://www.chofoundation.org/
check URL http://www.turingstudio.com/
check URL http://www.tildeslash.com/

In this short-form alert is implied and sent if the check fails. A
longer version would be:

check URL http://blabla/foobar
  [add header "Set-Cookie: Customer=WILE_E_COYOTE; Path=/acme"]
  if failed content {contains|notcontains|equals|notequal}"^regex$"  
     [with checksum 8f7f419955cefa0b33a2ba316cba3659]
  then alert

There will be changes during the implementation, but this is the start-
plan. Another thing, there must be content size limitations, if regex is
used, because regex need to compare the content in a buffer i.e. in
memory.


On Thu, 2004-12-02 at 09:59 -0800, Rory Toma wrote:
> +1 for me.
> 
> <quote who="Jan-Henrik Haukeland">
> > This is a nice feature and I propose that we try to implement this in
> > monit.  We need to vote, if we should add this feature in monit. So
> > please cast your votes!
> >
> > Here is mine +1
> >
> > The proposal is as follows:
> > ------------------------------------
> > Add content monitoring to monit  so the following requirements are meet:
> >
> > Check if a URL is up (responding)
> > Check if a URL does or does not contain a string
> >
> > The only protocol supported for URL testing is HTTP(S). We suggest the
> > following syntax in monit's control file for this new functionality:
> >
> > On Dec 2, 2004, at 9:06 AM, Martin Pala wrote:
> >
> >>  check host myhost with address 192.168.1.1
> >>     if failed url http://user:address@hidden:8080/index.php
> >>       [and content {contains|notcontains|equals|notequal}
> >> "^myregular*expression$"]
> >>       [with checksum 8f7f419955cefa0b33a2ba316cba3659]
> >>       then alert
> >
> > In addition I would like to suggest a short-form (not quite sure about
> > the syntax, only that a short-form would be nice):
> >
> >     check URL myURLCollection
> >             if failed urls [
> >                     http://user:address@hidden/foobar?querystring
> >                     http://user:address@hidden/foobar
> >                     http://blabla3.com/foobar?querystring
> >                     http://labla4.com/foobar?querystring
> >                     http://user:address@hidden/foobar
> >                     ....] # Space or newline separate url-entries
> >             then <action>
> >
> > The rationale for this varian is that if one should want to monitor
> > several hundreds of URLs it is less to write and you can group URLs
> > into collections. The URL-test should be conducted as follows,
> >     - Test all URLs in the list in one poll-session
> >     - If one or more URL failed, only send one and only one alert report
> > listing those URLs that failed.