Introduction to web management interface
1. Overview
connections: Both producers and consumers need to establish a connection with RabbitMQ before they can complete the production and consumption of messages. You can check the connection here
channels: Channel. After a connection is established, a channel will be formed, and the delivery of messages depends on the channel.
Exchanges: Switch, used to implement message routing
Queues: Queue, that is, message queue. Messages are stored in the queue, waiting for consumption, and then removed from the queue after consumption.
2. Admin user and virtual host management
The Tags option above is actually to specify the role of the user. The following options are available:
Super administrator(administrator)
You can log in to the management console, you can view all the information, and you can operate on users and policies.
Monitor(monitoring)
You can log in to the management console, and you can view the relevant information of the rabbitmq node (number of processes, memory usage, disk usage, etc.)
Strategy maker(policymaker)
You can log in to the management console, and you can manage the policy at the same time. But you cannot view the related information of the node (the part marked by the red box in the above figure).
General manager(management)
You can only log in to the management console, you cannot see node information, and cannot manage policies.
other
Unable to log in to the management console, usually ordinary producers and consumers.
-
Create virtual host
In order to allow users to work without interfering with each other, RabbitMQ added the concept of Virtual Hosts. In fact, it is an independent access path. Different users use different paths, each with its own queues and switches, which will not affect each other.
Enter the virtual machine settings interface:
