[rabbitmq-discuss] Monitoring rabbitmq

Mark Steele msteele at beringmedia.com
Thu Jan 28 16:19:34 GMT 2010

I suppose it depends on the level of certainty one is looking for. Checking
that the port is open doesn't mean that rabbit is capable of
receiving/sending messages (eg: SSL listener bug, etc...). I guess the only
real way to monitor would  be to connect, publish, and consume.

On Thu, Jan 28, 2010 at 7:00 AM, Matthew Sackman <matthew at lshift.net> wrote:

> Hi Mark,
> On Tue, Jan 26, 2010 at 03:42:39PM -0500, Mark Steele wrote:
> > I'm trying to find a good way to monitor rabbit for inclusion in an HA
> > cluster (pacemaker/corosync).
> >
> > Does anyone have a good resource agent already created for such a
> purpose?
> We don't have one off the shelf, though several of our clients are using
> RabbitMQ with pacemaker and heartbeat, and presumeably have written similar
> such scripts.
> Rather than using the rabbitmq-multi script to monitor (which should be
> fine), we tend to suggest just checking to see if the port is open (by
> default 5672, but that can change on configuration). How does pacemaker
> monitor something like apache? - again there would be the option of
> either checking the port is open, or using some sort of status
> monitoring. I don't know whether one is generally preferred to the
> other?
> Matthew
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

Mark Steele
Director of development
Bering Media Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100128/aa09e4d2/attachment.htm 

More information about the rabbitmq-discuss mailing list