# List metrics — GET /v1/o11y/product/metrics URL: https://docs.hanzo.ai/docs/openapi/o11y/get-o11y-product-metrics > Returns one product's RED series — request rate, errors, p50 and p95 latency — for the caller's org, plus that org's LLM usage rollup over the same window. `GET /v1/o11y/product/metrics` > [O11y →](https://docs.hanzo.ai/docs/openapi/o11y) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides) | | | | ------------- | ---------------------------------------------- | | **Address** | `https://api.hanzo.ai/v1/o11y/product/metrics` | | **Method** | `GET` | | **Operation** | `get_o11y_product_metrics` | | **Auth** | `Authorization: Bearer $HANZO_API_KEY` | Returns one product's RED series — request rate, errors, p50 and p95 latency — for the caller's org, plus that org's LLM usage rollup over the same window. The series come from org-tagged request spans, so a tenant only ever aggregates its own traffic; a validated platform SuperAdmin sees the whole product's RED, while usage stays the caller's own org either way. A well-formed product with no backing workload answers empty series; a malformed slug is a 400. ## Request 3 fields. | Field | In | Type | Required | Description | | --------- | ----- | ------- | -------- | --------------------------------------------------------------- | | `product` | query | string | — | Product is the console product slug to read, e.g. "kms". | | `range` | query | integer | — | Range is the window in seconds. | | `stepSec` | query | integer | — | StepSec is the bucket width in seconds, clamped to \[30, 3600]. | ## Response | Status | Body | Meaning | | --------- | -------------------- | ----------------- | | `200` | o11y.metricsResponse | ok | | `202` | Approval | held for approval | | `default` | problem-details | refused | `200` body — 31 fields. | Field | In | Type | Always | Description | | -------------------------- | ---- | ------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------- | | `product` | body | string | — | Product is the service these numbers are about, echoed back. | | `range` | body | object | — | Range is the window actually used, after clamping — not what was asked for. | | `range.sinceSec` | body | integer (int64) | — | | | `range.stepSec` | body | integer (int64) | — | | | `series` | body | object | — | Series is the RED trend: request rate, error rate and two latency quantiles, bucketed at range.stepSec and oldest bucket first. | | `series.errors` | body | o11y.point\[] | — | | | `series.errors[].t` | body | string | — | T is the bucket start, RFC3339 in UTC. | | `series.errors[].v` | body | number (double) | — | V is the bucket's value. | | `series.latencyP50Ms` | body | o11y.point\[] | — | | | `series.latencyP50Ms[].t` | body | string | — | T is the bucket start, RFC3339 in UTC. | | `series.latencyP50Ms[].v` | body | number (double) | — | V is the bucket's value. | | `series.latencyP95Ms` | body | o11y.point\[] | — | | | `series.latencyP95Ms[].t` | body | string | — | T is the bucket start, RFC3339 in UTC. | | `series.latencyP95Ms[].v` | body | number (double) | — | V is the bucket's value. | | `series.requests` | body | o11y.point\[] | — | | | `series.requests[].t` | body | string | — | T is the bucket start, RFC3339 in UTC. | | `series.requests[].v` | body | number (double) | — | V is the bucket's value. | | `summary` | body | object | — | Summary totals the window in one object, so a tile does not have to sum the series to render. | | `summary.errorRate` | body | number (double) | — | | | `summary.errors` | body | integer (int64) | — | | | `summary.p95Ms` | body | number (double) | — | | | `summary.requests` | body | integer (int64) | — | | | `usage` | body | object | — | Usage is the LLM side of the same window: how many calls, how many tokens and what they cost. | | `usage.calls` | body | integer (int64) | — | | | `usage.costCents` | body | integer (int64) | — | | | `usage.series` | body | o11y.usageBucket\[] | — | | | `usage.series[].calls` | body | integer (int64) | — | Calls is how many LLM calls landed in the bucket. | | `usage.series[].costCents` | body | integer (int64) | — | CostCents is what they cost, in cents. | | `usage.series[].t` | body | string | — | T is the bucket start, RFC3339 in UTC. | | `usage.series[].tokens` | body | integer (int64) | — | Tokens is how many tokens they consumed. | | `usage.tokens` | body | integer (int64) | — | | Failure carries the platform error shape — see [Errors](https://docs.hanzo.ai/docs/errors). ## Examples **CLI** ```bash hanzo o11y product metrics ``` **SDK** **.ts** ```ts import { Configuration, O11yApi } from 'hanzoai'; const api = new O11yApi(new Configuration({ accessToken: process.env.HANZO_API_KEY })); const { data } = await api.getO11yProductMetrics(); ``` **.py** ```python from hanzoai.cloud import ApiClient, Configuration from hanzoai.cloud.api import O11yApi client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"])) result = O11yApi(client).get_o11y_product_metrics() ``` **.go** ```go cfg := hanzoai.NewConfiguration() cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY")) client := hanzoai.NewAPIClient(cfg) resp, _, err := client.O11yAPI.GetO11yProductMetrics(context.Background()).Execute() if err != nil { return err } ``` **.rs** ```rust use hanzo_client::apis::{configuration::Configuration, o11y_api}; let mut cfg = Configuration::new(); cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok(); let result = o11y_api::get_o11y_product_metrics(&cfg, Default::default()).await?; ``` **.java** ```java import ai.hanzo.cloud.ApiClient; import ai.hanzo.cloud.api.O11yApi; ApiClient client = new ApiClient(); client.setBearerToken(System.getenv("HANZO_API_KEY")); var result = new O11yApi(client).getO11yProductMetrics(); ``` **HTTP** ```bash curl https://api.hanzo.ai/v1/o11y/product/metrics \ -H "Authorization: Bearer $HANZO_API_KEY" ``` **MCP** MCP reaches **o11y** through the `o11y` tool, which names its 307 operations with its own verbs — this one among them, under a name only MCP declares. `describe` explains any of them: ```bash curl -X POST https://api.hanzo.ai/v1/mcp \ -H "Content-Type: application/json" \ -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "describe", "arguments": { "op": "list_o11y_autocomplete_aggregate_attributes" } } }' ``` --- [O11y API](https://docs.hanzo.ai/docs/openapi/o11y) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)