Aias00 opened a new issue, #1947: URL: https://github.com/apache/rocketmq-dashboard/issues/1947
## Track RocketMQ Studio Track 1: unified control plane. ## Problem The Apache dashboard provider currently assigns `0` to `DashboardStatsVO.totalProxies`, `DashboardStatsVO.totalNameServers`, and every `ClusterOverviewVO.proxies` value regardless of the selected instance topology. The UI then renders those values as real node counts. For a direct instance, the configured endpoint can contain one or more NameServer addresses and the count is knowable. For a Proxy instance, the configured access endpoint may be a load balancer and does not reveal the number of Proxy or NameServer nodes. Reporting `0` in that case incorrectly means that the cluster has no such nodes. ## Evidence `RocketMQDashboardProvider.collectDashboardData` unconditionally builds: ```java .proxies(0) .totalProxies(0) .totalNameServers(0) ``` The home page displays `totalProxies` directly in the cluster summary. ## Expected behavior - Count configured NameServer endpoints for direct-access instances. - Represent topology counts as unavailable when the selected access path cannot discover them. - Render unavailable values as `N/A` rather than `0`. - Preserve real zero only when the architecture makes the absence known (for example, Proxy count for a direct 4.x instance). ## Proposed scope 1. Make Proxy/NameServer topology counters nullable in the dashboard response contract. 2. Derive NameServer count from normalized direct-instance endpoints. 3. Keep Proxy topology unavailable for Proxy access endpoints until a real Proxy Admin topology API is available. 4. Add backend and frontend regression tests for known zero, known count, and unavailable states. ## Verification - Direct endpoint `ns-a:9876;ns-b:9876` reports 2 NameServers and 0 Proxies. - Proxy endpoint does not claim 0 Proxy/NameServer nodes; the UI displays `N/A`. - Existing Broker, Topic, Group, and TPS dashboard data remains unchanged. -- 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]
