[rabbitmq-discuss] Queue inspector.

Matthias Radestock matthias at lshift.net
Mon Nov 5 18:20:14 GMT 2007


matt wrote:
> First off, I want to say how much we love amqp and rabbitMQ!

Thank you. It is always nice to hear from real users.

> We've ( meez.com) been using it in our production environment (when
> it was alpha) for about 6 months now I think.
> In brief, we use rabbitMQ as a way of communicating with our
> rendering cluster.  We have user facing tomcat servers that provide a
> way of giving the user options to create an avatar.  Upon save, we
> send export requests via rabbitMQ and they're picked up by nodes in
> the export cloud.  Upon success of the rendered images, a
> notification is sent back and the user is notified that the exports
> were successful.

That is a pretty neat use case, and it is good to hear that RabbitMQ
worked out well for you.

> the big immediate need we're looking for is a way to see how much is
> being queued up on the rabbitMQ cluster.  That way, we can
> programatically bring EC2 nodes up or take then down based on need.
> I know that this is in the pipeline - but is there *any* way of doing
>  this now and/or is there something that could be easily added to 
> support this?

queue.declare-ok, the result of a queue.declare operation, in one of its 
fields contains the number of messages in the queue. This is part of the 
amqp 0-8 spec and implemented by RabbitMQ. In combination with 
queue.declare's passive flag it allows you to determine the length of 
existing queues.

If you are using the RabbitMQ Java client, check out

This is only a very limited interface - you need to know the names of 
queues and you only get a report on the number of messages, not their 
storage size etc - but perhaps that is sufficient for your needs?

Hope this helps, and thank you for using RabbitMQ,


More information about the rabbitmq-discuss mailing list