The use of RABBITMQ trace logs and its doubts

RabbitMQ The default log is similar to the client "Accpet/close" and other information, for the exception or trace the internal structure of the message is more troublesome.

However, MQ has a rabbitmq_tracing plug-in, after installing the plugin in the Console Management tab page, you can see a trace of the menu.

One of the most important is to understand the format of pattern. General to trace the message will involve two parts: there is no receipt, there is no issue to go. The format of the packet capture record is as follows:

But to catch a queue of the release or consumption test many times, always feel that this pattern is very vague. At night and carefully check the plugin's official website, find the following:

The Firehose publishes messages to the topic Exchange amq.rabbitmq.trace with

Routing key either "publish. Exchangename", for messages entering the broker, or"deliver. QueueName", for messages leaving the broker;
That is to catch publish follow exchangename walk, catch consumption followed QueueName walk.

Https://www.rabbitmq.com/firehose.html

The use of RABBITMQ trace logs and its doubts