Re: URL content checking [Vote]

[alex black]

if I offer a bounty could it happen a liiiitle faster ? :)

> 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

very cool.

> 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.

A couple hundred k seems reasonable? Or do you mean to suggest an 
adjustable buffer size?

_very_ exciting :)




_a



> 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.
>
>
>
> _______________________________________________
> monit-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/monit-dev

--
alex black
founder
the turing studio, inc.

2600 10th street, suite 635
berkeley, ca 94710

mail: address@hidden
url : http://www.turingstudio.com
tel : 510.666.0074
fax : 510.666.0093