# Latency field

> Every run as a dot, over time. Sample data: runs from 09:35 to now, P50 2.3 s, P95 7.8 s, incident at 09:52.

- Type 106 · Distribution
- Component: `<LatencyField>`, the same name as the Figma component
- Install: `npx shadcn add @chartory/latency-field` (Code and Complete plans)
- Type page: https://usechartory.com/charts/latency-field

## Installation

1. **Set up the registry once.** Your token in .env and @chartory in components.json. Skip this when another chart is already installed. [Installation guide](https://usechartory.com/docs/installation)

2. **Add the chart.** One command adds the Latency field component to your project.

```bash
npx shadcn add @chartory/latency-field
```

3. **Use it.** Pass your rows. The props are the Figma properties.

usage.tsx:

```tsx
import { LatencyField }
  from "@/components/chartory/latency-field"

<LatencyField
  data={runLatency}
  size="m"
  legend
/>
```

## Props

### `<LatencyField>`

Every prop but data is a Figma property with the same name and values.

| Prop | Type | Default | Note |
| --- | --- | --- | --- |
| data | LatencyFieldData | Required | The chart's data. The tables below list every field. |
| size | "xs" \| "s" \| "m" \| "l" | "m" | The size class. Each one is laid out again from the data. |
| legend | boolean | true | Shows the legend row under the plot. |

### LatencyFieldData

The data prop: one object for the whole chart.

| Prop | Type | Default | Note |
| --- | --- | --- | --- |
| dots | LatencyFieldDot[] | Required | One entry per dot. |
| tmax | number | Required | The end of the time scale. |
| vmin | number | Required | The bottom of the value scale. |
| vmax | number | Required | The top of the value scale. |
| ticks | [number, string][] | Required | The axis ticks: [value, label] pairs. |
| p50 | number[] | Required | The median, per point. |
| p95 | number[] | Required | The 95th percentile, per point. |
| timeout | number | Required | The timeout. |
| sel | LatencyFieldSel | Required | The selection. |
| incident | LatencyFieldIncident | Required | The incident: time and label. |
| xl | [number, string][] | Required | The x axis labels: [position, label] pairs. |
| p50Text | string | Required | The median's label. |
| p95Text | string | Required | The 95th percentile's label. |
| timeoutText | string | Required | The timeout's label. |

### LatencyFieldDot

One object per entry in dots.

| Prop | Type | Default | Note |
| --- | --- | --- | --- |
| t | number | Required | The run's time. |
| v | number | Required | The run's latency. |
| s | "ok" \| "sel" \| "fail" | Required | The run's state: ok, selected or failed. |

### LatencyFieldSel

The sel object.

| Prop | Type | Default | Note |
| --- | --- | --- | --- |
| t0 | number | Required | The start time. |
| t1 | number | Required | The end time. |
| v0 | number | Required | The selection's lower latency. |

### LatencyFieldIncident

The incident object.

| Prop | Type | Default | Note |
| --- | --- | --- | --- |
| t | number | Required | The incident's time. |
| text | string | Required | The label as shown. |

## Latency field: a React and Figma chart in four sizes

### What does a latency field show?

A latency field draws every run as a dot by its time and its duration, with the median and P95 as lines and failures in their own colour. Slow bursts and incidents show as clouds rising. Use it for agent runs, API calls and jobs.

Chartory ships it as a Figma component and a React component with the same name. The code installs from the shadcn registry with one command and lands in your project as a file you own.

### What is the Latency field component?

It is one **<LatencyField>** component. Its props are the Figma properties with the same names and values, and the props table above lists them. The data is time, duration and status per run.

Sizes **XS**, **S**, **M** and **L** re-lay the chart out from the data instead of scaling it, so labels stay readable at every size.

### When should I use it?

- **Is every run shown?** Yes means the latency field fits.
- **Is it over time?** Yes means the latency field fits.
- **Is it many runs?** Yes means the latency field fits.

### When does another type fit better?

- **A summary per period.** Use Target trend instead.
- **One spread with no time.** Use Histogram instead.
- **One run in detail.** Use Flame graph instead.

## Latency field questions

### Does the Latency field chart work with shadcn/ui?

Yes. It installs through the shadcn registry with the shadcn CLI, and the file lands in your project.

### How do I install it?

Add your token and the @chartory registry once, then run npx shadcn add @chartory/latency-field. The Installation guide has the steps.

### Can my coding agent install it?

Yes. Connect the Chartory MCP server and ask for the latency field chart; the agent runs the same command and you review the diff.

### What data does it expect?

Time, duration and status per run. The sample data comes with the component, and the props table lists every field.

### Which sizes does it ship in?

XS, S, M and L, in Figma and in code. Each size is laid out again from the data, so text and lines keep their size.

### Is it in the Figma file too?

Yes. chart/106-latency-field has the same properties as the component.

### Does it follow light and dark mode?

Yes. Every paint is a token, so the chart follows light and dark mode and the collection you pick.

### Which plan has the code?

Code and Complete. Figma has the Figma file only.