Viewing Group Details

Last updated:2026-01-23 17:34:04

Viewing Group Details

Last updated: 2026-01-23 17:34:04

By viewing group details, such as the client connection relationship, subscription relationship, and consumption progress, you can comprehensively monitor the health status of the message production and consumption links, and quickly identify and locate key issues, such as consumption delay and client exceptions.
Operation Steps
1. Log in to the TDMQ for RocketMQ console.
2. In the left sidebar, choose Resource > Cluster, select a region, and click the ID of the target cluster to go to the cluster basic information page.
3. On the cluster basic information page, select the Group tab. In the group list, click the name of the target group to view group details.
Basic info
5.x Clusters
4.x Clusters
Parameter
Description
Group Name
Name of a group.
Creation Time
Time when a group is created.
Delivery Sequence
Sequence in which the server delivers messages to the consumer for consumption. Sequential delivery and concurrent delivery are supported, and concurrent delivery is the default method.
Sequential delivery: Messages that are associated logically are delivered to the same queue for serialized processing. This ensures that messages are consumed strictly in the sequence they were sent.
Concurrent delivery: Messages are delivered to multiple queues for parallel processing by multiple consumer threads. This maximizes system throughput and resource utilization, but cannot guarantee the message processing sequence.
Consumer Type
Method used by a client to obtain messages. The PUSH and PULL methods are supported.
PUSH: A long polling mechanism encapsulated within the client is used to simulate proactive message push by the server.
PULL: The application layer actively calls the client.
Total Heaped Messages
Total number of backlogged messages.
Parameter
Description
Group Name
Name of a group.
Creation Time
Time when a group is created.
Consumption Mode
The clustering or broadcast mode is used.
Clustering consumption: In the clustering consumption mode, each message only needs to be processed by any of the consumers in the cluster.
Broadcasting consumption: In the broadcasting consumption mode, each message is pushed to all registered consumers in the cluster to ensure that the message is consumed at least once by each consumer.
Protocol Type
Transmission Control Protocol (TCP) and Hypertext Transfer Protocol (HTTP) are supported.
Total Heaped Messages
Total number of backlogged messages.
Consumer Type
The options include ACTIVELY (the client actively pulls messages; pull mode) and PASSIVELY (the client waits for the server to push messages; push mode).
Client Connection
Parameter Name
Description
Client Address
IP address and port number of the server where the client resides. The port is a local port randomly opened by the client process and is used to communicate with the broker node over the network.
Host Name
Host name configured for the client server at the operating system level.
Client Type
It is available only for 5.x clusters. It identifies the role of a client, primarily the producer or consumer.
Client Language
Programming language used to develop the client, such as Java, CPP, GO, and DOTNET. TDMQ for RocketMQ supports multi-language clients.
Client Version
Version of the dependency library used by the TDMQ for RocketMQ client. Checking this field helps confirm whether the client version is compatible with the server or whether any known bugs exist.
Note:
Avoid using client versions with known risks. For details, see Client Risk Descriptions and Update Guide.
Message Heap
Number of backlogged messages. It is available only for 4.x clusters.
Operation
View details: You can view consumer details. For 4.x exclusive clusters, you can view queue information on the specific broker node subscribed to by the client, in addition to viewing the connection information and ID of the client.
View stack: You can view the stack of this client. You can also search for keywords above the stack to view stack information.
Subscription
Parameter Name
Description
Topic
Name of the topic that a group subscribes to.
Type
Type of a topic, including normal messages, ordered messages, delayed messages, and transactional messages. (For details about message types, see Message Types).
Heaped Messages
Number of messages under each topic among the messages backlogged in the current group.
Queue Quantity
Total number of queues under this topic. Queues are the smallest units for load balancing and parallel consumption in TDMQ for RocketMQ. A consumer will be assigned one or more queues for consumption.
Filter Condition
Filtering method used when consumers subscribe to messages.
TAG: Tags are set for messages to subscribe to messages with the same tag. It is the most commonly used method.
SQL92: SQL-like expressions are used for complex filtering on message properties (user properties).
Subscription Consistency
Check whether the subscription relationships of all consumer instances under this consumer group are consistent.
Consistent: All consumer instances have subscribed to the same topics and tags (or SQL expressions).
Inconsistent: At least one consumer instance has a different subscription relationship from others. This is a common cause of message loss or disorder, and the issue needs to be fixed. For details, see Subscription Relationship Consistency.
Operation
If no online client in the group subscribes to a topic, you can click Unsubscribe in the operation column to clear historical subscription relationship data and avoid the impact of historical dirty data.
Consumption progress: You can view the consumption progress only for 4.x exclusive clusters.
Parameter Name
Description
Topic
Topic to which a message belongs.
Broker Node
IP address of the broker server where the primary node of a queue is located.
Queue No.
ID of a message queue under this topic (starting from 0).
Consumer ID
Client ID of the consumer instance consuming messages in a queue. Generally, the format is IP@Process ID.
Consumer Offset
Start position of the next message to be consumed by a consumer instance in a queue.
Server Offset
It is also known as the broker offset or maximum offset. It indicates the position of the latest message in a queue stored on the broker server.
Heaped Messages
Number of unconsumed messages in a queue. The calculation formula is as follows: Number of backlogged messages = Server offset - Consumer offset. The number of backlogged messages can be sorted in descending order on the current page.
Latest Consumption Time
Timestamp of the last message successfully consumed from a queue. Message consumption in the queue may be stopped if there is a significant gap between this timestamp and the current time.

