Viewing Monitoring Data
Last updated:2025-07-23 11:11:46
Scenarios
TDMQ RocketMQ supports monitoring resources created under your account, including clusters, topics, and groups. Based on these monitoring metrics, you can analyze cluster usage, promptly deal with possible risks, and ensure stable system operation.
This document describes how to view monitoring metrics in the TDMQ RocketMQ Console and the descriptions of monitoring metrics.
Monitoring Metrics
The monitoring metrics supported by TDMQ RocketMQ are as follows:
Category | Metric | Unit | Remarks | Supported Dimension |
Billing metrics | Total TPS | Count/s | Total number of API calls for producing and consuming messages (calculated according to the billing rules). | Cluster, Topic |
| Production TPS | Count/s | Cluster, Topic | |
| Consumption TPS | Count/s | Cluster, Topic | |
| Message storage space | GBytes | - | Cluster, Topic |
| elastic TPS | Count/s | Only the Pro Edition and Platinum Version are supported. | Cluster |
| Rate limited production TPS | Count/s | - | Cluster, Topic |
| Rate limited consumption TPS | Count/s | - | Cluster, Topic, Group |
Production metrics | Number of produced messages | Count/s | - | Cluster, Topic |
| Amount of produced traffic | MBytes/s | - | Cluster, Topic |
| Number of Producers | Count | Only online producer clients are counted. | Cluster, Topic |
| production success rate | % | - | Cluster, Topic |
| Average duration of message production (sending RT) | ms | The time taken for a successful SDK call to the message sending API, i.e., the RT of message production, can only be collected by 5.x clients. | Cluster, Topic |
| Average message size | Bytes | - | Cluster, Topic |
| Message Type Quantity Change | Count | - | Cluster |
| Production Time Distribution | - | Heat distribution of different message time ranges (Pro Edition and Platinum Version only). | Cluster, Topic |
| Production message size distribution | - | Heat distribution of different message sizes (Pro Edition and Platinum Version only). | Cluster, Topic |
Consumption metrics | Number of consumed messages | Count/s | - | Cluster, Topic, Group |
| Number of heaped messages | Count | - | Cluster, Topic, Group, Topic & Group |
| Consumption traffic | MBytes/s | - | Cluster, Topic, Group |
| Number of Consumers | Count | - | Topic,Group |
| Consumption time | ms | The time taken from when the consumer starts processing messages to when processing is completed. Only 5.x clients can collect this metric. | Cluster, Topic, Group, Topic & Group, consumer client |
| Number of ready messages | Count | The message count with status is Ready means the number of messages that can be consumed by the consumer on the server. | Cluster, Topic, Group, Topic & Group |
| Number of messages in process | Count | The message count with status is Inflight indicates the number of messages being consumed on the server but not returned with a consumption result. | Cluster, Topic, Group, Topic & Group |
| Number of heaped retry messages | Count | Number of heaped retry messages in the queue that were not consumed successfully. | Group,Topic&Group |
| Number of dead letter messages saved per second | Count | Number of messages with new status DLQ per second means messages that failed consumption after reaching the maximum number of retries, but were saved to the specified Topic. | Cluster, Topic, Group, Topic & Group |
| Queuing time of ready messages | ms | The time difference between the readiness time of the earliest ready message and the current moment reflects the timeliness of the consumer pulling messages. | Cluster, Topic, Group, Topic & Group |
| Consumption processing lag time | ms | The time difference between the readiness time of the earliest message with no response returned and the current moment reflects the timeliness of the consumer completing message consumption. | Cluster, Topic, Group, Topic & Group |
| Number of retry messages | Count | Change in number of messages transferred to retry queue after failing client consumption. | Group |
| Duration distribution | - | Heat distribution of different message consumption time ranges (Pro Edition and Platinum Version only). | Cluster, Topic, Group, Topic & Group, consumer client |
| Number of messages in the local cache queue | Count | Only show data of PushConsumer client version 5.x. SimpleConsumer client has no cache queue. | Cluster, Topic, Group, Topic & Group |
| Total size of messages in the local cache queue | Bytes | Only display data of PushConsumer client version 5.x. SimpleConsumer client has no cache queue. | Cluster, Topic, Group, Topic & Group |
| Average queuing time in local cache queue | ms | Only display data of PushConsumer client version 5.x. SimpleConsumer client has no cache queue. | Cluster, Topic, Group, Topic & Group |
Error-related metrics | Number of common client errors | Count | Number of errors in client requests to the server during the process. | Cluster |
| Number of Router Not Found errors | Count | Typically, the Group/Topic name or format is incorrect when producing messages. | Cluster |
| Subscription Not Exist | Count | Typically, the Group/Topic name or format is incorrect when consuming messages. | Cluster |
| Message sending and receiving permission error count | Count | Data plane message sending and receiving authentication error, usually because the user in the client-side code has no production/consumption permission for the resource. | Cluster |
public network metrics | Public network outbound/inbound traffic | MB/s | - | Cluster |
| Public network outbound/inbound bandwidth | Mbps/s | - | Cluster |
| Public network outbound/inbound bandwidth utilization | % | - | Cluster |
| Public network dropped outbound/inbound bandwidth | Mbps/s | - | Cluster |
Category | Metric | Unit | Remarks | Supported Dimension |
Billing metrics (displayed only for virtual clusters) | Total TPS | Count/s | Total number of API calls for producing and consuming messages (calculated according to the billing rules). | Cluster, Topic |
| Production TPS | Count/s | Total number of API calls for producing messages (calculated according to the billing rules). | Cluster, Topic |
| Consumption TPS | Count/s | Total number of API calls for consuming messages (calculated according to the billing rules). | Cluster, Topic |
| Rate limited production TPS | Count/s | When the API call count exceeds cluster restrictions (converted according to billing rule), the server will enable traffic throttling. | Cluster, Topic |
Production metrics | Number of produced messages | Count/s | Average change in the number of messages produced per minute. | Cluster, Topic |
| Amount of produced traffic | MBytes/s | Total traffic variation in message production. | Cluster, Topic |
Consumption metrics | Number of consumed messages | Count/s | Average change in the number of consumed messages per minute. | Cluster, Topic, Group |
| Number of heaped messages | Count | Change in the number of heaped messages. | Cluster, Topic, Group |
| Consumption traffic | MBytes/s | Total traffic change in message consumption. | Cluster, Topic, Group |
| Number of online consumers | Count | - | Topic,Group |
| Number of heaped retry messages | Count | Change in number of messages transferred to retry queue after failing client consumption. | Cluster, Group |
| Consumption processing lag time | s | The time difference between the readiness time of the earliest message with no response returned and the current moment reflects the timeliness of the consumer completing message consumption. | Topic,Group |
| Number of dead letter messages saved per second | Count/s | - | Group,Group& Topic |
| Dead-letter message TPS | Count/s | - | Topic,Group |
public network metrics | Public network outbound/inbound traffic | MB/s | Change in public network traffic due to client requests to the cluster. | Cluster |
| Public network outbound/inbound bandwidth | Mbps/s | Change in public network bandwidth due to client requests to the cluster. | Cluster |
| Public network outbound/inbound bandwidth utilization | % | Current bandwidth / Bandwidth limit selected during purchase * 100%. | Cluster |
| Public network dropped outbound/inbound bandwidth | Mbps/s | Value generated when public network bandwidth is limited. If it is above 0, adjust the public network bandwidth limit of the large cluster. | Cluster |
storage-related metrics (displayed only for generic clusters/dedicated clusters) | Available disk space | MBytes | The designated cluster storage space at the time of purchase - used message storage space. | Cluster |
| Disk usage percentage | % | Used message storage space / designated cluster storage space at the time of purchase. | Cluster |
Viewing Monitoring Data
1. Log in to the RocketMQ console.
2. Click Monitoring Dashboard in the left sidebar, select region and the cluster to view.
3. On the monitoring page, select the tab of the resource you want to view, set the time range, and view corresponding monitoring data.
Icon | Description |
 | Click to adjust the chart time granularity, supporting 1-minute and 5-minute intervals. |
 | Click to refresh and obtain the latest monitoring data. You can set the time interval to automatically refresh the monitoring data at 30 s, 1 min and 5 min. |
On the cluster monitoring page, you can choose multiple topics in the cluster and view metrics comparison, as shown below.
Likewise, you can compare relevant metrics of multiple groups in a certain Topic's subscription relationship. You can also compare relevant metrics of multiple topics in a certain Group's subscription relationship.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback