Burn-rate tracks
Burn rate in four windows, against the paging rules.
Definition · Updated Nov 2, 2026
Burn-rate tracks show how fast an error budget is being spent over several windows at once, with the alert rule marked on the windows that have one. A short window catches spikes, a long one catches slow leaks. Use it for SLO alerting and on-call reviews.
Pay once. Every update included.
Live preview
Sample data: burn rate 6.2× in the last hour against a page at 14.4×, 0.73× this month
- Data shape
- A burn rate and a rule per window
- Good for
- SLO alerting, error budgets
- Avoid when
- There is no error budget
- 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
114 / Burn-rate tracks
- Layer
- one x · line
- Type
- Vector
- Size
- 0 × 238
- Stroke
- text/strong
- Group
- Marks · 8
Layers
114 / Burn-rate tracks
- Layer
- one x · line
- Type
- Vector
- Size
- 0 × 154
- Stroke
- text/strong
- Group
- Marks · 8
Layers
114 / Burn-rate tracks
- Layer
- one x · line
- Type
- Vector
- Size
- 0 × 128
- Stroke
- text/strong
- Group
- Marks · 8
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
Labels1616
Marks88
Height212 px246 px
Same tokens at every size: text styles, 1 px lines and mark radius stay put.
When to use
Fast or slow burn?
Three signs it fits, and three signs another type fits better.
Are several windows compared?
One budget over the month.
Yes: Keep the burn-rate tracks
Does each window have a rule?
Plain rates side by side.
Yes: Keep the burn-rate tracks
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/114-burn-rate-tracks
npx shadcn add @chartory/burn-rate-tracksimport { BurnRateTracks } from "@/components/chartory/burn-rate-tracks"import { burnRates } from "./burn-rates"export function BurnRates() { return ( <BurnRateTracks data={burnRates} size="m" legend={true} /> )}Hearth widget
Burn-rate tracks as a widget.
The chart in a Hearth card with a hero number and two blocks. One token set, light and dark.
EmberPreset
ChartoryDefault preset
Pick the blocks, the size and the preset for your own widget.
Read the Hearth widget docsFAQ
Burn-rate questions.
What people ask before they put burn-rate tracks in a dashboard.
Something else?
hello@usechartory.comSpending the budget exactly on schedule. Under 1× lasts the period; over 1× runs out early. Each track marks the line between the two.
Rates run from 0.25× to 20×, so the scale spreads them out evenly by ratio. A page at 14.4× and a ticket at 3× both stay readable.
One data object in the sample’s shape: a burn rate and a rule per window. The docs page lists every field and links its JSON Schema; the sample data comes with the component, so you can start from it and swap in your own.
Series take the preset’s data colours in order, and states such as up, down or warning take its status colours. Change the preset in Figma or in code to recolour every chart at once.
XS, S, M and L, in light and dark. Each size is laid out again from the data, so text and lines keep their size.
Yes. It plays in when it scrolls into view, and when the data changes every mark moves from its old place to its new one. With reduced motion on, it does not move.
Yes. The Figma component comes with Figma and Complete, the React component with Code and Complete.
Ask for it by name. The MCP server tells the agent what data it needs and runs the same command: npx shadcn add @chartory/burn-rate-tracks. You review the diff.
Related types
Other ways to show compare items.
The same question, a different shape of answer. Every type ships in Figma and in code.
Same family
Compare items
Rank, gap and change between products, teams or regions.