zjncs opened a new issue, #6658:
URL: https://github.com/apache/rocketmq-dashboard/issues/6658
## Problem
The BrokerCluster page's Proxy 管理 tab renders a 连接数 (Connections) column —
and exports it to CSV — for every proxy row, but no code path ever measures
proxy connections:
- the only real-cluster discovery path (`RocketMQClusterProvider`,
heartbeat-syncer based) builds every `ProxyVO` with `.connections(0)` hardcoded;
- the page masks a missing value with `proxy.connections ?? 0`;
- only the mock/demo repository invents numbers (156).
So against a real cluster every row shows "0", which reads as *measured zero
connections*, and in demo mode it shows an invented count. This is the same
fabricated-value class as #769, and the sibling NameServer Connections column
was already removed for exactly this reason ("fabricate a hardcoded 0 for every
nameserver").
## Expected behavior
Drop the Connections column and its CSV export from the proxy tab (mirroring
the nameserver fix) until a real per-proxy connection source exists.
## Evidence
Reproduced with the frontend tests (`cd web && npx vitest run
src/pages/studio/__tests__/BrokerCluster.test.tsx`): on the current branch the
column renders with the mock's invented `2340`.
- `web/src/pages/studio/BrokerCluster.tsx`: `connections: proxy.connections
?? 0` in `mapClusters`, the `connections` column in the proxy tab, and its
`PROXY_EXPORT_COLUMNS` entry;
- server: `RocketMQClusterProvider` builds every discovered `ProxyVO` with
`.connections(0)`.
--
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]
