create and update also accept --input-json (inline JSON, @file, or - for stdin); explicit flags override fields from the JSON. See Input JSON.
List Metrics
Output columns: ID, NAME, TYPE, CREATED
Get Metric
Create Metric
Common options
Type-specific options
Each metric type requires the options marked in the Metric Types table. Options are grouped here by the type they configure.
The following options configure other metric behaviours the API accepts; descriptions are taken from
coval metrics create --help.
Metric Types
Examples
Duplicate Metric
Create a copy of an existing metric.Update Metric
update accepts the same options as Create Metric; omitted options are left unchanged. Flags can only set a value. To clear a field, send an explicit JSON null through --input-json:
Delete Metric
Test Metric
Run a metric against one or more simulation outputs to test its behavior. This is an asynchronous operation — it returns immediately with metric output IDs that you can use to track the result.Metric Versions
List the version history of a metric definition.
Output columns: Version ID, #, Change Type, Label
Judge Models
List the models that can be used in--runtime-config when creating or updating a metric.
Baselines
Baselines learn a metric’s normal value over time and flag anomalous deviations. All baseline commands are nested undercoval metrics baselines <metric_id>.
List Baselines
Get Baseline
Create Baseline
Update Baseline
Delete Baseline
Thresholds
A threshold turns a metric’s value into a pass/fail target. Each metric has at most one threshold, soget and update take no threshold ID. All threshold commands are nested under coval metrics thresholds <metric_id>.