Aias00 opened a new issue, #1069: URL: https://github.com/apache/rocketmq-dashboard/issues/1069
## Problem Message ID, key, and time-range queries are part of the #982 runtime data surface. They must use the endpoint of the selected Studio instance instead of process-wide RocketMQ configuration. ## Proposed change - Reuse `RuntimeAdminClientResolver` from #1058. - Require and propagate `instanceId` through message query API, service, provider, and page layers. - Route message-ID, key, and time-range queries to the selected instance endpoint. - Add focused backend and frontend regression coverage. ## Dependency Depends on #1058. Implementation starts after #1058 merges into `rocketmq-studio`, so this can remain an independent PR. ## Scope Part of #982. Message trace is explicitly excluded and tracked separately. -- 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]
