crewship metrics
Fetch mission performance metrics or pull a metric timeseries. Without flags, returns the mission summary — success rate, p50/p99 durations, total runs over the last default window. With--series <name>, switches to a timeseries endpoint and returns time-bucketed points.
requireAuthAndWorkspace).
The output is always structured JSON (or YAML with --format yaml). Pipe through jq or use --filter for ad-hoc shapes — there is no canonical table form for the records returned.
Flags
| Flag | Default | Purpose |
|---|---|---|
--series <name> | "" | Fetch a timeseries for the named metric instead of the mission summary. Routes to /api/v1/metrics/timeseries. |
--range <window> | 24h | Window for --series — 1h, 24h, 7d are the supported sugar values. |
--filter <jq-expr> | "" | Pipe JSON output through jq <expr> (requires jq in $PATH). |
--format flag (table / json / yaml / ndjson / quiet) is honoured. The default is indented JSON because the data here is structured records without a single canonical “table” shape.
Endpoints
| Mode | Endpoint |
|---|---|
| Default | GET /api/v1/mission-metrics |
--series <name> | GET /api/v1/metrics/timeseries?metric=<name>&range=<window> |
Examples
Mission summary
Active-runs timeseries over the last hour
Week-long window
Pull a single field via jq
YAML output
Pipe to a chart
See also
crewship paymaster— cost-oriented view of the same underlying data.crewship telemetry— distributed-trace observability across crews.crewship journal— per-agent execution events behind the metrics aggregation.crewship history— individual run records that feed the success-rate and duration percentiles.