tencent cloud

TDMQ for RocketMQ

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Introduction and Selection of the TDMQ Product Series
What Is TDMQ for RocketMQ
Strengths
Scenarios
Product Series
Comparison with Open-Source RocketMQ
High Availability
Quotas and Limits
Supported Regions
Basic Concepts
Billing
Billing Overview
Pricing
Billing Examples
Pay-as-you-go Switch to Monthly Subscription (5.x)
Renewal
Viewing Consumption Details
Refund
Overdue Payments
Getting Started
Getting Started Guide
Preparations
Step 1: Creating TDMQ for RocketMQ Resources
Step 2: Using the SDK to Send and Receive Messages (Recommended)
Step 2: Running the TDMQ for RocketMQ Client (Optional)
Step 3: Querying Messages
Step 4: Deleting Resources
User Guide
Usage Process Guide
Configuring Account Permissions
Creating the Cluster
Configuring the Namespace
Configuring the Topic
Configuring the Group
Connecting to the Cluster
Managing Messages
Managing the Cluster
Viewing Monitoring Data and Configuring Alarms
Cross-Cluster Message Replication
Use Cases
Naming Conventions for Common Concepts of TDMQ for RocketMQ
RocketMQ Client Use Cases
RocketMQ Performance Load Testing and Capacity Assessment
Access over HTTP
Client Risk Descriptions and Update Guide
Migration Guide for TencentCloud API Operations Related to RocketMQ 4.x Cluster Roles
Migration Guide
Disruptive Migration
Seamless Migration
Developer Guide
Message Types
Message Filtering
Message Retries
POP Consumption Mode (5.x)
Clustering Consumption and Broadcasting Consumption
Subscription Relationship Consistency
Traffic Throttling
​​API Reference(5.x)
History
API Category
Making API Requests
Topic APIs
Consumer Group APIs
Message APIs
Role Authentication APIs
Hitless Migration APIs
Cloud Migration APIs
Cluster APIs
Data Types
Error Codes
​​API Reference(4.x)
SDK Reference
SDK Overview
5.x SDK
4.x SDK
Security and Compliance
Permission Management
CloudAudit
Deletion Protection
FAQs
4.x Instance FAQs
Agreements
TDMQ for RocketMQ Service Level Agreement
Contact Us

Viewing Producer Connections of a Topic

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 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.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan