Hi Craig,
And yes, I'm for script-based checks ;-)
Willy
On Fri, May 15, 2009 at 05:38:38PM +0200, Craig wrote:
> Hi,
>
> I'd really like to do multiple and advanced checks on a backend, but it
> does not seem to be possible currently. Shoot^H^H^H^H^HCorrect me, if I
> missed it in the manual...
>
> It would be cool if something like this worked:
>
> option httpchk CHECK1 GET /service1.jsp HTTP/1.1\r\nHost:\ www.host.com
> option httpchk CHECK2 GET /service2.html HTTP/1.1\r\nHost:\ www.host.com
> expect "my text"
> option httpchk CHECK3 HEAD /service3.jsp HTTP/1.1\r\nHost:\ www.host.com
> notexpect "HTTP/1.1 302"
>
> You could define extra keywords like "expect","notexpect" and the
> Service would only be considered up, if the returned text contains (or
> does not contain) a certain textpattern, (custom) Host-Headers could be
> checked, too.
>
> Checks would be defined by a name, so that this would be possible:
>
> server one 192.168.0.1:80 weight 100 check CHECK1 inter 1000 fall 1 rise
> 6 check CHECK2 inter 5000 fall 1 rise 1
>
> CHECK1 would be a service that is a bit slowish if it is being restarted
> (e.g. some Tomcat Application), but is important for your site and you
> do not wish users to see any error in that application.
> CHECK2 could be some static web page.
>
> It is surely possible to do multiple httpchks with ACLs and some
> fuddling, but I think defining multiple backends is not that nice for
> this task. Any other opinions about this?
>
>
> Best regards,
>
> Craig
Received on 2009/05/17 09:43
This archive was generated by hypermail 2.2.0 : 2009/05/17 09:45 CEST