Loyal-Young opened a new issue, #7240: URL: https://github.com/apache/rocketmq-dashboard/issues/7240
## Problem `buildDashboardTrafficInsights` rounds percentages and per-broker TPS for display, then compares those rounded values to health thresholds. Values just below a threshold are therefore classified as though they reached it. ## Reproduction - A cluster carrying 1499 of 2500 TPS (59.96%) displays 60.0% and incorrectly gets a traffic-concentration warning at the 60% threshold. - An unhealthy cluster carrying 624 of 2500 TPS (24.96%) displays 25.0% and is incorrectly classified critical at the 25% threshold. - A throughput drop of 29.96% displays -30.0% and incorrectly triggers the 30% drop warning. - A broker at 249.99 TPS displays 250.0 TPS and incorrectly meets a 250 TPS skew threshold. ## Expected Compare the unrounded ratios and rates to thresholds. Keep rounded values for display so the UI format does not change. Add regressions around both sides of the thresholds. -- 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]
