Wang1rrr opened a new issue, #7003:
URL: https://github.com/apache/rocketmq-dashboard/issues/7003

   ### Description
   
   The bundled Grafana dashboards select and group RocketMQ 5 native message 
counters by `broker`. These counters carry `node_id` instead. As a result, the 
broker dropdown is empty, per-broker TPS queries return no series, and the 
overview's broker count collapses different brokers into one group.
   
   Upstream RocketMQ 5.3.2 sets the node ID to the broker name in 
[BrokerMetricsManager](https://github.com/apache/rocketmq/blob/rocketmq-all-5.3.2/broker/src/main/java/org/apache/rocketmq/broker/metrics/BrokerMetricsManager.java#L268-L270),
 using the label defined in 
[BrokerMetricsConstant](https://github.com/apache/rocketmq/blob/rocketmq-all-5.3.2/broker/src/main/java/org/apache/rocketmq/broker/metrics/BrokerMetricsConstant.java).
 Studio's own native metric profile already uses `node_id`.
   
   ### Reproduction
   
   Use native `rocketmq_messages_in_total` series for two brokers with 
`cluster="prod"`, distinct `node_id` values and multiple topics. With `promtool 
test rules`:
   
   - The shipped Broker Count expression returns 1 instead of 2.
   - The shipped Broker Messages In/Out TPS and Per-Broker TPS In expressions 
return no samples after selecting `broker-a`.
   - The shared broker variable queries `label_values(..., broker)`.
   
   ### Expected behavior
   
   Read the native `node_id` label in the dropdown and native counter queries, 
while keeping the existing `$broker` dashboard variable name. Update the 
generator and shipped assets together.
   
   This concerns broker selection/counting and native per-broker TPS. It is 
separate from the consumer-group selector in #6765.
   


-- 
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]

Reply via email to