Aias00 opened a new issue, #1176: URL: https://github.com/apache/rocketmq-dashboard/issues/1176
## Problem `GET /api/dashboard` has no instance context and `RocketMQDashboardProvider` always uses the process-wide `DefaultMQAdminExt`. In a multi-instance Studio deployment, the home dashboard can therefore show the configured default NameServer instead of the instance selected by the user. The provider also reports every discovered cluster as `V5_PROXY_CLUSTER`, even for NameServer-based instances. ## Proposed fix - accept an optional `instanceId` on the dashboard API and client call; - when supplied, resolve a short-lived admin client through `RuntimeAdminClientResolver`; - retain the existing default-admin path when `instanceId` is omitted; - derive the overview cluster type from the selected instance rather than hard-coding a Proxy type; - add controller/provider and frontend API coverage. ## Scope Track 1 / ARCH-01: multi-instance runtime routing and architecture-aware dashboard rendering. -- 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]
