Audit Logs
The immutable control-plane activity stream — every action by a user, by Apex, by Autopilot, or by a scheduled job.
At a glance
| Route | /audit-logs |
| Section | Govern |
| Page permission | audit_logs |
What it is
The immutable control-plane activity stream. Every action taken in the platform — by a user, by Apex, by Autopilot, or by a scheduled job — is recorded with actor, timestamp, target, and payload, and cannot subsequently be altered.
In plain terms
A permanent, unchangeable record of everything anyone or anything did in the product. It matters more here than in most tools, because the product can make changes on its own — and you need to be able to check what it did.
Who it is for
Compliance and security teams, auditors, and administrators investigating what happened and who did it.
How it works
Written by the services performing the action
Audit entries are written by the services performing the action rather than reconstructed from request logs — so the record reflects business meaning rather than HTTP traffic.
"Approved remediation of 14 idle volumes" rather than "POST /api/… 200".
Retention by plan
| Plan | Audit log retention |
|---|---|
| Explorer | Not retained |
| Pro | 90 days |
| Business | 365 days |
| Enterprise | 1,095 days |
Explorer retains no audit history at all. If your organisation has any record-keeping obligation — or you intend to enable any automation — this is usually the deciding constraint when choosing a plan.
Features
- Immutable records of every control-plane action
- Actor, timestamp, target object, and payload detail per entry
- Coverage of user actions, Apex actions, Autopilot actions, and scheduled jobs
- Filtering, pagination, and sorting
- Export for external audit and archival
- Plan-governed retention
How to use it
Confirm your plan's retention meets your compliance requirement
Before you need it, not during an audit.
Use filters to narrow your investigation
To the actor, object, or time window in question.
Establish a periodic export routine
Where your retention obligation exceeds your plan's retention period. This is a standing process, not a reaction.
Review privileged actions periodically
As a security control rather than only after an incident.
Why it matters
Audit trails are unglamorous until they are the only thing standing between an organisation and a failed audit, or an unexplained change.
Connects to
- Records actions from every module
- Evidence supports Compliance
- Retention governed by Membership
- Related error history appears in Errors
Ownership
The map from cloud resources to owning teams and services, including automated inference sweeps that assign untagged resources by pattern.
Tag Governance
Tag policy definition and enforcement across cloud resources, with compliance scanning and an advisor that codifies your existing conventions.