RockteMQ-AI commented on issue #1484: URL: https://github.com/apache/rocketmq-dashboard/issues/1484#issuecomment-5242161771
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** The Cluster page (`frontend-new/src/pages/Cluster/cluster.jsx`) loads instances from `remoteApi.queryClusterList()` and defaults to the first cluster/broker without reading any instance context from the URL. The Dashboard page has no mechanism to pass the selected instance to the Cluster page during navigation — there is no URL parameter (e.g., `?instance=xxx`) or shared state preserved across the route transition. **Impact:** Users viewing metrics for a specific instance on the Dashboard may inadvertently operate on a different broker when navigating to Cluster Health, because the Cluster page always defaults to the first available instance. **Severity:** Medium — no data loss, but incorrect operational context can lead to confusion during troubleshooting. **Suggested Fix:** 1. Dashboard navigation to `/cluster` should append the selected instance as a query parameter (e.g., `/cluster?instance=<name>`). 2. Cluster page should read this parameter via `useSearchParams` and pre-select the matching instance if available. 3. Fall back to the current first-instance behavior when the parameter is missing or invalid. 4. Add route-level regression tests as mentioned in the scope. An automated fix proposal can be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by RockteMQ-AI* -- 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]
