Every execution in Cargo — a tool run, a play batch, an agent message — is observable from the terminal. Runs, batches, spans, and traces all have list, get, and metrics commands.
Runs and batches
A batch with status: success can still contain individual run failures —
always check failedRunsCount.
Spans and traces
Drill into a single execution’s node-by-node breakdown:
trace list requires --started-after, and span list requires
--execution-started-after — both accept an ISO date. The uuid flags narrow
the results but are optional.
Metrics
get-metrics returns per-node execution status counts and credits used, filterable by release, batch, or date range — so you can spot regressions between deploys.
Alerts
An alert makes this telemetry watch itself. It runs on a cron, computes a metric over the spans since its last tick — error rate, a duration percentile, credits, or span count — and fires actions as runs when the value breaches a threshold. Define one with defineAlert, or drive it from the CLI:
A play can also declare its own batch-health threshold and alert actions — see Plays.
Using the UI
Each tool and play also has Records and Metrics views in the web app — filter by status, version, batch, or date; inspect any execution node-by-node; and retry failed runs individually or in bulk (from scratch or from the failed node). 
