Monitoring Metric Description
Last updated:2026-01-27 11:25:32
TDMQ for RocketMQ provides a comprehensive and multi-dimensional monitoring metric system, covering various dimensions, such as clusters, topics, and groups, helping you understand the resource operation status in real time. This document describes the meanings of various monitoring metrics for TDMQ for RocketMQ. Through these metrics, you can quickly master the health status of resources, such as instances, and determine whether specification adjustment and other Ops operations need to be performed to ensure stable operation.
Metric Description
The following table describes all monitoring metrics provided by TDMQ for RocketMQ. You can configure monitoring and alarm policies based on your actual business requirements.
Classification | Metric Name | Unit | Description |
Billing metrics | Total Cluster TPS | Count/s | Maximum number of API calls per minute in a cluster (sum of API calls for producing and consuming messages, which is calculated based on billing rules). Traffic throttling is triggered if the value exceeds the limit. |
| Production TPS | Count/s | Maximum number of API calls per minute for producing messages in a cluster (calculated based on billing rules). Traffic throttling is triggered if the value exceeds the limit. |
| Consumption TPS | Count/s | Maximum number of API calls per minute for consuming messages in a cluster (calculated based on billing rules). Traffic throttling is triggered if the value exceeds the limit. |
| Message Storage Space | GBytes | Space occupied by stored messages in a cluster. |
| Elastic TPS | Count/s | Number of API calls that exceeds the computing specifications limit (calculated based on billing rules) after the computing elasticity switch is enabled. It is supported only in the Pro and Platinum editions. |
| Throttled Production TPS | Count/s | When the number of API calls exceeds the cluster limit (calculated based on billing rules), the server enables traffic throttling. |
| Throttled Consumption TPS | Count/s | When the number of API calls exceeds the cluster limit (calculated based on billing rules), the server enables traffic throttling. |
Production metrics | Produced Messages | Count/s | Change in the average number of messages produced per minute in a cluster. |
| Production Traffic | MBytes/s | Change in the total traffic for producing messages in a cluster. |
| Producer Count | Count | Number of producer clients in a cluster. |
| Production Success Rate | % | Change in the message production success rate in a cluster. Only 5.x clients can collect this metric. |
| Avg Message Production Duration (Message sending RT) | ms | Duration for a successful call to the message sending API using the software development kit (SDK), that is, the RT for message production. Only 5.x clients can collect this metric. |
| Avg Message Size | Bytes | Change in the size of messages in the cluster. |
| Quantity Change of Different Types of Messages | Count | Change in the size of messages in the cluster. |
| Production Duration Distribution | Count | Heat map of messages of different consumption duration ranges (available only in the Pro and Platinum editions). |
| Produced Message Size Distribution | Count | Heat map of messages of different sizes (available only in the Pro and Platinum editions). |
Consumption metrics | Consumed Messages | Count/s | Change in the average number of messages consumed per minute in a cluster. |
| Heaped Messages | Count | Change in the number of backlogged messages in a cluster. |
| Consumption Traffic | MBytes/s | Change in the total traffic for consuming messages in the cluster. |
| Consumption Duration | ms | Duration for consumers to process messages (from starting message processing to message processing completed). Only 5.x clients can collect this metric. |
| Ready Messages | Count | Number of messages in the ready status, which indicates the number of messages that can be consumed by consumers on the server. |
| Messages Being Processed | Count | Number of messages in the Inflight status, which indicates the number of messages being consumed on the server for which consumption results have not been returned. |
| Dead Letter Messages Stored per Sec | Count | Number of new messages in the DLQ status per second, which indicates the number of messages that fail to be consumed after the maximum number of retries is reached and are saved to the specified topic. |
| Queuing Time of Ready Messages | ms | Time difference between the ready time of the earliest ready message and the current time, which reflects the timeliness of messages pulled by consumers. |
| Message Consumption Delay | ms | Time difference between the ready time of the earliest unacknowledged message and the current time, which reflects the timeliness of message consumption by consumers. |
| Consumption Duration Distribution | Count | Heat map of duration ranges for consuming different types of messages (available only in the Pro and Platinum editions). |
| Messages in Local Cache Queue | Count | Only PushConsumer client data of 5.x clusters is displayed. SimpleConsumer clients do not have a cache queue. |
| Total Message Size in Local Cache Queue | Bytes | Only data of PushConsumer clients of 5.x clusters is displayed. SimpleConsumer clients do not have a cache queue. |
| Avg Queuing Time of Messages in Local Cache Queue | ms | Only data of PushConsumer clients of 5.x clusters is displayed. SimpleConsumer clients do not have a cache queue. |
Error metrics | Number of Client Errors | Count | Number of errors reported during client requests to the server. |
| Router Not Found | Count | Group/Topic name and format errors during message production. |
| Subscription Not Exist | Count | Group/Topic name and format errors during message consumption. |
| Permission error for sending and receiving messages | Count | Authentication errors reported for message sending/receiving on the data plane. Generally, these errors are reported because the user in the client code does not have production/consumption permissions for the resources. |
Public network metrics | Public Network Inbound Bandwidth | Mbps/s | Change in the public network bandwidth due to client requests to the cluster. |
| Public Network Inbound Traffic | MB | Change in the public network traffic due to client requests to the cluster. |
| Public Network Outbound Bandwidth | Mbps/s | Change in the public network bandwidth due to the cluster outflow traffic. |
| Public Network Outbound Traffic | MB | Change in the public network traffic due to the cluster outflow traffic. |
| Inbound Bandwidth Usage | % | Current inbound bandwidth/Bandwidth upper limit selected during the purchase x 100% |
| Outbound Bandwidth Usage | % | Current outbound bandwidth/Bandwidth upper limit selected during the purchase x 100% |
| Dropped Outbound Bandwidth | Bit/s | A value is generated when the public network bandwidth is limited. If it is greater than 0, adjust the public network bandwidth limit of the cluster. |
| Dropped Inbound Bandwidth | Bit/s | A value is generated when the public network bandwidth is limited. If it is greater than 0, adjust the public network bandwidth limit of the cluster. |
Classification | Metric Name | Unit | Description |
Production metrics | Produced Messages | Count/s | Change in the average number of messages produced per minute in a topic. |
| Production Traffic | MBytes/s | Change in the total traffic for message production in the topic. |
| Producer Count | Count | Number of producer clients in the topic. Only 5.x clients can collect this metric. |
| Production Success Rate | % | Change in the production success rate of messages in the topic. Only 5.x clients can collect this metric. |
| Avg Message Production Duration (Message sending RT) | ms | Duration for a successful call to the message sending API using the SDK, that is, the RT for message production in the topic. Only 5.x clients can collect this metric. |
| Avg Message Size | Bytes | Change in the average size of messages in the topic. |
| RocketmqTopicSendCostTimeOverflow RocketmqTopicSendCostTime500 RocketmqTopicSendCostTime200 RocketmqTopicSendCostTime50 RocketmqTopicSendCostTime20 RocketmqTopicSendCostTime10 RocketmqTopicSendCostTime5 RocketmqTopicSendCostTime1 | Count | Heat map of messages of different consumption duration ranges (available only in the Pro and Platinum editions). |
| RocketmqMessageSizeOverflow RocketmqMessageSize4096k RocketmqMessageSize2048k RocketmqMessageSize1024k RocketmqMessageSize512k RocketmqMessageSize4k RocketmqMessageSize1k | Count | Heat map of messages of different sizes (available only in the Pro and Platinum editions). |
Consumption metrics | Consumed Messages | Count/s | Change in the average number of messages consumed per minute in the topic. |
| Heaped Messages | Count | Change in the number of backlogged messages in the topic. |
| Consumption Traffic | MBytes/s | Change in the total traffic for consuming messages in the topic. |
| Consumer Count | Count | Number of consumer clients that subscribe to the topic. |
| Consumption Duration | ms | Average duration from the start of message processing to processing completion by consumers in the topic. |
| Ready Messages | Count | Number of messages in the ready status in the topic, which indicates the number of messages that can be consumed by consumers on the server. |
| Messages Being Processed | Count | Number of messages in the Inflight status in the topic, which indicates the number of messages being consumed by clients for which consumption results have not been returned. |
| Dead Letter Messages Stored per Sec | Count | Number of new messages in the DLQ status per second in the topic, which indicates the number of messages that fail to be consumed after the maximum number of retries is reached and are saved to the specified topic. |
| Queuing Time of Ready Messages | ms | Time difference between the ready time of the earliest ready message and the current time in a topic, which reflects the timeliness of messages pulled by consumers. |
| Message Consumption Delay | ms | Time difference between the ready time of the earliest unacknowledged message and the current time, which reflects the timeliness of message consumption by consumers. |
| RocketmqTopicProcessTimeOverflow RocketmqTopicProcessTime60000 RocketmqTopicProcessTime10000 RocketmqTopicProcessTime1000 RocketmqTopicProcessTime100 RocketmqTopicProcessTime10 RocketmqTopicProcessTime5 RocketmqTopicProcessTime1 | Count | Heat map of duration ranges for consuming different types of messages (available only in the Pro and Platinum editions). |
| RocketmqTopicConsumerCachedMessages | Count | Only PushConsumer client data of 5.x clusters is displayed. SimpleConsumer clients do not have a cache queue. |
| RocketmqTopicConsumerCachedBytes | Bytes | Only data of PushConsumer clients of 5.x clusters is displayed. SimpleConsumer clients do not have a cache queue. |
| RocketmqTopicAwaitAverageTime | ms | Only data of PushConsumer clients of 5.x clusters is displayed. SimpleConsumer clients do not have a cache queue. |
Billing metrics | Total TPS | Count/s | Maximum number of API calls per minute in the topic (sum of API calls for producing and consuming messages, which is calculated based on billing rules). Traffic throttling is triggered if the number of API calls per minute exceeds the limit. |
| Production TPS | Count/s | Maximum number of API calls per minute for producing messages in the topic (calculated based on billing rules). Traffic throttling is triggered if the number of API calls per minute exceeds the limit. |
| Consumption TPS | Count/s | Maximum number of API calls per minute for consuming messages in the topic (calculated based on billing rules). Traffic throttling is triggered if the number of API calls per minute exceeds the limit. |
| Message Storage Space | GBytes | Space occupied by stored messages in the topic. |
| Throttled Production TPS | Count/s | When the number of API calls exceeds the cluster limit (calculated based on billing rules), the server enables traffic throttling. |
| Throttled Consumption TPS | Count/s | When the number of API calls exceeds the cluster limit (calculated based on billing rules), the server enables traffic throttling. |
Classification | Metric Name | Unit | Description |
Consumption metrics | Consumed Messages | Count/s | Change in the average number of messages consumed per minute in the group. |
| Heaped Messages | Count | Change in the number of backlogged messages in the group. |
| Consumption Traffic | MBytes/s | Change in the total traffic for consuming messages in the group. |
| Consumer Count | Count | Number of consumer clients in the group. |
| Consumption Duration | ms | Average duration for consumers in the group to process messages (from starting message processing to message processing completed). Only 5.x clients can collect this metric. |
| Ready Messages | Count | Number of messages in the ready status among messages consumed by the group, which indicates the number of messages that can be consumed by consumers on the server. |
| Messages Being Processed | Count | Number of messages in the Inflight status among messages consumed by the group, which indicates the number of messages being consumed by clients for which consumption results have not been returned. |
| Dead Letter Messages Stored per Sec | Count | Number of new messages in the DLQ status per second in the group, which indicates the number of messages that fail to be consumed after the maximum number of retries is reached and are saved to the specified topic. |
| Queuing Time of Ready Messages | ms | Time difference between the ready time of the earliest ready message among messages consumed by the group and the current time, which reflects the timeliness of messages pulled by consumers. |
| Message Consumption Delay | ms | Time difference between the ready time of the earliest unacknowledged message among messages consumed by the group and the current time, which reflects the timeliness of messages consumed by consumers. |
| RocketmqGroupProcessTimeOverflow RocketmqGroupProcessTime60000 RocketmqGroupProcessTime10000 RocketmqGroupProcessTime1000 RocketmqGroupProcessTime100 RocketmqGroupProcessTime10 RocketmqGroupProcessTime5 RocketmqGroupProcessTime1 | Count | Heat map of duration ranges for consuming different types of messages (available only in the Pro and Platinum editions). |
| RocketmqGroupConsumerCachedMessages | Count | Number of messages in the local cache queue of the current group or consumer. Only PushConsumer client data of 5.x clusters is displayed, and SimpleConsumer clients do not have a cache queue. |
| RocketmqGroupConsumerCachedBytes | Bytes | Total size of messages in the local cache queue of the current group or consumer. Only PushConsumer client data of 5.x clusters is displayed, and SimpleConsumer clients do not have a cache queue. |
| RocketmqGroupAwaitAverageTime | ms | Average queuing time of messages in the local cache queue of the current group or consumer. Only PushConsumer client data of 5.x clusters is displayed, and SimpleConsumer clients do not have a cache queue. |
| Number of Retry messages generated per second | Count/s | Change in the number of messages that are transferred to the retry queue after they fail to be consumed by a client. |
| Retry message accumulation | Count | Change in the number of backlogged retry messages. |
Billing metrics | Consumption TPS | Count/s | Maximum number of API calls per minute for consuming messages in the current group (calculated based on billing rules). Traffic throttling is triggered if the number of API calls per minute exceeds the limit. |
| Throttled Consumption TPS | Count/s | When the number of API calls exceeds the cluster limit (calculated based on billing rules), the server enables traffic throttling. |
Classification | Metric Name | Unit | Description |
Billing metrics(displayed only for virtual clusters) | Total Cluster TPS | Count/s | Sum of API calls for producing and consuming messages in a cluster (calculated based on billing rules). |
| Production TPS | Count/s | Maximum number of API calls for producing messages per minute in a cluster (calculated based on billing rules). |
| Consumption TPS | Count/s | Maximum number of API calls for consuming messages per minute in a cluster (calculated based on billing rules). |
| Throttled Production TPS | Count/s | When the number of API calls exceeds the cluster limit (calculated based on billing rules), the server enables traffic throttling. |
Production metrics | Produced Messages | Count/s | Change in the average number of messages produced per minute in a cluster. |
| Production Traffic | MBytes/s | Change in the total traffic for producing messages in a cluster. |
Consumption metrics | Consumed Messages | Count/s | Change in the average number of messages consumed per minute in a cluster. |
| Heaped Messages | Count | Change in the number of backlogged messages in a cluster. |
| Consumption Traffic | MBytes/s | Change in the total traffic for consuming messages in the cluster. |
| Heaped Retry Messages | Count | Change in the number of messages that are transferred to the retry queue after they fail to be consumed by a client. |
Public network metrics(displayed only for general/exclusive clusters) | Public Network Inbound Bandwidth | Mbps/s | Change in the public network bandwidth due to client requests to the cluster. |
| Public Network Inbound Traffic | MB/s | Change in the public network traffic due to client requests to the cluster. |
| Public Network Outbound Bandwidth | Mbps/s | Change in the public network bandwidth due to the cluster outflow traffic. |
| Public Network Outbound Traffic | MB/s | Change in the public network traffic due to the cluster outflow traffic. |
| Inbound Bandwidth Usage | % | Current inbound bandwidth/Bandwidth upper limit selected during the purchase x 100% |
| Outbound Bandwidth Usage | % | Current outbound bandwidth/Bandwidth upper limit selected during the purchase x 100% |
| Dropped Outbound Bandwidth | Mbps/s | A value is generated when the public network bandwidth is limited. If it is greater than 0, adjust the public network bandwidth limit of the cluster. |
| Dropped Inbound Bandwidth | Mbps/s | A value is generated when the public network bandwidth is limited. If it is greater than 0, adjust the public network bandwidth limit of the cluster. |
Storage metrics(displayed only for general clusters/exclusive clusters) | Available Disk Space | MBytes | Cluster storage space specified during purchase - Used message storage space. |
| Disk Usage Percentage | % | Used message storage space/Cluster storage space specified during purchase. |
Node metrics (displayed only for exclusive clusters) | Node Business Load | % | It is calculated as follows: Current node TPS/Recommended single-node TPS specification at purchase x 100%. The value may exceed 100% sometimes. When the value exceeds 100%, the business needs to determine whether to scale out nodes based on actual conditions. |
Classification | Metric Name | Unit | Remarks |
Production metrics | Produced Messages | Count/s | Change in the average number of messages produced per minute in a topic. |
| Production Traffic | MBytes/s | Change in the total traffic for message production in the topic. |
Consumption metrics | Consumed Messages | Count/s | Change in the average number of messages consumed per minute in the topic. |
| Heaped Messages | Count | Change in the number of backlogged messages in the topic. |
| Consumption Traffic | MBytes/s | Change in the total traffic for consuming messages in the topic. |
Billing metrics(displayed only for 4.x virtual clusters) | Total Cluster TPS | Count/s | Sum of API calls for producing and consuming messages in a cluster (calculated based on billing rules). |
| Production TPS | Count/s | Maximum number of API calls for producing messages per minute in a topic (calculated based on billing rules). |
| Consumption TPS | Count/s | Maximum number of API calls for consuming messages per minute in a topic (calculated based on billing rules). |
| Throttled TPS | Count/s | When the number of API calls exceeds the cluster limit (calculated based on billing rules), the server enables traffic throttling. |
Classification | Metric Name | Unit | Remarks |
Consumption metrics | Consumed Messages | Count/s | Change in the average number of messages consumed per minute. |
| Heaped Messages | Count | Change in the number of backlogged messages. |
| Consumption Traffic | MBytes/s | Change in the total traffic for consuming messages. |
| Online Consumers | Count | Change in the number of online consumers. |
| Message Consumption Delay | s | Time difference between the ready time of the earliest unacknowledged message and the current time, which reflects the timeliness of message consumption by consumers. |
| Dead Letter Messages Stored per Sec | Count/s | Number of new messages in the DLQ status per second in the group, indicating the number of messages that fail to be consumed after the maximum number of retries is reached and are saved to the specified topic. |
| Heaped Retry Messages | Count | Change in the number of messages that are transferred to the retry queue after they fail to be consumed by a client. |
Overview of Parameters in Each Dimension
Parameter Name | Dimension Name | Dimension Explanation | Dimension Explanation |
Instances.N.Dimensions.0.Name | tenant | Dimension name of the cluster ID. | Enter a dimension name of the string type: tenant. |
Instances.N.Dimensions.0.Value | tenant | Specific cluster ID. | Enter a specific cluster ID, for example, rmq-xxxxxxxxxx. |
Instances.N.Dimensions.1.Name | topic | Topic dimension name. | Enter a dimension name of the string type: topic. |
Instances.N.Dimensions.1.Value | topic | Specific topic name. | Enter a specific topic name, for example, testTopic. |
Instances.N.Dimensions.2.Name | group | Consumer group dimension name. | Enter a dimension name of the string type: group. |
Instances.N.Dimensions.2.Value | group | Specific consumer group name. | Enter a specific consumer group name, for example, default. |
Instances.N.Dimensions.3.Name | client_id | Client dimension name. | Enter the dimension name of the string type: client_id. |
Instances.N.Dimensions.3.Value | client_id | Specific client ID. | Enter a specific client ID, for example, default. It can be obtained on the Consumer List page under Cluster Management in the TDMQ for RocketMQ console. |
Parameter Name | Dimension Name | Dimension Explanation | Dimension Explanation |
Instances.N.Dimensions.1.Name | tenant | Dimension name of the cluster ID. | Enter a dimension name of the string type: tenant. |
Instances.N.Dimensions.1.Value | tenant | Specific cluster ID. | Enter a specific cluster ID, for example, rocketmq-xxxxxxxxxx. |
Instances.N.Dimensions.2.Name | namespace | Namespace dimension name. | Enter a dimension name of the string type: namespace. |
Instances.N.Dimensions.2.Value | namespace | Specific namespace name. | Enter a specific namespace name, for example, default. |
Instances.N.Dimensions.3.Name | topic | Topic dimension name. | Enter a dimension name of the string type: topic. |
Instances.N.Dimensions.3.Value | topic | Specific topic name. | Enter a specific topic name, for example, testTopic. |
Instances.N.Dimensions.4.Name | group | Consumer group dimension name. | Enter a dimension name of the string type: group. |
Instances.N.Dimensions.4.Value | group | Specific consumer group name. | Enter a specific consumer group name, for example, default. |
Input Parameter Description
Topic metrics are used as examples.
The input parameter values for querying message queue monitoring data are as follows:
&Namespace = QCE/ROCKETMQ
&Instances.N.Dimensions.0.Name = tenant
&Instances.N.Dimensions.0.Value = Specific cluster ID
&Instances.N.Dimensions.1.Name = topic
&Instances.N.Dimensions.1.Value = Specific topic name
&Instances.N.Dimensions.2.Name = group
&Instances.N.Dimensions.2.Value = Specific consumer group name
&Instances.N.Dimensions.3.Name = client_id
&Instances.N.Dimensions.3.Value = Specific client ID
Topic metrics are used as examples.
The input parameter values for querying message queue monitoring data are as follows:
&Namespace = QCE/ROCKETMQ
&Instances.N.Dimensions.0.Name = tenant
&Instances.N.Dimensions.0.Value = Specific cluster ID
&Instances.N.Dimensions.1.Name = namespace
&Instances.N.Dimensions.1.Value = Specific namespace
&Instances.N.Dimensions.2.Name = topic
&Instances.N.Dimensions.2.Value = Specific topic name
&Instances.N.Dimensions.3.Name = group
&Instances.N.Dimensions.3.Value = Specific consumer group name
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback