Skip to content
DocsChartsIncident tapeLast updated Nov 2, 2026

Incident tape

One incident, minute by minute. Sample data: P95 run time during one incident, 09:30 to 10:40, first over 8 s at 09:42, 6 min from alert to acknowledged.

p95 run time through an incidentp95 run time per minute from 09:30: 4.4 s at the start, over the 8 s threshold from 09:42 and 8.14 s now at 10:33; alert at 09:52, acknowledged at 09:58, model switch at 10:12.8 S09:40 RISING09:42 OVER 8 S09:52 ALERT09:53 PAGED09:58 ACK10:12 SWITCH09:3009:4009:5010:0010:1010:2010:3010:40P95 RUN TIMEOVER 8 SACKNOWLEDGEDFIX PROPOSED
p95 run time through an incident
Timep95 run time (s)Event
09:304.4
09:314.54
09:324.43
09:334.54
09:344.58
09:354.43
09:364.45
09:374.6
09:384.62
09:394.64
09:404.66RISING
09:414.95
09:428.04OVER 8 S
09:435.77
09:446.1
09:456.22
09:466.7
09:477.01
09:487.12
09:497.48
09:507.96
09:518.16
09:528.45ALERT
09:538.26PAGED
09:548.14
09:558.53
09:568.15
09:578.52
09:588.44ACK
09:598.16
10:008.16
10:018.48
10:028.49
10:038.2
10:048.54
10:058.15
10:068.37
10:078.19
10:088.11
10:098.18
10:108.18
10:118.14
10:128.32SWITCH
10:138.49
10:148.4
10:158.55
10:168.32
10:178.24
10:188.55
10:198.1
10:208.24
10:218.35
10:228.17
10:238.21
10:248.33
10:258.24
10:268.33
10:278.43
10:288.11
10:298.4
10:308.33
10:318.32
10:328.46
10:338.14
p95 run time through an incidentp95 run time per minute from 09:30: 4.4 s at the start, over the 8 s threshold from 09:42 and 8.14 s now at 10:33; alert at 09:52, acknowledged at 09:58, model switch at 10:12.8 SRISINGOVERALERTPAGEDACKSWITCH09:3009:5010:1010:2010:40P95 RUN TIMEOVER 8 SACKNOWLEDGEDFIX PROPOSED
p95 run time through an incident
Timep95 run time (s)Event
09:304.4
09:314.54
09:324.43
09:334.54
09:344.58
09:354.43
09:364.45
09:374.6
09:384.62
09:394.64
09:404.66RISING
09:414.95
09:428.04OVER 8 S
09:435.77
09:446.1
09:456.22
09:466.7
09:477.01
09:487.12
09:497.48
09:507.96
09:518.16
09:528.45ALERT
09:538.26PAGED
09:548.14
09:558.53
09:568.15
09:578.52
09:588.44ACK
09:598.16
10:008.16
10:018.48
10:028.49
10:038.2
10:048.54
10:058.15
10:068.37
10:078.19
10:088.11
10:098.18
10:108.18
10:118.14
10:128.32SWITCH
10:138.49
10:148.4
10:158.55
10:168.32
10:178.24
10:188.55
10:198.1
10:208.24
10:218.35
10:228.17
10:238.21
10:248.33
10:258.24
10:268.33
10:278.43
10:288.11
10:298.4
10:308.33
10:318.32
10:328.46
10:338.14

Installation

  1. 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. 2

    Add the chart

    One command adds the Incident tape component to your project.

    npx shadcn add @chartory/incident-tape
  3. 3

    Use it

    Pass your rows. The props are the Figma properties.

    usage.tsx
    import { IncidentTape }  from "@/components/chartory/incident-tape"<IncidentTape  data={incidentSteps}  size="m"  legend/>

Props

<IncidentTape>

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

PropTypeDefault
data: The chart's data. The tables below list every field.IncidentTapeDataRequired
size: The size class. Each one is laid out again from the data."xs" | "s" | "m" | "l""m"
legend: Shows the legend row under the plot.booleantrue
color: The data colour of the primary marks (data/primary)."cat-1" | "cat-2" | "cat-3" | "cat-4""cat-1"

IncidentTapeData

The data prop: one object for the whole chart.

PropTypeDefault
vals: The values, in order.number[]Required
span?: The time span.number—
min: The bottom of the value scale.numberRequired
max: The top of the value scale.numberRequired
thr: The threshold.numberRequired
thrText: The threshold's label.stringRequired
now: Where now is on the axis.numberRequired
xl: The x axis labels: [position, label] pairs.[number, string][]Required
events: One entry per event.IncidentTapeEvent[]Required

IncidentTapeEvent

One object per entry in events.

PropTypeDefault
i: The index of the item it belongs to.numberRequired
text: The label as shown.stringRequired
short: The short form of the label, for the small sizes.stringRequired
tone: The tone of the mark (a colour token)."success" | "warning" | "neutral" | "primary"Required

The data as a JSON Schema: schemas/incident-tape.json

Incident tape chart: a React and Figma chart in four sizes

What does an incident tape chart show?

An incident tape chart lays the steps of an incident along the measure that triggered it: rising, over the limit, alert, paged, acknowledged, fix proposed. Gaps between steps show where time was lost. Use it for incident reviews and on-call reports.

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 Incident tape component?

It is one <IncidentTape> component. Its props are the Figma properties with the same names and values, and the props table above lists them. The data is a measure over time and dated steps.

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 it one incident? Yes means the incident tape fits.
  • Do the steps matter? Yes means the incident tape fits.
  • Is it minutes, not days? Yes means the incident tape fits.

When does another type fit better?

  • Many incidents over a month. Use Burn-down instead.
  • Only the measure against target. Use Target trend instead.
  • A schedule over days. Use Gantt instead.

Incident tape questions

Installing, data, Figma and plans.

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

Stay in the loop

New charts, by email.

Get an email when new chart types and releases ship.

Unsubscribe any time.