pilichoumao opened a new issue, #6410: URL: https://github.com/apache/rocketmq-dashboard/issues/6410
### Describe the bug On `rocketmq-studio` at 779b8c0e7aed2396d3cc72743dcd544ea48e9ae6, Clients can query all physical clusters in the selected registered NameServer. `RocketMQClientProvider` preserves each row's `clusterName` and includes the physical cluster in producer/consumer identities. The frontend diagnostic resource key, duplicate identity and client-ID grouping omit it. For two independent clusters with the same Producer group (for example `DefaultProducer`), the diagnostics therefore combine the resources and warn about mixed versions across clusters. Identical client IDs on different clusters can raise ID collision or duplicate-record warnings. Address concentration and diagnostic distinct counts also need to retain the scope of the observed rows rather than pool independent inventories. ### Reproduction and expected behavior Three tests against the actual diagnostic utility fail on the baseline: two scoped resources become one; same ID across clusters raises a collision; same ID/address across clusters raises a duplicate. Same-cluster mixed-version and duplicate controls pass. Source inspection confirms that ALL passes no `clusterId` filter and the provider returns scoped rows. This evidence uses provider-shaped fixtures, not a live Broker topology. Partition diagnostic resources and identities by physical cluster, preserve same-cluster diagnoses, and identify the cluster on resource/issue rows. Keep raw inventory and backend/API behavior unchanged. ### Related work #6203 addresses TCP source ports within a cluster, not physical cluster scope. #6321 addresses the separate page overview's connection-row counting. #4617 previously identified per-connection issue attribution to resource summaries; scoped issue/resource identities must agree while keeping readable display names. Existing JSON tuple identity encoding (#6303) must be retained rather than replaced with delimiter concatenation. -- 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]
