RockteMQ-AI commented on issue #1222: URL: https://github.com/apache/rocketmq-dashboard/issues/1222#issuecomment-5212669742
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue is valid. `RocketMQClusterProvider` pre-assigns `running`/`healthy` status before verifying runtime statistics, and failures in `fetchBrokerRuntimeStats` are only logged at debug level. This means the UI cannot distinguish a genuinely healthy cluster from one where runtime stats collection has silently failed. **Root Cause:** Status assignment precedes runtime stats validation; exception path does not downgrade health state. **Impact:** Cluster health dashboard may show false-positive healthy status during broker runtime stats outages (ACL issues, network partitions, broker overload). **Severity:** medium The proposed scope is well-defined: add an explicit availability signal, downgrade aggregate cluster health on partial failures, and add regression coverage. *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]
