Skip to content

What is Audit log?

An audit log is an append-only record of who did what, to which object, and when — kept separately from application logs so that it can be relied on as evidence rather than read as debugging output.

Updated

Administrative actions, scoped to the organisation, downloadable for a date range.

Operations

Audit log, explained

The difference between an audit log and an application log is intent. Application logs exist to diagnose a system and are written, rotated and discarded on operational convenience. An audit log exists to answer a question after the fact, usually a contested one, so it has to be structured, complete for the actions it claims to cover, and difficult to edit.

How Enclessa uses it

Enclessa writes a structured audit log of administrative action into its own partitioned table, scoped to the organisation, and gained an explicit organisation column as part of tenant-isolation hardening. Platform operators write to a separate audit log of their own. An administrator can download the organisation’s audit log for a date range, up to a year at a time, as JSON Lines or CSV. A live stream of the log into an organisation’s own external system is not offered.