Aias00 opened a new issue, #1262: URL: https://github.com/apache/rocketmq-dashboard/issues/1262
## Problem Runtime Apache operations write audit records through `AuditService.record(operationType, target, detail, result)`. The textual target often embeds the cluster identifier, but the structured `AuditRecordVO.clusterId` field remains unset. This prevents the existing audit storage/export model from reliably filtering or correlating runtime actions by cluster. This is distinct from #1152: that change preserves `clusterId` when a record already has one; it does not populate the field at runtime. ## Scope - Add an explicit cluster-aware audit recording path. - Update the existing runtime write paths that already know the selected Apache cluster/instance endpoint. - Preserve the current audit target/detail/result semantics. - Add focused service/provider tests. ## Out of scope - Audit authorization changes. - New audit query APIs or schema changes. - Cloud provider operations that do not expose an Apache cluster identifier. Track 1: control-plane runtime operation observability. -- 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]
