# Replay lanes

> Where each alert went: pager, chat or digest. Sample data: alerts from Fri 9 to Fri 16, 1 paged right away, 8 to chat, 22 held for the digest.

- Type 124 · Schedule and status
- Component: `<ReplayLanes>`, the same name as the Figma component
- Install: `npx shadcn add @chartory/replay-lanes` (Code and Complete plans)
- Type page: https://usechartory.com/charts/replay-lanes

## 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 Replay lanes component to your project.

```bash
npx shadcn add @chartory/replay-lanes
```

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

usage.tsx:

```tsx
import { ReplayLanes }
  from "@/components/chartory/replay-lanes"

<ReplayLanes
  data={alertRoutes}
  size="m"
  legend
/>
```

## Props

### `<ReplayLanes>`

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

| Prop | Type | Default | Note |
| --- | --- | --- | --- |
| data | ReplayLanesData | 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. |
| color | "cat-1" \| "cat-2" \| "cat-3" \| "cat-4" | "cat-1" | The data colour of the primary marks (data/primary). |

### ReplayLanesData

The data prop: one object for the whole chart.

| Prop | Type | Default | Note |
| --- | --- | --- | --- |
| days | number | Required | The number of days. |
| dl | string[] | Required | The day labels. |
| quiet | [number, number][] | Required | The quiet ranges: [start, end]. |
| lanes | ReplayLanesLane[] | Required | One entry per lane. |
| digests | ReplayLanesDigest[] | Required | One entry per digest. |

### ReplayLanesLane

One object per entry in lanes.

| Prop | Type | Default | Note |
| --- | --- | --- | --- |
| label | string | Required | The name shown on the chart. |
| tok | string | Required | The colour token, e.g. "data/primary". |
| items | ReplayLanesItem[] | Required | One entry per item. |
| total | number | Required | The total. |
| totalText | string | Required | The total's label. |
| totalShort | string | Required | The total's label at the small sizes. |

### ReplayLanesItem

One object per entry in lanes.items.

| Prop | Type | Default | Note |
| --- | --- | --- | --- |
| d | number | Required | The day. |
| held? | boolean | false | Marks the item as held. |

### ReplayLanesDigest

One object per entry in digests.

| Prop | Type | Default | Note |
| --- | --- | --- | --- |
| d | number | Required | The day of the digest. |
| n | number | Required | The count. |

## Replay lanes: a React and Figma chart in four sizes

### What does a replay lanes show?

Replay lanes split a week of alerts into lanes by where they were sent, such as pager, chat and digest, so you see what woke people up and what waited. Use it for alert routing reviews and noise reduction.

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 Replay lanes component?

It is one **<ReplayLanes>** component. Its props are the Figma properties with the same names and values, and the props table above lists them. The data is alerts with a time and a route.

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 routing the point?** Yes means the replay lanes fit.
- **Are there lanes per route?** Yes means the replay lanes fit.
- **Is it alerts, not shifts?** Yes means the replay lanes fit.

### When does another type fit better?

- **Fires per rule.** Use Alert fire strip instead.
- **Every event in one row.** Use Event barcode instead.
- **Who is on call.** Use Rota lanes instead.

## Replay lanes questions

### Does the Replay lanes 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/replay-lanes. The Installation guide has the steps.

### Can my coding agent install it?

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

### What data does it expect?

Alerts with a time and a route. 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/124-replay-lanes 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.