Tencent Cloud

Recent Pages

Message Query

Last updated: 2024-06-26 15:56:25

Overview
If there are abnormal or missing messages, you can use the message query feature in the TDMQ for RabbitMQ console to analyze and locate the problem promptly.
This document describes how to query messages in the TDMQ for RabbitMQ console.
Prerequisites
You have toggled on Trace Plugin for the vhost where you want to query messages.
﻿
Use Limits
Overview of the implementation principle of message query: After the Trace Plugin of the VHost is enabled, the service component will consume the trace messages of the corresponding RabbitMQ cluster. Through a series of processing, it can achieve the feature of querying message traces on the console.
Based on the principles mentioned, message trace relies on service components consuming trace messages. Since service components are underlying public services, they cannot guarantee that trace messages from high-traffic RabbitMQ clusters can be consumed in a timely manner; heap of trace messages can cause issues such as high memory load within the cluster, affecting the stability of the RabbitMQ cluster.
Therefore, it is not recommended to enable the Trace Plugin in production environments, especially in overall clusters (including all VHosts), where the scenario involves sending  TPS over 10,000 . The Trace Plugin is advised to be used in small-traffic verification/troubleshooting scenarios.
Directions
1. Log in to the RabbitMQ console.
2. On the left sidebar, click Message Query and select the region and time range for the query.
3. Select the cluster, vhost, and queue to be queried. You can enter the routing key, user, message headers, and message body to narrow down the query.
4. Click Query, and all results will be displayed in the list below.
﻿
Note：
To ensure the stability of the cluster, the console restricts the quantity and dimensions of message queries. Users can query messages under specific queues, with up to 10,000 results returned. These results are based on filtering by queue and Routing Key (adding a Routing Key filter is optional). Users can also add filters for user, headers, and body to further refine their search, but the query will be conducted within the aforesaid limit of up to 10,000 messages. Therefore, it is recommended to use the message query feature in small-traffic verification/troubleshooting scenarios.
5. Click View Message Details in the Operation column of the target message to view its details and content (message body).
﻿