oz0 audit export

Export one hash chain of the audit log as JSON lines: a tenant's with --tenant, the cluster's own without.

For: Operators and developers looking up a command.

Export one hash chain of the audit log as JSON lines: a tenant's with --tenant, the cluster's own without. Each line carries the entry, its place in the chain and its hashes, and the last line is the chain's head, so audit verify --file checks an export without the cluster.

Without the content permission, each entry's private part (what a job read or wrote) is left out and its hash kept, and the digests in its detail are keyed for this one export, so they cannot confirm a guess of what they cover: equal digests stay equal within the export. Such an entry is marked blinded and has no salt, which would confirm a guess too.

Every export's head is signed with the audit key, which stands in for what such an entry's hashes would show and says whose the export is. The export is recorded in the chain (audit.export).

With --follow the command keeps running and writes new entries as they come, each batch followed by a head line, for a SIEM to read; the session is recorded once (audit.follow), not at every poll.

Usage

oz0 audit export [flags]

Flags

FlagTypeDefaultDescription
--afterintonly entries after this seq, such as the last one of an earlier export
--clusterboolexport the cluster's own chain
--followboolkeep running and write new entries as they are recorded
--output (-o)stringwrite to this file instead of stdout
--sincestringonly entries recorded at or after this time (RFC 3339)
--tenantstringthe cluster's own, for cluster adminsexport this tenant's chain
--untilstringonly entries recorded before this time (RFC 3339)

Inherited flags

FlagTypeDefaultDescription
--contextstring$OZ0_CONTEXT or <config dir>/orchestrator-zero/context.jsonCLI context file written by server init
--log-levelstringinfolog level: debug, info, warn or error

See all oz0 commands and the global flags.

On this page
Copyright © 2026