> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nelkap.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Metrics

> Watch the health of your runs over time: how many start, wait, run, and fail, and how long they take.

Metrics chart your runs over time, so you see a problem build up before it hits your customers: a backlog that keeps growing, runs that take longer each day, an error rate that climbs after a deploy. They're computed from your runs, with nothing to set up in your code.

## Choose what you see

* Period: the last hour, 24 hours, 3 days, 7 days, 15 days, or 30 days. The last hour is charted minute by minute, the last 24 hours hour by hour, and longer periods day by day.
* Project: one project, or the whole workspace, chosen at the top of the page.

Metrics are updated every minute. Times are shown in your own time zone.

## The charts

| Chart | What it shows | What to watch for |
| - | - | - |
| Backlog | Pending runs, waiting for their turn, and ready runs, on their way to your app. | A backlog that keeps growing: runs come in faster than they're let through. |
| Concurrency | Runs your app is running. | A flat line at your limit: runs are waiting for a turn. |
| Suspended | Sleeping and waiting runs. | Waiting runs piling up: the events that should wake them may not come. |
| Outcomes | Runs that completed, failed, or were canceled, by the time they ended. | A rise in failed runs. |
| Triggers | Runs started from your code, by events, by schedules, and by replays. | A drop: something stopped starting runs. |
| Latency | How long runs take from creation to end, and how long they wait before they start, at the median and the 95th percentile. | Queue wait climbing: runs wait longer for a turn. |
| Error rate | Failed runs, out of those that completed or failed. | A jump right after a deploy. |

The median is the time half of the runs stay under. The 95th percentile is the time 95 runs out of 100 stay under, so it shows the slowest runs without being thrown off by a single one.

## Read the latency chart

A run's time from creation to end includes its sleeps and waits. A workflow that sleeps a day takes at least a day, even if its steps take a second. So compare latency with itself over time, rather than with a fixed number.

Queue wait is the time between a run's creation and its start. It rises when runs wait for a turn under a [concurrency limit](https://docs.nelkap.com/guides/concurrency.md). Since Nelkap starts pending runs every minute, a queue wait of up to a minute is normal.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.