Was this page helpful?

You can also Contact Sales or Submit a Ticket for help.

Yes

Feedback

Parameter	Description
Group Name	Name of a group.
Creation Time	Time when a group is created.
Delivery Sequence	Sequence in which the server delivers messages to the consumer for consumption. Sequential delivery and concurrent delivery are supported, and concurrent delivery is the default method. Sequential delivery: Messages that are associated logically are delivered to the same queue for serialized processing. This ensures that messages are consumed strictly in the sequence they were sent. Concurrent delivery: Messages are delivered to multiple queues for parallel processing by multiple consumer threads. This maximizes system throughput and resource utilization, but cannot guarantee the message processing sequence.
Consumer Type	Method used by a client to obtain messages. The PUSH and PULL methods are supported. PUSH: A long polling mechanism encapsulated within the client is used to simulate proactive message push by the server. PULL: The application layer actively calls the client.
Total Heaped Messages	Total number of backlogged messages.

Parameter Name	Description
Client Address	IP address and port number of the server where the client resides. The port is a local port randomly opened by the client process and is used to communicate with the broker node over the network.
Host Name	Host name configured for the client server at the operating system level.
Client Type	It is available only for 5.x clusters. It identifies the role of a client, primarily the producer or consumer.
Client Language	Programming language used to develop the client, such as Java, CPP, GO, and DOTNET. TDMQ for RocketMQ supports multi-language clients.
Client Version	Version of the dependency library used by the TDMQ for RocketMQ client. Checking this field helps confirm whether the client version is compatible with the server or whether any known bugs exist. Note: Avoid using client versions with known risks. For details, see Client Risk Descriptions and Update Guide.
Message Heap	Number of backlogged messages. It is available only for 4.x clusters.
Operation	View details: You can view consumer details. For 4.x exclusive clusters, you can view queue information on the specific broker node subscribed to by the client, in addition to viewing the connection information and ID of the client. View stack: You can view the stack of this client. You can also search for keywords above the stack to view stack information.

Parameter Name	Description
Topic	Name of the topic that a group subscribes to.
Type	Type of a topic, including normal messages, ordered messages, delayed messages, and transactional messages. (For details about message types, see Message Types).
Heaped Messages	Number of messages under each topic among the messages backlogged in the current group.
Queue Quantity	Total number of queues under this topic. Queues are the smallest units for load balancing and parallel consumption in TDMQ for RocketMQ. A consumer will be assigned one or more queues for consumption.
Filter Condition	Filtering method used when consumers subscribe to messages. TAG: Tags are set for messages to subscribe to messages with the same tag. It is the most commonly used method. SQL92: SQL-like expressions are used for complex filtering on message properties (user properties).
Subscription Consistency	Check whether the subscription relationships of all consumer instances under this consumer group are consistent. Consistent: All consumer instances have subscribed to the same topics and tags (or SQL expressions). Inconsistent: At least one consumer instance has a different subscription relationship from others. This is a common cause of message loss or disorder, and the issue needs to be fixed. For details, see Subscription Relationship Consistency.
Operation	If no online client in the group subscribes to a topic, you can click Unsubscribe in the operation column to clear historical subscription relationship data and avoid the impact of historical dirty data.

tencent cloud

Operation Steps