unbridled-41 opened a new issue, #5458:
URL: https://github.com/apache/rocketmq-dashboard/issues/5458
### Studio Version
branch: `rocketmq-studio` @ `6a68042f` (the revision verified; the branch is
based on it)
deployed as: built from source (asset regeneration check)
### Runtime Environment
Not environment-specific: the defect is in a bundled Grafana dashboard JSON.
### Connected RocketMQ Cluster
Any cluster that produces dead-letter resends.
### Describe the Bug
The bundled "RocketMQ DLQ & Retry" dashboard draws its **DLQ Resend Count
(1m)** panel — unit `short`, i.e. a count — from
```
rate(rocketmq_dlq_resend_count{cluster="$cluster"}[1m])
```
`rate()` returns the average increase per second, so the panel shows resends
per second, 60× below the per-minute count its title and unit advertise. The
sibling panel in the same bundle, "Reject Count (1m)", uses `increase(...[1m])`.
### Steps to Reproduce
1. Read `server/src/main/resources/grafana/rocketmq-dlq.json` (or import the
dashboard from the Grafana API's zip).
2. Compare the panel's `expr` with its title and unit, and with the "Reject
Count (1m)" panel of `rocketmq-threadpool.json`.
### What Did You Expect to See?
A count of resends in the selected 1-minute window.
### What Did You See Instead?
A per-second rate, 60× smaller than the count the title promises.
### Evidence
- `server/src/main/resources/grafana/rocketmq-dlq.json:101`; generator
`server/scripts/gen_grafana_dashboards.py` (DLQ panel 1).
- `cd server/scripts && python3 -m unittest test_gen_grafana_dashboards` —
the added case fails against `rate(...)` and passes against `increase(...)`;
regenerating all 12 dashboards reproduces the checked-in resources byte for
byte.
### Impact
An operator estimating resend volume from the panel under-reports it by a
factor of 60.
### Acceptance Criteria
- The panel counts resends over the window its title names.
- A regression test pins the expression.
**Corresponding PR:** #5422
--
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]
