Audit log
Weik.io 2026.2Weik.io records every change in the audit trail with its diff and who made it, and keeps the trail for 400 days. Video
Watch: Watching the whole installation, 3:10
The video watches the whole installation from the Home and Observability pages, then from the Health page.
This part of the video couldn't be loaded.
On this page
Weik.io writes an audit record for every change, whether you make it in the admin UI or with the weikio CLI. Use the trail to find who changed what, and to follow everything one request did.
Weik.io keeps each record for 400 days. Once the trail reaches 8 GiB, each new record pushes out the oldest. Nobody can delete records from the trail or empty it. The backend has no permission to delete the whole trail or change its 400-day or 8 GiB limit.
What is audited#
| Area | What gets a record |
|---|---|
| Changes | Every change and its diff |
| Upgrades | Every step an upgrade applied |
| Backups | Backups taken |
| Restores | Restores run and documents restored |
| Agents | Enrolments, revocations, new bundles and repoints |
| Sign-in | Sign-ins with the grants a claim mapping gave, and sign-outs |
| Accounts | Failed sign-ins and account locks, and password and authenticator changes |
| Break-glass | Break-glass windows opened and closed, and every request of a break-glass session |
| Secrets | Each reveal, and each delivery of secrets to a deployment |
| Audit trail | Every read of the trail |
An apply gets one record for the whole file and one for each document it changed. An apply from a pipeline also records the commit it applied from and that commit’s repository and branch.
What a record has#
- The time
- The actor and the caller’s address
- The action
- The target
- The outcome
- The reason given
- A correlation ID shared by everything one request did
A record of a change applied from a pipeline also has its commit, the same one that weikio describe integration shows as applied from weikio-integrations@a1b2c3d.
Query the trail#
$ weikio audit query --since 7d --target-kind secretThe command prints the records newest first, up to 1,000 in pages of 100. Each line shows the record’s fields apart from the reason and the correlation ID. The actor appears by e-mail and the action in the admin UI’s words.
| Flag | What it filters by |
|---|---|
--, or --from and --to |
The time window |
-- |
A user’s or a key’s ID |
-- |
An action, such as SecretRevealed or UpgradeStepApplied |
--, -- |
One item, such as -- |
-- |
ok, denied, refused or error |
--, --env |
A project’s or an environment’s records |
To see older records, run the command printed after the last record.
-o json prints the records and their sequence numbers as the API returns them.
To see everything one request did, run weikio audit show <correlation-id>. It prints every audit record and every log line of that correlation ID in time order.
Who may read it#
A platform administrator sees every record. A member whose grant in a project has the members verb and no limits sees that project’s records.
Everyone else follows their projects’ changes with weikio activity, which leaves out the other records, such as sign-ins and dry runs. Running weikio activity isn’t audited.
Each caller can read the trail up to 300 times a minute on each hub server. A read over that limit fails with HTTP 429 and a Retry-After header.
In the admin UI#
To read the trail in the admin UI, go to Settings › Operations › Audit log. Open a record there to see everything its request did.
To see one actor’s records, pick them in the Actors filter. For a platform administrator, the filter lists every actor:
- Users, by e-mail
- API keys, by name and ID
- Agents, by name and ID
system, for the platform’s own jobs
For a project’s admin, it lists the members of their projects.




weikio audit query line.Forward the trail to a SIEM#
The telemetry forwarder sends every audit record to Splunk or to any other system that accepts OTLP. It keeps each record on its disk until the destination accepts it.
Each record arrives as one log record with the event name weikio.audit.record. You can search on its attributes, for example:
weikio.audit.actionweikio.audit.actor.displayweikio.audit.target.nameweikio.audit.outcomeweikio.audit.origin.commitweikio.audit.diff
Telemetry forwarding shows how to set up the forwarder and how to remove repeated records.
Audit and backups#
Every backup archive contains the audit trail, so a restore brings it back. The restored trail stops before the archive’s BackupTaken record. The restore appears in the trail as a RestoreRun record that refers to the archive.