f1amingo opened a new issue, #10644: URL: https://github.com/apache/rocketmq/issues/10644
### Before Creating the Enhancement Request - [x] I have confirmed this should be classified as an enhancement. ### Summary Add a new gauge metric `rocketmq_lmq_number` to the Broker's OpenTelemetry metrics system, exposing the current LMQ (Light Message Queue) count. ### Motivation Currently, the Broker exposes `rocketmq_topic_number` and `rocketmq_consumer_group_number` gauges but lacks visibility into LMQ count. Operators cannot monitor LMQ growth or detect potential resource exhaustion through standard metrics pipelines (Prometheus/Grafana). Adding this metric enables proactive capacity management for LMQ-heavy deployments. ### Describe the Solution You'd Like - Add `GAUGE_LMQ_NUM` constant in `BrokerMetricsConstant` - Register an `ObservableLongGauge` in `BrokerMetricsManager` that reads from `messageStore.getQueueStore().getLmqNum()` ### Describe Alternatives You've Considered Querying LMQ count via admin command (`GetParentTopicInfo`), but this is pull-based and not suitable for continuous monitoring/alerting. ### Additional Context The `getLmqNum()` API already exists in `ConsumeQueueStoreInterface` and its implementations. -- 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]
