RabbitMQ Management is a plugin that can be enable for RabbitMQ. It gives a single static HTML page that makes background queries to the HTTP API for RabbitMQ. Information from the management interface can be useful when you are debugging your applications or when you need an overview of the whole system. If you see that the number of unacked messages starts to get high, it could mean that your consumers are getting slow. If you need to check if an exchange is working, you can try to send a test message.
A link to the RabbitMQ management interface can be
found on the details page for your hosted RabbitMQ solution,
your CloudAMQP instance.
If you have RabbitMQ installed on localhost, go to
to find the management page.
All the tabs from the menu are explained in this post. Screenshots from the views are shown for: Overview, Connections and channels, Exchanges, Queues and Admin - users and permissions. A simple example will also show how to set up a queue an exchange and add a binding between them.
In the prior posts Part 1: RabbitMQ for beginners - What is RabbitMQ?, the default virtual host, user and permissions were used in the examples. In this post different views in the management interface are shown and all the examples are still only working with the default values - still there are some important concept that are good to be familiar with.
The overview shows two charts, one for queued messages and one with the message rate. You can change the time interval shown in the chart by pressing the text (chart: last minute) above the charts. Information about all different statuses for messages can be found by pressing (?).
The total number of connections, channels, exchanges, queues and consumers for ALL virtual hosts the current user has access to.
Nodes show information about the different nodes in the RabbitMQ cluster (a cluster is a group of nodes i.e, a group of computers), or information about one single node if just one node is used. Here can information about server memory, number of erlang processes per node and other node-specific information be found. Info show i.e. further information about the node and enabled plugins.
Listening ports for different protocols can be found here. More information about the protocols will be found in a later part of RabbitMQ for beginners.
It is possible to import and export configuration definitions. When you download the definitions, you get a JSON representation of your broker (your RabbitMQ settings). This can be used to restore exchanges, queues, virtual hosts, policies and users. This feature can be used as a backup. Every time you make a change in the config, you can keep the old settings just in case.
A connection is a TCP connection between your application and the RabbitMQ broker. A channel is a virtual connection inside a connection.
RabbitMQ connections and channels can be in different states; starting, tuning, opening, running, flow, blocking, blocked, closing, closed. If a connection enters flow-control this often means that the client is being rate-limited in some way; A good article to read when that is happening can be found here.
The connection tab shows the connections established to the RabbitMQ server. vhost shows in which vhost the connection operates, the username the user associated with the connection. Channels tell the number of channels using the connection. SSL/TLS indicate whether the connection is secured with SSL.
If you click on one of the connections, you get an overview of that specific connection. You can view channels in the connection and data rates. You can see client properties and you can close the connection.
More information about the attributes associated with a connection can be found here in the manual page for rabbitmqctl, the command line tool for managing a RabbitMQ broker.
The channel tab show information about all current channels.
shows in which vhost the channel operates,
the user associated with the channel.
tells the channel guarantee mode. It can be in
confirm or transactional mode.
When a channel is in confirm mode, both the broker and the client
count messages. The broker then confirms messages as it handles them.
Confirm mode is activated once the
method is used on a channel.
If you click on one of the channels, you get a detailed overview of that specific channel. From here you can see the message rate on the number of logical consumers retrieving messages via the channel.
More information about the attributes associated with a channel can be found here in the manual page for rabbitmqctl, the command line tool for managing a RabbitMQ broker.
An exchange receives messages from producers and pushes them to queues. The exchange must know exactly what to do with a message it receives. All exchanges can be listed from the exchange tab. Virtual host shows the vhost for the exchange, type is the exchange type such as direct, topic, headers, fanout. Features show the parameters for the exchange (e.g. D stand for durable, and AD for auto-delete). Features and types can be specified when the exchange is created. In this list there are some amq.* exchanges and the default (unnamed) exchange. These are created by default.
By clicking on the exchange name, a detailed page about the exchange are shown. You can see and add bindings to the exchange. You can also publish a message to the exchange or delete the exchange.
The queue tab show the queues for all or one selected vhost.
Queues have different parameters and arguments depending on how they were created. The features column show the parameters that belong to the queue. It could be features like Durable queue (which ensure that RabbitMQ will never lose the queue), Message TTL (which tells how long a message published to a queue can live before it is discarded), Auto expire (which tells how long a queue can be unused for before it is automatically deleted), Max length (which tells how many (ready) messages a queue can contain before it starts to drop them) and Max length bytes (which tells the total body size for ready messages a queue can contain before it starts to drop them).
You can also create a queue from this view.
If you press on any chosen queue from the list of queues, all information about the queue are shown like in the pictures that follow below.
The first two charts include the same information as the overview, but it just shows the number of queued messages and the message rates for that specific queue.
Consumers show the consumers/channels that are connected to the queue.
A binding can be created between an exchange and a queue. All active bindings to the queue are shown under bindings. You can also create a new binding to a queue from here or unbind a queue from an exchange.
It is possible to manually publish a message to the queue from "publish message". The message will be published to the default exchange with the queue name as given routing key - meaning that the message will be sent to the queue. It is also possible to publish a message to an exchange from the exchange view.
It is possible to manually inspect the message in the queue. "Get message" get the message to you and if you mark it as "requeue", RabbitMQ puts it back to the queue in the same order.
A queue can be deleted by the delete button, and you can empty the queue by pressing purge.
From the Admin view it is possible to add users and change user permissions. You can set up vhosts, policies, federation and shovels. Information about shovels can be found here: https://www.rabbitmq.com/shovel.html and http://www.cloudamqp.com/docs/shovel.html. Information about federation can be found here: https://www.cloudamqp.com/blog/2015-03-24-rabbitmq-federation.html
This example show how you can create a queue "example-queue" and an exchange called example.exchange.
The exchange and the queue are connected by a binding called "pdfprocess". Messages published to the exchange with the routing key "pdfprocess" will end up in the queue.
A lot of things can be viewed and handled from the management interface and it will give you a good overview of your system. By looking into the management interface, you will get a good understanding about RabbitMQ and how everything is related.
Please email us at firstname.lastname@example.org if you have any suggestions or feedback.