leizhiyuan opened a new issue, #1639:
URL: https://github.com/apache/rocketmq-dashboard/issues/1639

   ## Motivation
   
   The Tencent Cloud provider (`provider/tencent`, Trocket v20230308 OpenAPI) 
gained Topic
   management (#1535) and consumer group management (#1590), but message query 
operations on
   `TencentInstanceProvider` (`queryMessages` / `getMessageTrace`) still threw
   `UnsupportedOperationException`. Users cannot search messages or inspect 
their trace on a Tencent
   Cloud RocketMQ 5.x instance from the Message page.
   
   ## What this adds
   
   Implements the instance-scoped message surface for the Tencent provider by 
mapping to the Trocket
   OpenAPI:
   
   - **Query messages by message ID** - `DescribeMessage` returns the full 
detail (body, properties,
     producer, store time), with `TAGS` / `KEYS` surfaced from `Properties` 
onto the record's
     `tag` / `key`.
   - **Query message list by topic / time / key / tag** - `DescribeMessageList` 
(async task-based:
     first call passes an empty `TaskRequestId`, response carries the task id 
for paging). Maps
     `MessageItem` -> `MessageRecordVO` with `ProduceTime` parsed into 
`storeTime`.
   - **Message trace** - `DescribeMessageTrace` parses the per-stage JSON 
payload (`produce` /
     `persist` / `consume`) into `TraceNodeVO` nodes and `ConsumerStatusVO` 
entries (consumer group,
     delivery status, retry count). The topic is passed through the trace call 
chain because the
     API requires a non-empty `Topic`.
   
   ## Time parsing
   
   Tencent returns `ProduceTime` in several shapes (`yyyy-MM-dd HH:mm:ss`, 
`.SSS`, `,SSS`). The parser
   accepts the common formats and falls back to epoch-millis when the value is 
already numeric.
   
   ## Scope
   
   Scoped to the `rocketmq-studio` branch where the Tencent provider lives. 
Only message query and
   trace; dead-letter (DLQ) operations for Tencent remain unsupported.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to