yuluo-yx opened a new issue, #2228: URL: https://github.com/apache/rocketmq-dashboard/issues/2228
### Problem\n\nOperational actions recorded through the legacy AuditService do not set resourceType. The repository consequently stores them as GENERAL, even for cluster configuration, broker configuration, Topic, Consumer Group, message, and DLQ operations. Resource-type filters therefore cannot find those records.\n\n### Expected behavior\n\nEvery operational caller should provide its actual resource type while preserving the existing audit target, cluster identifier, detail, result, and best-effort failure behavior.\n\n### Reproduction\n\n1. Update cluster or broker configuration, send a message, reset an offset, or resend a DLQ message.\n2. Query audit records by the corresponding resource type.\n3. The record is absent because it was persisted as GENERAL.\n\n### Acceptance criteria\n\n- Operational audit callers classify their records as CLUSTER, BROKER, TOPIC, GROUP, MESSAGE, or DLQ.\n- The old AuditService entry point remains compatible for callers that genuinely use GENERA L.\n- Unit tests cover classification and audit-failure isolation. -- 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]
