Dump messages from a RabbitMQ queue to files, without affecting the queue.
Precompiled binary pacakges can be found on the releases page.
If you have Go installed, you can install rabbitmq-dump-queue from source by running:
go get github.com/dubek/rabbitmq-dump-queue
To dump the first 50 messages of queue incoming_1 to /tmp:
rabbitmq-dump-queue -url="amqp://user:password@rabbitmq.example.com:5672/" -queue=incoming_1 -max-messages=50 -output-dir=/tmp
This will create the files /tmp/msg-0000, /tmp/msg-0001, and so on.
The output filenames are printed one per line to the standard output; this
allows piping the output of rabbitmq-dump-queue to xargs or similar utilities
in order to perform further processing on each message (e.g. decompressing,
decoding, etc.).
Running rabbitmq-dump-queue -help will list the available command-line
options.
In order to fetch messages from the queue and later return them in the original
order, rabbitmq-dump-queue uses a standard AMQP basic.get API
call without
automatic acknowledgements, and it doesn't manually acknowledge the received
messages. Thus, when the AMQP connection is closed (after all the messages
were received and written to files), RabbitMQ returns all the un-acked messages
(all the messages) back to the queue in their original order.
This means that during the time rabbitmq-dump-queue receives and saves the messages, the messages are not visible to other consumers of the queue. This duration is usually very short (unless you're downloading a lot of messages), but make sure your system can handle such a situation (or shut down other consumers of the queue during the time you use this tool).
Note that the same approach is used by RabbitMQ's management HTTP API (the
/api/queues/{vhost}/{queue}/get endpoint with requeue=true).
Github pull requests and issues are welcome.
rabbitmq-dump-queue is under the MIT License. See the LICENSE file for details.