Configure Audit Retention
Configure Eenos automatic audit cleanup and supported retention periods, inspect event counts and database size, and distinguish policy saves from purge execution.
Open System → Activity Logs → Retention Settings.
Summary fields
| Field | Meaning |
|---|---|
| Stored Events | Count of audit events in the database, including history outside the recent table's 500-event limit. |
| Database Size | Size of the database file when readable. |
| Last Automatic Cleanup | Last recorded cleanup timestamp, when available. |
These are page-load summaries. Count or file-access failures can produce zero values, so a zero alone is not proof that the history is empty. Removing rows does not necessarily reduce the database file size immediately.
Automatic Audit Cleanup
| Field | Choices and behavior |
|---|---|
| Enable automatic cleanup | Enables age-based removal when the cleanup task runs. Turning it off retains events from this automatic policy. |
| Retention Period | 30, 60, 90, 120, 180, 365 or 730 days. Events older than the selected period are eligible for cleanup. |
The default policy is automatic cleanup enabled with 120 days, also marked recommended in the interface. Review the displayed policy for your server. Explicitly disabling automatic cleanup prevents that cleanup task from deleting events; it does not prevent manual deletion from Recent Activity.
Choose the switch and period, then Save Retention Settings. The period remains a required supported choice even while automatic cleanup is off. The page reports validation or persistence failures; a successful save records a retention-settings activity event. Demo sessions cannot save changes.
Save versus cleanup execution
Saving updates policy and preserves the last-cleanup timestamp. It does not immediately run a purge or install the scheduled cleanup job. Automatic removal depends on the separate audit cleanup task being scheduled and executed. Verify that task and the last-cleanup result before relying on ongoing retention.
When cleanup runs, it removes events older than the UTC cutoff calculated from the retention period and records its completion timestamp. A shorter period can make more existing history eligible at the next execution. Increasing retention cannot recover events already deleted.
Review retention before shortening it
Cleanup permanently removes eligible audit records. Preserve history needed for investigation or recordkeeping before shortening the period or enabling cleanup. A saved policy and a successful cleanup are separate outcomes.
Use View Recent Activity to return to the event table. Do not use its Empty Audit Log control as a substitute for an age-based retention policy.