Aias00 opened a new issue, #4143: URL: https://github.com/apache/rocketmq-dashboard/issues/4143
## Problem The Studio message REST API and `MessageService` support an optional custom trace topic when looking up a message trace, and the Message Explorer UI can persist and use that value. The AI/MCP tool `rmq.message.trace` exposes only `cluster`, `msgId`, and `topic`, so AI and CLI callers are forced to use the default trace topic even when a deployment stores traces elsewhere. ## Expected behavior - Add an optional `traceTopic` string to the `rmq.message.trace` input schema. - Forward the value through `MessageTraceToolHandler` to the existing four-argument `MessageService.getMessageTrace` method. - Keep `cluster` and `msgId` as the only required fields. - Preserve the current output schema and risk/permission classification. - A missing or blank `traceTopic` keeps the existing default/provider behavior through `MessageService`. ## Acceptance criteria - The canonical tool catalog advertises optional `traceTopic`. - Handler coverage proves a supplied custom topic reaches `MessageService`. - Existing message trace projection behavior remains unchanged. - No new endpoint or provider-specific behavior is introduced. ## Scope This issue only covers message-id trace lookup. Trace lookup by business key remains separate work. -- 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]
