tencent cloud

Viewing Producer Connections of a Topic
Last updated:2026-01-23 17:34:03
Viewing Producer Connections of a Topic
Last updated: 2026-01-23 17:34:03
In a production environment, the connection status between the producer and the broker directly affects the stability and performance of message sending. Monitoring the connection relationship (such as the client IP address, version, and message sending time) can help rapidly identify network exceptions or resource bottlenecks, ensuring efficient and reliable message delivery.

Constraints and Limitations

For 4.x virtual clusters, you cannot view the producer information.

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 Topic tab, click the target topic name, and select the Producer Management tab to view relevant information about the producers under the topic.
Parameter Name
Description
Producer ID
Unique identifier of a producer instance. Typically, it is automatically generated by the client upon startup and is used to distinguish different connections on the broker side.
Producer Address
IP address and port of the server where the producer client resides, which are key information for identifying the source server of the producer.
Last Sending Time
Timestamp when the producer sends the last message to the topic, which reflects the activity level of the producer. A significant gap between this timestamp and the current time indicates that the producer may become inactive.
Client Type
Indicates whether a producer is of the Producer or Reply Producer type.
Client Language
Programming language used for producer-side development, such as Java, Go, C++, and Python.
Client Version
Version number of the TDMQ for RocketMQ client used by the producer. It is used to determine whether the client is outdated or to confirm whether the issue is specific to a particular version when bugs occur.
Note:
Avoid using client versions with known risks. For details, see Client Risk Descriptions and Update Guide.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback