Skip to content

Commit a851c8d

Browse files
Feediver1micheleRP
andauthored
DOC-1485: Fix doc reference to configurable audit log retention (#1338)
Co-authored-by: Michele Cyran <michele@redpanda.com>
1 parent 43b5128 commit a851c8d

1 file changed

Lines changed: 11 additions & 1 deletion

File tree

modules/manage/partials/audit-logging.adoc

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -397,7 +397,17 @@ ifdef::env-cloud[]
397397

398398
== Configure retention for audit logs
399399

400-
Assess the retention needs for your audit logs. You may not need to keep the logs for the default seven days. This is controlled by setting the `retention.ms` property for the `_redpanda.audit_log` topic.
400+
You can export audit events to your SIEM for long-term retention to support audit and compliance needs. Redpanda Data recommends that you retain audit logs for at least one year in a separate system like your SIEM, so if there is an issue with the Redpanda cluster you have access to the audit logs.
401+
402+
If you need to change the default seven-day retention period, update the retention settings using the `retention.ms` property for the `_redpanda.audit_log` topic:
403+
404+
[,bash]
405+
----
406+
# Set 1-year retention (in milliseconds) on the audit log topic
407+
rpk topic alter-config _redpanda.audit_log --set retention.ms=31536000000
408+
----
409+
410+
NOTE: In Redpanda Cloud, both `retention.ms` (time-based) and `retention.bytes` (size-based) retention policies are applied simultaneously. Data becomes eligible for deletion when either limit is reached, depending on whichever occurs first. This means neither setting strictly takes precedence; the earliest limit (by time or size) triggers data cleanup. When updating audit log retention, check to make sure you do not already have a size-based retention policy that might remove logs before the period you specify.
401411

402412
== Next steps
403413

0 commit comments

Comments
 (0)