Fix: Add audit log timestamp precision documentation for all affected versions (product-is#26581)

- Add configuration section for next version with log_mgt.audit_log.truncate_to_microseconds config
- Add note about nanosecond precision change for versions 7.1 and 7.2
- Document recordedAt field precision behavior with Java 21 support

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: wso2-engineering-bot

en/identity-server/7.1.0/docs/deploy/monitor/monitor-logs.md

@@ -95,6 +95,9 @@ appender.AUDIT_LOGFILE.filter.threshold.level = INFO
 
 The log levels that can be configured are [listed below](#set-the-log4j-log-level).
 
+!!! note "Audit log timestamp precision"
+    With Java 21 support in WSO2 Identity Server 7.1, the timestamps in audit logs (v2 version) can have nanosecond precision due to the Java upgrade. This change affects the `recordedAt` field in the audit log.
+
 ### Configure HTTP access logs
 
 See [HTTP Access Logging]({{base_path}}/deploy/monitor/http-access-logging) for instructions on how to configure and use HTTP access logs.

en/identity-server/7.2.0/docs/deploy/monitor/monitor-logs.md

@@ -95,6 +95,9 @@ appender.AUDIT_LOGFILE.filter.threshold.level = INFO
 
 The log levels that can be configured are [listed below](#set-the-log4j-log-level).
 
+!!! note "Audit log timestamp precision"
+    With Java 21 support in WSO2 Identity Server 7.2, the timestamps in audit logs (v2 version) can have nanosecond precision due to the Java upgrade. This change affects the `recordedAt` field in the audit log.
+
 ### Configure HTTP access logs
 
 See [HTTP Access Logging]({{base_path}}/deploy/monitor/http-access-logging) for instructions on how to configure and use HTTP access logs.

en/identity-server/next/docs/deploy/monitor/monitor-logs.md

@@ -95,6 +95,19 @@ appender.AUDIT_LOGFILE.filter.threshold.level = INFO
 
 The log levels that can be configured are [listed below](#set-the-log4j-log-level).
 
+#### Configure audit log timestamp precision
+
+Starting from Java 21 support in WSO2 Identity Server, the timestamps in audit logs (v2 version) can have nanosecond precision due to the Java upgrade. This change affects the `recordedAt` field in the audit log.
+
+To maintain microsecond precision and avoid this behavior change, add the following configuration to the `deployment.toml` file in `<IS_HOME>/repository/conf/`:
+
+```toml
+[log_mgt]
+audit_log.truncate_to_microseconds = true
+```
+
+When this configuration is set to `true`, the timestamp values in audit logs are forcefully truncated to microsecond precision instead of nanosecond precision.
+
 ### Configure HTTP access logs
 
 See [HTTP Access Logging]({{base_path}}/deploy/monitor/http-access-logging) for instructions on how to configure and use HTTP access logs.