Audit Logs
Record who did what, to which object, when, and why.
Problem
Sensitive changes need investigation and accountability beyond application logs.
When to use it
- Permissions, finance, support access, exports
- Compliance or customer trust needs evidence
When not to use it
- As a substitute for domain history
- Recording secrets or excessive personal data
Minimal example
Append actor, tenant, action, target, reason, request id, and safe before/after fields to access-controlled storage.
Tradeoffs
- Tamper evidence, retention, and access controls
- Audit data itself is sensitive