RocketMQ series: Detailed explanation of the use of rocketmq operation and maintenance console

After setting up the RocketMQ console, open http://{your ip}:8080 directly in the browser

By default, you will enter the cockpit (dashboard).

Overview

The overall horizontal menu is divided into eight parts:

Operation and maintenance : mainly setting up nameserver and configuring vipchannel

Cockpit : The dashboard of the console. You can view the number and trends of messages by broker and topic respectively.

Cluster : The cluster status of the entire RocketMq, including fragmentation, number, address, version, TPS of message production and message consumption, etc. This can be used as a data indicator when doing performance testing.

Topic : Topic, you can add/update topic; also view topic information, such as status, routing, consumer management and sending messages, etc.

Consumer : You can view/create a new consumer group in the current broker, including consumer information and consumption progress.

Producer : You can view the producer group under the production group in the current broker, including producer information and producer status.

Message : You can query specific messages according to topc, messageID, and messageKey.

User Center : Switching language is related to login (login requires opening the corresponding configuration in the console configuration, and no login is required by default)

The most commonly used are cluster , topic , consumer and message

Let’s look at each part separately.

Operation and maintenance

 As mentioned just now, there are only two functions in operation and maintenance.

  • set nameserver
  • Open/close vipcannnel

Set nameserver: You can add multiple nameserver addresses to the input box. By default, the nameserver configuration in the console startup configuration is read. If a new nameserver node is added to the rockermq cluster, it can be dynamically configured here and the update will take effect.

Open/close vipchannel: The default is false here, vipchannel is aimed at the priority of the topic, which is equivalent to some topics that can go to v when processing messages

Guess you like

Origin blog.csdn.net/WXF_Sir/article/details/122174648