RockteMQ-AI commented on issue #2228: URL: https://github.com/apache/rocketmq-dashboard/issues/2228#issuecomment-5301300482
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** Operational audit callers do not pass `resourceType` to the audit service, causing all records to be persisted as `GENERAL`. This makes resource-type-based filtering ineffective for cluster config, broker config, topic, consumer group, message, and DLQ operations. **Impact:** Audit trail — resource-type filters cannot find operational records, reducing audit usefulness. **Severity:** Medium — affects audit query functionality but does not cause data loss. **Proposed fix:** Update operational audit callers to classify their records with the appropriate resource type (CLUSTER, BROKER, TOPIC, GROUP, MESSAGE, DLQ) while preserving backward compatibility for callers that genuinely use GENERAL. Add unit tests for classification and audit-failure isolation. An automated fix proposal can be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by github-manager* -- 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]
