Skip to content

Replay lanes

Where each alert went: pager, chat or digest.

Definition · Updated Nov 2, 2026

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.

Pay once. Every update included.

Live preview

Last week's alerts replayed under the rulesOver 8 days (FRI 9 to FRI 16): pager 1 right away, chat 8 right away, digest 22 held; 7 digests carried 22 held alerts.PAGERCHATDIGEST1NOW8NOW22HELD3344242FRI 9SUN 11WED 14FRI 16PAGERCHATHELDDIGEST SENT
Last week's alerts replayed under the rules
Digest sentAlerts in it
SAT 103
SUN 113
MON 124
TUE 134
WED 142
THU 154
FRI 162

Sample data: alerts from Fri 9 to Fri 16, 1 paged right away, 8 to chat, 22 held for the digest

Size
Legend
Data shape
Alerts with a time and a route
Good for
Alert routing, noise reviews
Avoid when
All alerts go one way
Sizes
XS, S, M and L, re-laid out from the data

Anatomy

Inspect it like the Figma file.

The same layers, names and tokens as the component. Select one to read its size, fill and style.

Layers

124 / Replay lanes

chart/124-replay-lanes
plot · replay lanes
Layer
day · 0.29
Type
Rectangle
Size
49 × 219
Fill
surface/card
Group
Marks · 55

Layers

124 / Replay lanes

chart/124-replay-lanes
plot · replay lanes
Layer
day · 0.29
Type
Rectangle
Size
14 × 108
Fill
surface/card
Group
Marks · 55

Sizes

Re-laid out, never scaled.

The same data at XS, S, M and L. Every size is redrawn from the data, so text and line weights never shrink.

M against S

Width360 px480 px

Plot328 px440 px

Labels2020

Marks5555

Height212 px246 px

Same tokens at every size: text styles, 1 px lines and mark radius stay put.

When to use

What woke people up.

Three signs it fits, and three signs another type fits better.

Is routing the point?

Fires per rule.

Yes: Keep the replay lanes

Are there lanes per route?

Every event in one row.

Yes: Keep the replay lanes

Is it alerts, not shifts?

Who is on call.

Yes: Keep the replay lanes

Code and Figma

One name in Figma and in code.

Every Figma property is a prop with the same name and values. One command installs it.

Figma

chart/124-replay-lanes

size
legend
Property = propValuesDefault
size"xs" · "s" · "m" · "l""xs"
legendtrue · falsetrue
color"cat-1" · "cat-2" · "cat-3" · "cat-4""cat-1"
npx shadcn add @chartory/replay-lanes
replay-lanes.tsx
import { ReplayLanes } from "@/components/chartory/replay-lanes"import { alertRoutes } from "./alert-routes"export function AlertRoutes() {  return (    <ReplayLanes      data={alertRoutes}      size="m"      legend={true}    />  )}

Hearth widget

Replay lanes as a widget.

The chart in a Hearth card with a hero number and two blocks. One token set, light and dark.

Get the code

EmberPreset

ChartoryDefault preset

Pick the blocks, the size and the preset for your own widget.

Read the Hearth widget docs

FAQ

Replay lanes questions.

What people ask before they put replay lanes in a dashboard.

Something else?

hello@usechartory.com
  • How many alerts took that route (1 to the pager right away, 8 to chat, 22 held for the digest).

Related types

The same question, a different shape of answer. Every type ships in Figma and in code.

Same family

Schedule and status

19 types in Chartory answer this question.