oz0 usage anomalies
Usage and flags for oz0 usage anomalies.
For: Operators and developers looking up a command.
Lists the tenant's spend-anomaly findings: each UTC day whose spend was far above the median of its baseline, with the top three drivers by agent, model and plugin (by team only where works-council mode shows the team), the day's most costly jobs, what the check left out (replays, evals, shadow runs and comparisons) and the day's outside spend, shown apart. Never by person. Open findings by default; --all lists resolved ones too.
Resolve one with oz0 eval resolve ID --reason .... Tenant readers may.
Usage
oz0 usage anomalies [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--all | bool | resolved findings too | |
--json | bool | print JSON instead of a table | |
--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.