View Client Details
Last updated:2026-01-30 14:55:29
This article introduces how to view client information on the MQTT console, including basic info, connection information, and subscription relationships, helping you to monitor client status in real-time and promptly address related issues.
View Client Details
Viewing client info has two operation entries:
Entry I:
1. Log in to the MQTT console.
2. Click Resource > Cluster in the left sidebar. After selecting a region, click the "ID" of the target cluster to enter the cluster basic information page.
3. Select Client in the left tab bar to view the client list.
Note:
The Client Management page allows you to search based on the entered Client ID and supports fuzzy search.
When no input is provided, a maximum of 1024 sessions are randomly displayed.
Entry II:
1. Log in to the MQTT console.
2. Click Resource > Client in the left sidebar, select the region and cluster, and then view the client list.
View Client Info: Click the client ID or click Details in the Operation column of the target client to further view client-related information.
Client Details Description
Basic Information
Show basic client info, including the client ID, address, connection status, createTime, and MQTT Protocol Version.
Parameter | Description |
Client ID | The client's unique identity identifier, usually starting with paho or hive. |
Client Host | The source address of the network where the client and server establish a connection, including the IP address and port number. |
Connection Status | The client's online status. When online, you can disconnect manually in the client list operation bar. After disconnection, it is unable to consume messages. |
Creation Time | The time when the client was created. |
MQTT Protocol Version | TDMQ for MQTT is fully compatible with the standard MQTT 3.1, MQTT 3.1.1, and MQTT 5.0 protocols. For protocol compatibility details, refer to MQTT Protocol Compatibility Notes. |
Spread attribute (Optional) | Optional configuration. After configuring the spread attribute for a designated client through the API, the spread attribute will subsequently follow message passing and convert into the User Property of messages sent by the client. Customers can leverage this feature, combined with specific business scenarios, to add business context information to messages. When connecting to the MQTT trigger function, the function can also be triggered based on designated filtered spread attributes. |
Session Ddetails
The Session detail block shows the memory state of the current Session connection. This information is not persistent. When the network connection disconnects and reconnects, the data will be cleared and counted again.
Parameter | Description |
Clean Session(MQTT V3.1.1) Clean Start(MQTT V5.0) | Used to determine how the client and server handle previous sessions. true(1): When users wish to establish a temporary, stateless session, the server will drop the saved session status (including unconfirmed QoS 1/2 messages, subscription information, etc.) for the client ID upon disconnection. Suitable for temporary data collection clients, devices not requiring historical status, or when users wish to restart from a cleared state. false(0): The client wishes to establish a persistent, stateful session. After disconnection, the server will retain the client's subscription information and unconfirmed QoS 1/2 messages so that the client can restore them upon reconnection. Suitable for clients requiring reliable receipt of all messages, where even messages missed during disconnection should be re-delivered after reconnection. |
Connection time | The client with the current connection status "online" shows this info. It records the timestamp of the current session's successful establishment, which is the last time a CONNECT message was received and a CONNACK reply was successful, referring to the start time of this connection. |
Last Connection Time | The client with the current connection status "not connected" shows this info. It records the timestamp of the last successful session establishment. |
Session Creation Time | Record the initial creation timestamp of the session. When Clean Session = False, the creation time of the first connection session. Even if the client disconnects and reconnects, as long as the session is not expired, this creation time remains unchanged. When Clean Session = True, every time a connection is established, a temporary new session is created. The "creation time" of this session is exactly the connection time, and the session is terminated after disconnection. |
Last Disconnection Time | Record the timestamp of the last normal or disconnected due to an exception session, combined with "connection time" can calculate the device's online rate and offline duration. |
Keep Alive | The heartbeat interval declared by the client in the CONNECT message. The client guarantees to the server that the interval between any two consecutive messages will not exceed Keep Alive * 1.5. The server uses this to judge client liveness. If no message is received for Keep Alive * 1.5, the server will consider the client offline and disconnect. |
Received Data Volume | In the current connection, the total number of network bytes received by the server from the client, including all types of MQTT messages (such as CONNECT, PUBLISH, SUBSCRIBE, PINGREQ) and the underlying protocol header overhead. It measures inbound traffic. |
Received Packets | In the current connection, the number of MQTT packets received by the server from the client. CONNECT: Connection request count. DISCONNECT: Disconnect request count. PUBLISH: Received message count. PUBACK: Publish acknowledgment (QoS 1). Client acknowledgment for QoS 1 messages forwarded by the server. PUBREC: Publish received (QoS 2 step one). Client acknowledgment for QoS 2 messages forwarded by the server for the first time. PUBREL: Publish release (QoS 2 step two). The client responds to the server's PUBREC, indicating it is ready to complete message transmission. PUBCOMP: Publish complete (QoS 2 step three). The client's final acknowledgment of the server's PUBREL message. PINGREQ: Heartbeat request count. SUBSCRIBE/UNSUBSCRIBE: Subscribe/Unsubscribe request count. |
Sent Data Volume | In the current connection, the total number of network bytes sent by the server to the client, including all downstream messages (such as CONNACK, PUBLISH, PINGRESP) and the underlying protocol overhead. It measures outbound traffic. |
Sent Packets | In the current connection, the number of MQTT packets sent by the server to the client. CONNACK: Connection confirmation count. PUBLISH: Forwarded message count. PUBACK: Publish confirmation count. PUBREC: Publish received (QoS 2 step one). Server acknowledgment for QoS 2 messages published by the client for the first time. PUBREL: Publish release (QoS 2 step two). The server as sender sends this message upon receiving the client's PUBREC to request final confirmation. PUBCOMP: Publish complete (QoS 2 step three). The server as recipient sends final acknowledgment for the client's PUBREL message, completing the entire QoS 2 message flow. SUBACK/UNSUBACK: Subscription confirmation/cancellation count. The server's response to the client's SUBSCRIBE message, which includes the granted QoS level for each subscription. PINGRESP: Heartbeat request response count. DISCONNECT: Disconnect. |
Subscription
The client subscription relationship refers to the association set between a specific client and ALL its subscribed Topic filters. For details, see Subscribe to Messages Using the Client.
Parameter | Description |
Topic FIlter | Client subscribed Topic Filter. |
QoS | The QoS level specified by the client when subscribing to a certain topic. |
Unacknowledged Messages | Number of messages sent to the client but not fully acknowledged (ACK), mainly for QoS 1 and QoS 2 messages. QoS 1: The broker has sent PUBLISH but not received PUBACK from the client. QoS 2: The broker has sent PUBLISH but not completed the full process of PUBREC > PUBREL > PUBCOMP. For QoS 0 messages, there is no acknowledgement mechanism, so the "unconfirmed" status does not exist. |
Accumulated Messages | Total number of messages temporarily stored on the server waiting to be sent to the client. |
SUBSCRIBE Properties | Show User Property in SUBSCRIBE Properties for different Topic Filter subscriptions, making it easy for O&M personnel to trace the subscription source and quickly locate anomalous subscription behavior. |
Client Certificate
A client certificate is a digital certificate issued by a CA certificate to a client device. When establishing a connection with the server, the server performs security verification on the client's identity based on the client certificate. After successful verification, both parties can achieve secure communication using the built-in encryption key in the certificate. If verification fails, the server will reject the client's connection request.
After a client certificate is registered, you can manage registered client certificates on this page at any time, such as viewing the status of registered certificates, filtering invalid or expiring (expiring within 30 days) client certificates, and viewing client details. For client registration methods, see Step 4: Configuring Client Certificates.
Client Events
Client events refer to a series of status changes and interaction notifications triggered by clients during MQTT protocol communication. Tracking system events helps users troubleshoot and locate issues promptly, ensuring system stability. This page supports the display and query of certificate events and various client behavior events (such as online/offline status and connections) within a specified time range. For details, see Query Client Events.
Client Message Trace
Supports querying details of a specific client message, such as message ID, request time, and QoS. If the target trajectory is not found, you can narrow the search range through precise time and message ID filtering. The message ID can be obtained on the Message Query Page.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback