oz0 job export
Usage and flags for oz0 job export.
For: Operators and developers looking up a command.
Write a job as one JSON document for an incident review or a support case: the job, its trace (each step with its timing, node, tokens and cost), its findings and tags. --content adds what each step read and wrote, which needs the content permission and is in the audit log, up to 16 MiB of it (the steps past that are listed in steps_omitted).
The tenant's secrets of 6 characters or more are replaced by [redacted:<name>] wherever they appear; shorter ones are not, as they would replace ordinary words.
Usage
oz0 job export JOB [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--content | bool | include what each step read and wrote (needs the content permission; audited) | |
--output (-o) | string | stdout | file to write |
--tenant | string | default | tenant |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.