Audit log and audit export
Search your organisation's audit log, see what each change did, undo a settings change, download the log, and copy it to your own S3-compatible bucket on a schedule.
The audit log records every settings change, sign-in, daemon enrollment and content view in your organisation, newest first. Secret values are redacted when a row is written and again when it is shown, so they are never in the log.
| Page | What | Read | Change |
|---|---|---|---|
Audit (/audit) |
search, entry details, undo, download | audit:read (owner, admin, developer) |
undo: the permission of the change being undone; download: org:manage |
Settings, Audit export (/settings/audit-export) |
a copy of the log in your bucket | audit:read |
org:manage (owner, admin) |
Find a change
Open Audit and narrow the list:
| Filter | How |
|---|---|
| Age | pills: Any time, Last day, Last 7 days, Last 30 days |
| Subject | pills built from the actions on the page (gears, budget, content, key, ...) |
| Action | click an action in a row, such as gears.updated |
| Actor | click a person in a row |
| Target | the target field: an id or a name |
| Text | the search box: actions, people, targets, details (up to 200 characters) |
Each filter shows as a chip you can remove. The list pages 100 entries at a time; "Older" loads the next page. The URL keeps the filters, for example:
/audit?age=7d&action=gears.updatedContent access shows up like any other change: content.viewed (someone opened a prompt and response), content.searched, content.exported, content.alert_evaluated, session_share.viewed.
What changed, and undo
Click an entry to open its details: who, when, the target, and the before/after diff of the change. For a reversible settings change, the dialog has Undo. Undo puts the before value back through the same operation that made the change, so that operation's permission check applies, and writes a new entry with undo_of pointing at the original.
| Action | What it changed | Undo needs |
|---|---|---|
gears.updated |
the gears | org:manage |
prompt_filters.updated |
prompt and response filters | org:manage |
budget.created, budget.updated, budget.deleted |
a budget | billing:manage or org:manage |
spend_cap.set |
the monthly spend cap | billing:manage or org:manage |
pricing.updated |
pricing | providers:write |
routing.mode_changed |
a routing policy | routing:write |
auto_routing.updated |
model choice (auto routing) | org:manage |
content.settings |
content logging | content:settings |
member.role_changed |
a member's role | members:manage |
session_sharing.settings |
session sharing | org:manage |
quality.settings |
quality checks | org:manage |
key.update |
an API key | keys:write |
key.scope |
an API key's scope | keys:write |
model_access.updated |
model access by role | org:manage |
Undo is refused (409 not_undoable) for other kinds of entry, for entries recorded before the log kept the previous value, and for changes that involve a secret. It is also refused when the change was already undone (already_undone) or the setting changed again since (changed_since).
Download the log
Owners and admins get CSV and NDJSON buttons in the page header. They download the whole filtered log (not only the shown page), newest first, at most 100,000 rows, with the columns id, ts, tenant_id, actor, action, target, detail. CSV is RFC 4180 with a header line; NDJSON is one JSON object per line. The download itself writes an audit.exported row.
Audit export to your bucket: /settings/audit-export
A copy of the org's audit log in your own S3-compatible bucket (AWS S3, Cloudflare R2, MinIO, Backblaze B2, Wasabi, ...), as NDJSON, on a schedule or on demand.
- Under Settings, Audit export, fill in the destination and Save.
- Test connection: it writes one test object and shows its key.
- Export now, or wait for the schedule.
| Field | Notes |
|---|---|
| Endpoint | empty for AWS S3; R2: https://<account>.r2.cloudflarestorage.com |
| Region | R2: auto |
| Bucket | |
| Prefix | optional folder inside the bucket |
| Access key ID | |
| Secret access key | sealed in the vault, never shown again; leave empty on later saves to keep it |
| Schedule | Hourly, Daily (default), or Off (Export now only) |
| Path-style URLs | on by default: endpoint/bucket/key; off: bucket.endpoint/key. Ignored for AWS |
Objects are named <prefix>/venom-audit/<org id>/<yyyy>/<mm>/<dd>/audit-<first row id>.ndjson, at most 10,000 rows each, with the same columns as the download. A run writes the rows after the last exported one, up to 100,000 rows; the rest follow on the next runs. Because an object is named by its first row id, a retried run rewrites the same object instead of adding a duplicate, and the watermark moves only after a write succeeds.
The run history lists each run's time, trigger, result (running, ok, failed with the reason), rows, size and objects. Saving or removing the destination and every manual run are audited (audit.exported with destination: s3); scheduled runs are recorded only in the run history, so the export doesn't keep exporting its own entries. Removing the destination leaves the objects already written in your bucket.
The deployment needs VENOM_VAULT_KEYS to store the secret key; without it the page says "The export needs the vault". Uploads go over https to a public address with no redirects.
Evidence for auditors
The cloud's audit log covers the organisation's side. For the laptop's side (signed commit receipts, approvals and policy versions), venom writes an offline-checkable bundle with venom audit export and checks it with venom audit verify-export; see Audit export in security. The org's signed compliance pack (members, keys, spend, controls) comes from Settings, Compliance, and is checked with venom compliance verify.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| No Undo button | The kind of entry isn't reversible, it involves a secret, it predates before/after recording, or your role lacks the permission in the table. |
changed_since on undo |
The setting changed again after this entry. Undo the newer entry first, or change it by hand. |
| No CSV or NDJSON buttons | Downloads need org:manage (owner, admin). |
| Test connection fails | Check the endpoint, region, bucket and keys; for MinIO and most self-hosted stores keep Path-style URLs on. The endpoint must be https and resolve to a public address. |
| "Nothing new to export." | Every row was already exported. |
Related
- Requests and request traces: where content views come from.
- Alerts
- Security: audit: the CLI's permission audit log.