yyqdbngt opened a new issue, #2188: URL: https://github.com/apache/rocketmq-dashboard/issues/2188
### What happened? The RocketMQ 5 native metrics profile maps semantic broker health to `rocketmq_processor_watermark`. That metric represents request-processor queue watermarks, not scrape or broker availability: a healthy idle broker can report zero and a busy broker can report a positive value. The profile therefore exposes load as an `up`-style health signal. ### Expected behavior Use the Prometheus `up` series for the RocketMQ 5 broker-health semantic metric, consistent with the existing RocketMQ 4 profile and the semantic metric's availability meaning. ### Reproduction Resolve `broker_health` from the `rocketmq5-native` metric profile. The generated query currently aggregates processor watermarks rather than checking whether the broker target is scrapeable. -- 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]
