Audit log
Every admin mutation in Floprints writes an audit_log row synchronously. Actor, action, target, and diff — write-or-fail by design.
Write-or-fail design
Every admin mutation writes an audit_log row synchronously. If the audit write fails, the mutation fails. There is no silent audit loss.
This makes the log defensible in compliance reviews.
What gets logged
Each entry records:
| Field | Content |
|---|---|
| Actor | User who performed the action |
| Action | Mutation type (create, update, delete, etc.) |
| Target | Resource type and ID |
| Diff | Before/after snapshot of changed fields |
| Timestamp | When the mutation occurred |
Gateway rejections and significant runtime events may also appear depending on configuration.
Console access
Admin → Audit log provides:
- Filter by actor, target type, action, date range
- Live refresh
- Detail view with full diff
Request correlation
Every log line carries a request-id propagated from middleware — one grep correlates a user report to server logs.