[rabbitmq-discuss] RabbtMQ heart beat

Tue Jan 28 18:00:36 GMT 2014

I'd also recommend looking at the Aliveness test.  See the management API
for details:
http://hg.rabbitmq.com/rabbitmq-management/raw-file/default/priv/www/api/index.html

This is a very simple check that can be done from the load balancer
typically to see not only if the host is up, but also in a state that can
publish & consume messages.  You can also have the load balancer do a port
check on 5672 (by default port can be changed) but you will get lots of
errors in your rabbit log files about this.

Jason

On Mon, Jan 27, 2014 at 5:34 AM, Michael Klishin <mklishin at gopivotal.com>wrote:

>
> On 27 Jan 2014, at 15:27, Patrick Long <pat at munkiisoft.com> wrote:
>
> > What is the RabbitMQ specific test to see if the node is up and running?
> Is there a specific port the load balancer should ping?
>
> If you have management plugin [1] enabled, there is an HTTP API endpoint
> [2].
>
> Otherwise, you can connect with valid credentials, open a channel, close it
> and close the connection.
>
>
> 1. http://rabbitmq.com/management.html
> 2.
> http://hg.rabbitmq.com/rabbitmq-management/raw-file/rabbitmq_v3_2_3/priv/www/api/index.html
>
> MK
>
> Software Engineer, Pivotal/RabbitMQ
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>

-- 
Jason McIntosh
https://github.com/jasonmcintosh/
573-424-7612
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140128/b3488bbf/attachment.html>