Aias00 opened a new issue, #982: URL: https://github.com/apache/rocketmq-dashboard/issues/982
## Problem\nRuntime views do not consistently use the selected cluster.\n\n- Client connections accept , but the provider uses the singleton and only writes the requested ID back into the response.\n- DLQ UI exposes an instance selector but neither list nor resend requests carry that context.\n- Message query and trace APIs have no cluster/instance parameter.\n\nThis can display or mutate the default NameServer cluster while the UI identifies another cluster.\n\n## Expected\nAll runtime operations resolve an AdminClient by the selected cluster/instance and preserve that context through the API, audit record, and UI.\n\n## Acceptance criteria\n- Client, DLQ, message query, and trace contracts include the required cluster context.\n- The backend obtains the matching AdminClient instead of the singleton default client.\n- DLQ instance selection reloads data and resend preserves the selected scope.\n- Tests prove that the selected cluster is used rather than merely echoed. -- 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]
