# TaskAgentMetrics

> API reference for Task Agent Metrics (metrics.clrk.apoxy.dev/v1alpha1)

**API Group:** `metrics.clrk.apoxy.dev/v1alpha1`

## Operations

### List TaskAgentMetrics

<APIEndpoint method="GET" path="/apis/metrics.clrk.apoxy.dev/v1alpha1/namespaces/{namespace}/taskagentmetrics" />

list objects of kind TaskAgentMetrics

**Response**

- `200`: OK

---

### List TaskAgentMetrics

<APIEndpoint method="GET" path="/apis/metrics.clrk.apoxy.dev/v1alpha1/taskagentmetrics" />

list objects of kind TaskAgentMetrics

**Response**

- `200`: OK

---

### Get TaskAgentMetric

<APIEndpoint method="GET" path="/apis/metrics.clrk.apoxy.dev/v1alpha1/namespaces/{namespace}/taskagentmetrics/{name}" />

Get the specified TaskAgentMetrics

**Response**

- `200`: OK

---

### Query TaskAgentMetrics series

<APIEndpoint method="GET" path="/apis/metrics.clrk.apoxy.dev/v1alpha1/namespaces/{namespace}/taskagentmetrics/{name}/series" />

Runs a metric query and returns a `MetricSeriesSet`. The query parameters (`metric`, `groupBy`, `since`, `until`, `step`, `quantiles`, `scopeKind`, `scopeName`) and the response shape are documented in [Query fleet metrics](/docs/clrk/guides/query-fleet-metrics.md).

---

## Schema Reference

### TaskAgentMetrics

| Field | Type | Description |
| --- | --- | --- |
| `timestamp` | [Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta) | Timestamp is when the rollup was computed (the query time). **(required)** |
| `usage` | object | Usage is the scalar rollup. See the Usage* key constants. **(required)** |
| `window` | [Duration](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#duration-v1-meta) | Window is the look-back the usage values cover, e.g. 24h. Making the window self-describing on every object resolves the telemetry read model's standing ambiguity, where an unset since/until means "the latest N records" rather than a stated span. **(required)** |
