# Metrics reference

> Source: https://docs.clonepartner.com/reference/metrics/

Envoy records execution metrics for tasks, steps, and connector operations. Metrics support live run views and operational monitoring without replacing run status or logs.

## Backend selection

Supported metrics backends include:

- `noop` when collection is disabled;
- `sqlite` for local persistence;
- `statsd` for forwarding counters and timing data to a compatible collector.

Availability and configuration can vary by deployment build. Keep the metrics path separate from the application database backup and run-log plan.

## Metric categories

### Task and run

- run start and completion;
- elapsed duration;
- terminal status;
- total processed and emitted items;
- errors and skips.

### Step

- input and output counts;
- errors;
- duration or processing time;
- throughput indicators;
- batch behavior.

### Connector

- method calls;
- request duration;
- failures;
- records or pages where reported.

Exact metric names and tags depend on the backend and deployed version.

## Live and durable values

The run page receives live updates while execution is active. Persisted metrics are the post-run source for review. A browser disconnection does not stop execution or invalidate already stored data.

Counters can update in intervals rather than after every record. Treat a temporary flat line as an observation to investigate, not proof of a stuck task.

## Labels and cardinality

Useful bounded labels include environment, task name, step name, connector type, and status. Avoid unbounded labels such as record ID, email address, raw error message, or full URL.

High-cardinality labels increase storage and query cost and can expose sensitive data.

## Interpretation

- **Input rises, output flat:** filter, errors, buffering, or slow downstream.
- **Errors rise with request rate:** provider validation, authorization, or throttling.
- **Duration rises without volume change:** upstream latency, destination contention, or resource pressure.
- **Output exceeds input:** an array-producing step expands records.
- **Processed count differs from destination count:** skips, deduplication, partial failures, or non-record outputs.

Reconcile metrics with logs, mapping state, and destination queries.

## Operational checks

1. Run a known small task.
2. Verify task and step counters.
3. Verify completion duration.
4. Trigger one controlled failure.
5. Confirm the error counter and terminal status.
6. Check backend retention and storage growth.
7. Verify dashboards do not depend on unbounded labels.

See [Operations metrics](/operations/metrics) and [Debugging](/reference/debugging).