Retention¶

control.audit.retention

Retention and protection¶

The journal lives in the same database as the rest of the machine's state and survives a restart of the process. It creates no files on disk.

Records are only ever appended: editing or deleting an individual record exists neither in the console nor in the API. Retention — seven days by default — is set by the audit_log_ttl_secs process setting in /etc/mcaster/, and the console cannot change it. That is deliberate: whoever wants to hide their action must not be able to shorten retention with the same access that let them perform it. A value of zero means "keep everything", not "wipe everything".

Against someone with access to the database itself the journal offers no protection and promises none.