RockteMQ-AI commented on issue #4611:
URL:
https://github.com/apache/rocketmq-dashboard/issues/4611#issuecomment-5751646225
**Issue Evaluation**
Category: `bug` | Status: **Confirmed**
The bug is confirmed. There is a key shape mismatch within
`clientConnectionDiagnostics.ts`:
- Per-connection issue producers (`addUnknownFieldIssues` at `:292`,
`addClientIdIssues` at `:277`) set `resource` to the bare normalized name
(e.g., `my-group`).
- Resource summary matching (`issuesForResource` at `:474-475`) compares
against the type-qualified key `${group.type}:${group.resource}` (e.g.,
`Consumer:my-group`).
The equality filter `issue.resource === resource` therefore never matches,
causing `buildResourceSummaries` to compute `issueCount: 0` and `status:
healthy` for every resource that only has per-connection issues.
**Impact:** The resource-dimension table silently under-reports. Operators
see all-green rows while the connection-level issues panel simultaneously shows
warnings for the same resources.
**Severity:** Medium — diagnostic accuracy is compromised; no data mutation
risk.
The existing tests only cover resource-level issues (which use the qualified
key), which is why the mismatch was never caught.
---
*Automated evaluation by RocketMQ AI Assistant*
--
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]
