This can help u more easily view what the healthcheck middleware can
also show (especially in detailed mode); it can show thread stacks and
such which can be useful for debugging stuck servers and such (similar
in concept to apache mod_status).
https://review.openstack.org/#/c/311482/
Run the
...@andybotting.com>>
Date: Friday, April 29, 2016 at 10:49 AM
To: Simon Pasquier mailto:spasqu...@mirantis.com>>
Cc:
"openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>"
mailto:openstack-operators@lists.openstack.org>>
Subject: Re: [Ope
Yup, that healthcheck middleware was made more advanced by me,
If u need to do anything special with it, let me know and I can help
make that possible (or at least instruct what might need changed to do
that).
Simon Pasquier wrote:
Hi,
On Thu, Apr 28, 2016 at 5:13 AM, Andy Botting mailto:a.
Hi Simon,
> There's a healthcheck oslo.middleware plugin [1] available. So you could
> possibly configure the service pipeline to include this except it won't
> exercise the db connection, RabbitMQ connection, and so on. But it would
> help if you want to kick out a service instance from the load
Hi,
On Thu, Apr 28, 2016 at 5:13 AM, Andy Botting wrote:
> We're running our services clustered behind an F5 loadbalancer in
> production, and haproxy in our testing environment. This setup works quite
> well for us, but I'm not that happy with testing the health of our
> endpoints.
>
> We're cu
We're running our services clustered behind an F5 loadbalancer in
production, and haproxy in our testing environment. This setup works quite
well for us, but I'm not that happy with testing the health of our
endpoints.
We're currently calling basic URLs like / or /v2 etc and some services
return a
