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.
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 - 2
Add the chart
One command adds the Latency field component to your project.
npx shadcn add @chartory/latency-field - 3
Use it
Pass your rows. The props are the Figma properties.
usage.tsximport { 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.
LatencyFieldData
The data prop: one object for the whole chart.
LatencyFieldDot
One object per entry in dots.
LatencyFieldSel
The sel object.
LatencyFieldIncident
The incident object.
The data as a JSON Schema: schemas/latency-field.json
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
Installing, data, Figma and plans.
Yes. It installs through the shadcn registry with the shadcn CLI, and the file lands in your project.
Add your token and the @chartory registry once, then run npx shadcn add @chartory/latency-field. The Installation guide has the steps.
Yes. Connect the Chartory MCP server and ask for the latency field chart; the agent runs the same command and you review the diff.
Time, duration and status per run. The sample data comes with the component, and the props table lists every field.
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.
Yes. chart/106-latency-field has the same properties as the component.
Yes. Every paint is a token, so the chart follows light and dark mode and the collection you pick.
Code and Complete. Figma has the Figma file only.