Commands

up0 metrics

Metric catalog and range queries

up0 metrics

Metric catalog and range queries

up0 metrics ls

List metric names the organization has emitted in the range, with type and series count.

Usage: up0 metrics ls [OPTIONS]
NameTypeDefaultDescription
--sincestring-Relative lookback, e.g. 15m, 1h, 24h, 7d — mutually exclusive with --start/--end (default: last 1h)
--startstring-Range start, ISO 8601 — mutually exclusive with --since
--endstring-Range end, ISO 8601 — mutually exclusive with --since
--jsonbooleanfalseEmit the API response as JSON
--org-idstring-Organization ID (or set UP0_ORG_ID) (env: UP0_ORG_ID)

up0 metrics query

A bucketed, aggregated time series for one metric over a range.

Counters are reported as their raw cumulative value, not rate-corrected -- metric_type in the output says which case you are in. An empty bucket's value is null for every aggregation except sum/count, which have a well-defined 0 for "nothing in this bucket". The CLI does not compute quantiles itself; --aggregation quantile is passed straight to the API, which does.

Usage: up0 metrics query [OPTIONS]
NameTypeDefaultDescription
--metric-namestringrequiredExact metric_name — required, one metric per request
--sincestring-Relative lookback, e.g. 15m, 1h, 24h, 7d — mutually exclusive with --start/--end (default: last 1h)
--startstring-Range start, ISO 8601 — mutually exclusive with --since
--endstring-Range end, ISO 8601 — mutually exclusive with --since
--aggregationchoice (sum, avg, min, max, count, quantile)avgAggregation applied per bucket
--quantilefloat-Fraction in [0, 1] — required iff --aggregation quantile, rejected otherwise (enforced by the API, not duplicated here)
--group-bystring-Label key to split into its own series (repeatable, up to 10)
--jsonbooleanfalseEmit the API response as JSON
--org-idstring-Organization ID (or set UP0_ORG_ID) (env: UP0_ORG_ID)

On this page