jerryshao opened a new issue, #11173: URL: https://github.com/apache/gravitino/issues/11173
### Describe what's wrong `SimpleAuditLogV2.toString()` formats timestamps with `"yyyy-MM-dd HH:mm:ss"`. The underlying timestamp on the event object is a `long` representing milliseconds since epoch. Multiple events that fire within the same wall-clock second cannot be ordered from the audit log, and millisecond-precision correlation with external systems (S3 logs, VPC flow logs, SIEM events) is not possible. ### Error message and/or stacktrace `core/src/main/java/org/apache/gravitino/audit/v2/SimpleAuditLogV2.java` line 100: the timestamp format string `"yyyy-MM-dd HH:mm:ss"` truncates the millisecond precision already available in the underlying event field. ### How to reproduce Fire multiple operations in rapid succession. Observe that several audit rows share identical timestamps, with no way to determine their relative order. ### Additional context Audit row timestamps should use ISO 8601 format with at least millisecond precision and an explicit timezone offset (e.g. `2026-05-18T18:32:26.123+00:00`). Only the rendering needs to change — the underlying event timestamp is already millisecond precision. -- 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]
