Aias00 opened a new issue, #1222: URL: https://github.com/apache/rocketmq-dashboard/issues/1222
## Problem `RocketMQClusterProvider` creates each discovered Broker as `running` and the cluster as `healthy` before reading runtime statistics. When `fetchBrokerRuntimeStats` fails, the exception is logged only at debug level and the returned view is indistinguishable from a healthy runtime. ## Scope - Keep successful topology discovery available. - Add an explicit runtime-statistics availability signal to Broker/cluster views. - Mark the aggregate cluster as warning when one or more Broker runtime-stat queries fail. - Add regression coverage for successful, partial failure, and empty topology cases. ## Track Track 1 - Control Plane runtime diagnostics. -- 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]
