RockteMQ-AI commented on issue #1540: URL: https://github.com/apache/rocketmq-dashboard/issues/1540#issuecomment-5248529699
**Issue Evaluation** Category: `bug` | Status: **Confirmed** Verified against `upstream/rocketmq-studio` branch. `ClusterController.listClusters()` accepts an optional `instanceId` parameter and the backend `ClusterService` supports both `listClusters()` (global) and `listClusters(instanceId)` (scoped). However, the Broker Cluster diagnostics page in the frontend calls `listClusters()` without passing an `instanceId` and provides no instance selector. In a multi-instance Studio deployment, this always reads the default/global cluster discovery path rather than the operator-selected instance. **Root Cause:** Frontend does not load Apache instances or pass `instanceId` to `listClusters()`. **Impact:** Multi-instance deployments see incorrect or merged diagnostics. **Severity:** Medium — incorrect diagnostics in multi-instance setups. An automated fix proposal will 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]
