The content of this page has been automatically translated by AI. If you encounter any problems while reading, you can view the corresponding content in Chinese.
Help & Documentation>TDMQ for RabbitMQ

Message Query

Last updated: 2024-08-02 15:42:06

Operation scenarios

If there are issues like abnormal message delivery or missing messages, you can use the message query feature in the TDMQ RabbitMQ console for timely analysis and problem localization.
This article guides you in querying messages through the TDMQ RabbitMQ console.

Prerequisites

The Vhost that requires message queries has the Trace Plugin enabled.


Use Limits

Overview of the message query implementation principle: After enabling the Trace Plugin for the VHost, the service component will consume the corresponding RabbitMQ cluster's trajectory messages. Through a series of processes, it can realize the console’s message tracking feature.
Based on this principle, message tracking relies on service components consuming trajectory messages. Since the service component is a fundamental public service, it cannot ensure the timely consumption of high-volume RabbitMQ cluster trajectory messages. If trajectory messages accumulate, it can cause high cluster memory load and affect the stability of the RabbitMQ cluster.
Therefore, it is not recommended to enable the Trace Plugin in production environments, especially in scenarios where the entire cluster (including all VHosts) has a TPS exceeding 10000. The Trace Plugin is recommended for low traffic validation/troubleshooting scenarios.

Operation step

1. Log in to RabbitMQ Console.
2. Select Message Query from the left sidebar, choose the region and time range for the query.
3. Select the cluster, Vhost, and Queue you need to query. You can also fill in the Routing Key, users, message headers, and body to further narrow the search.
4. Click Inquiry, and the results will be displayed in the list below.

Note:
To ensure cluster stability, the console limits the number and dimensions of message queries. Users can query messages in specific queues, with a maximum return of 10000 results, filtered by the queue and optionally the Routing Key. Users can also add filters for users, headers, and body for further inquiry, but queries will be conducted within the previously mentioned maximum of 10000 results. Therefore, it is recommended to use the message query feature in low-traffic validation/troubleshooting scenarios.
5. Find the message for which you want to view details, and click View Message Details in the operations column to see detailed information and content (message body).