Skip to main content
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

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. Since Nelkap starts pending runs every minute, a queue wait of up to a minute is normal.