[toc] RabbitMQ web management page (RabbitMQ) RabbitMQ web management page (RabbitMQ web management page)

1. An overview

First, the Web admin page should look something like this:

First, there are six tabs:

  1. Overview: Provides an Overview of RabbitMQ. If it is a cluster, you can also view the nodes in the cluster. Everything, including RabbitMQ port mapping information, can be viewed in this TAB.
  2. Connections: This TAB shows producers and consumers connected to RabbitMQ.
  3. Could you tell me more about the relationship between Channels?
  4. Exchange: Displays information about all switches.
  5. Queue: Displays all Queue information.
  6. Admin: All user information is displayed here.

In the upper right corner is the page refresh time, which is every 5 seconds by default, showing all Virtual hosts.

This is an overview of the entire admin page, so let’s take a look at each one.

2. Overview

Overview includes the following function modules:

Respectively is:

The Totals:

Total contains number of messages ready for consumption, number of messages to be confirmed, total number of messages and various processing rates of messages (send rate, confirm rate, write to disk rate, etc.).

Nodes:

Nodes are the machines on which RabbitMQ runs, the Nodes of a cluster.

Click on each node to view detailed information about the node.

Churn the statistics:

Connection, Channel and Queue creation/closure rates.

Ports and contexts:

This displays port mapping information and Web context information.

  • 5672 is the RabbitMQ communication port.
  • 15672 is the port of the Web management page.
  • 25672 is the cluster communication port.

Export definitions && Import definitions

The last two import and export some configuration information of the current instance:

3. Connections

This shows the information about the current connection to RabbitMQ, whether it is the message producer or the message consumer, as soon as the connection is made.

Note that AMQP 0-9-1 refers to the version number of the AMQP protocol.

The meanings of other attributes are as follows:

  • User name: indicates the User name used for the current connection.
  • State: indicates the current connection status. Running indicates that the connection is running. Idle Indicates idle.
  • SSL/TLS: Indicates whether SSL is used for connection.
  • Channels: The total number of Channels created by the current connection.
  • From Client: data packets sent per second.
  • To Client: Packets received per second.

Click on the connection name to view the details of each connection.

In details, you can view the number of channels for each connection and other details. You can also forcibly close a connection.

4. Channels

This is where the channel information is displayed:

So what is a channel?

A connection (IP) can have multiple channels, as shown in the figure above. There are two connections, but there are 12 channels in total.

A connection can have multiple channels, which are implemented through multiple threads. Normally, we create queues, switches, and so on in channels.

The producer’s channel is usually closed immediately; Consumers are always listening, and channels are almost always there.

The meanings of the preceding parameters are as follows:

  • Channel: indicates the Channel name.
  • User name: indicates the User name used to log in to the channel.
  • Model: indicates the channel confirmation mode. C indicates confirm. T stands for transaction.
  • State: indicates the current status of the channel. Running indicates that the channel is running. Idle Indicates idle.
  • Unconfirmed: indicates the total number of messages to be confirmed.
  • Prefetch: Prefetch represents the maximum number of unacknowledged messages that each consumer can handle. It is simply used to specify how many messages a consumer can fetch from RabbitMQ at a time and cache them in RabbitMQ. Once the consumer’s buffer is full, RabbitMQ will stop sending new messages to the consumer until it sends an ACK. In general, the consumer is responsible for processing messages, ack messages, and RabbitMQ will deliver messages as long as the number of unAcked messages is less than prefetch * consumers.
  • Unacker: Total number of messages to be ack.
  • Publish: Rate at which the message producer sends messages.
  • Confirm: Indicates the rate at which the message producer confirms the message.
  • Unroutable (DROP) : Indicates an unreceived message that has been deleted.
  • Deliver/GET: The rate at which message consumers get messages.
  • Ack: Rate at which message consumers ack messages.

5. Exchange

This is where switch information is displayed:

Various information about the switch is displayed here.

Type Indicates the switch Type.

Features has two values D and I.

D stands for switch persistence, which stores the properties of the switch inside the server. After an accident or shutdown of the MQ server, restarting RabbitMQ does not require manual re-establishment or code execution. The switch will be set up automatically, which means that the switch will always exist.

I indicates that the switch cannot be used by message producers to push messages, but is only used for binding between switches.

Message Rate in Indicates the rate of incoming messages. Message Rate out Indicates the rate of outgoing messages.

Click Add a New Exchange below to create a new switch.

6. Queue

This TAB is used to display message queues:

The meanings are as follows:

  • Name: indicates the message queue Name.
  • Type: Indicates the Type of message queue. In addition to classic, there is another message Type called Quorum. The two differences are shown below:

  • Features: indicates the Features of message queues. D indicates message queue persistence.
  • State: indicates the status of the current queue. Running: indicates that the queue is running. Idle Indicates idle.
  • Ready: Indicates the total number of messages to be consumed.
  • Unacked: Indicates the number of messages to be answered.
  • Total: indicates the Total number of messages Ready+Unacked.
  • Incoming: indicates the rate of incoming messages.
  • Deliver/GET: Indicates the rate at which messages are fetched.
  • Ack: Indicates the rate at which the message is answered.

Click Add a new Queue below to Add a new message queue.

Click the name of each message queue to enter the message queue. After entering the message queue, you can perform further operations on the message queue, such as:

  • Bind message queues to a switch.
  • Send a message.
  • Get a message.
  • Move a message (requires plug-in support).
  • Delete the message queue.
  • Clears messages in the message queue.
  • .

The diagram below:

7. Admin

Here are some user management operations, as shown below:

The meanings of each attribute are as follows:

  • Name: indicates the user Name.
  • Tags: Indicates the character Tags. Only one can be selected.
  • Can Access virtual hosts: indicates the virtual host that Can be accessed.
  • Has password: indicates whether the user Has a password.

Two common operations are managing users and virtual hosts.

Click “Add a user” below to Add a new user. When adding a user, you need to set Tags for the user, which is actually the user role, as follows:

  • None:

The Management Plugin cannot be accessed

  • Management:

Queues can be shared by AMQP users. Queues can be shared by AMQP users. Queues can be shared by AMQP users. View “global” statistics about your own virtual hosts, including the activities of other users in those virtual hosts

  • Policymaker:

Management can do anything to view, create, and delete policies and parameters to which its own virtual hosts belong

  • Monitoring:

List all virtual hosts, This includes virtual hosts that they cannot log in to. Look at connections and channels of other users. Look at node-level data such as clustering and memory usage to see what all virtual hosts really are Global statistics of the

  • Administrator:

Policymaker and Monitoring Anything you can do Create and delete virtual hosts View, create, and delete users View Create and delete permissions Close connections for other users

  • Impersonator

Simulator, unable to log in to admin console.

In addition, here can also carry on the virtual host virtual host operation, but about the virtual host I plan to write another article and we discuss in detail, here will not expand.

Nodule 8.

Well, today is a primer on the information that RabbitMQ’s Web management page displays.