RockteMQ-AI commented on issue #2911: URL: https://github.com/apache/rocketmq-dashboard/issues/2911#issuecomment-5498255628
**Issue Evaluation** Category: `bug` | Status: **Needs Info** The issue claims "Aliyun consumer lag rows double-count the aggregate", but I could not locate the aggregation logic described. Specifically: 1. `ConsumerLagResolver` is a simple utility that resolves individual lag values (broker diff vs proxy fallback) — it does not perform any aggregation or summing. 2. `AliyunInstanceProvider` uses the Aliyun SDK's `GetConsumerGroupLag` API to fetch lag data, but I did not find any code that sums or aggregates lag values in a way that would cause double-counting. 3. The `diffTotal` field mentioned in the issue does not appear in the current codebase. Could you clarify: - Which class/method performs the aggregation that leads to double-counting? - Is this in a specific branch or version? - Can you provide a link to the specific code or a stack trace showing the double-counting behavior? Without being able to locate the problematic aggregation logic, I cannot verify the issue. --- *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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
