You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "yyqdbngt (via GitHub)" <gi...@apache.org> on 2026/08/14 06:52:46 UTC
[I] RocketMQ 5 broker health profile uses processor load instead of availability [rocketmq-dashboard]
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: commits-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] RocketMQ 5 broker health profile uses processor load instead of availability [rocketmq-dashboard]
Posted by "RockteMQ-AI (via GitHub)" <gi...@apache.org>.
RockteMQ-AI commented on issue #2188:
URL: https://github.com/apache/rocketmq-dashboard/issues/2188#issuecomment-5291110952
**Issue Evaluation**
Category: `unknown` | Status: **Evaluated**
Thank you for your report. A maintainer will review.
---
*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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] RocketMQ 5 broker health profile uses processor load instead of availability [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #2188: RocketMQ 5 broker health profile uses processor load instead of availability
URL: https://github.com/apache/rocketmq-dashboard/issues/2188
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] RocketMQ 5 broker health profile uses processor load instead of availability [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #2188:
URL: https://github.com/apache/rocketmq-dashboard/issues/2188#issuecomment-5376659786
This issue has been automatically closed because there has been no activity for 7 days. If you believe this issue is still relevant, please reopen it with updated information.
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org