You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RabbitMQ has an aliveness check that is a lot more reliable than the existing connection check used in this library. I use it a custom check on a similar health checker called django-watchman. It has caught several incidences that the connection check (what we originally used) did not.
That API check "Declares a test queue, then publishes and consumes a message. Intended for use by monitoring tools."
But you need to parse the URL or have the users declare the vhost/url separately. I used this snippet if that helps:
Hi @JBKahn, thanks for the suggestion. Don't mind improving the check, but I am not using RabbitMQ myself right now, so I'd appreciated a pull request and would be delighted to review it. Best Joe
I'm not using RabbitMQ either right now, swapped to SQS and I've not even installed this library before. I figured I'd just offer up a suggestion, I'll circle back when I have some extra time but if anyone uses this and wants to work on it before I get there. Feel Free.
RabbitMQ has an aliveness check that is a lot more reliable than the existing connection check used in this library. I use it a custom check on a similar health checker called django-watchman. It has caught several incidences that the connection check (what we originally used) did not.
That API check "Declares a test queue, then publishes and consumes a message. Intended for use by monitoring tools."
But you need to parse the URL or have the users declare the vhost/url separately. I used this snippet if that helps:
The text was updated successfully, but these errors were encountered: