Loyal-Young opened a new issue, #6905: URL: https://github.com/apache/rocketmq-dashboard/issues/6905
### Before Creating the Bug Report - [x] I searched existing issues and open pull requests for the collector-status badge and its current wording. - [x] Reproduced on the current `rocketmq-studio` branch. ### Studio Version `rocketmq-studio` at `a92c23144408cdf5729707050e9ecd9b75f1bad0`. ### Runtime Environment The System Alerts page. A component test supplies both zero and nonzero collector component counts; no broker is required. ### Describe the Bug The System Alerts page labels a successful collector-status response as "Native collection enabled" with a green check. The endpoint reports the configured collection interval and the number of registered cluster and business collector components. It does not report whether collection is enabled, running, or healthy. Thus the page can assert an operational state it has not measured, including when both counts are zero. ### Steps to Reproduce 1. Open System Alerts with the collector-status endpoint returning `clusterCollectorCount: 0` and `businessCollectorCount: 0`. 2. Observe the green "Native collection enabled" badge. ### What Did You Expect to See? Show the collector component counts returned by the endpoint with neutral styling. Do not infer runtime health from an HTTP response or component count. ### What Did You See Instead? The page claims that native collection is enabled even when the response reports no collector components. ### Additional Context The proposed UI-only change uses the existing API response and adds regression cases for zero and nonzero counts. ### Are You Willing to Submit a Pull Request? - [x] Yes. -- 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]
