Skip to content

Event barcode

Every event as a thin line, by service.

Definition · Updated Nov 2, 2026

An event barcode draws every event as a thin line on a time axis, one row per service, coloured by outcome. Bursts, gaps and error streaks show as patterns. Use it for API requests, logins or deploys over a day.

Pay once. Every update included.

Live preview

Request outcomes350 sampled requests over the last 24 hours on 3 services; Agents has the highest error rate at 6%.Chat APIEmbeddingsAgents00:0012:00NOWOKSLOWERROR
Request outcomes
ServiceSampled requestsError rateSlow rate
Chat API1502%6%
Embeddings1100.5%2%
Agents906%12%

Sample data: requests to chat API, embeddings and agents over 24 hours, OK, slow and error

Size
Legend
Data shape
Per row: a count, error and slow shares, and an hourly pattern
Good for
API requests, logins, deploys
Avoid when
Counts per period are enough
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

061 / Event barcode

chart/061-barcode-requests
plot · event barcode
Layer
event
Type
Rectangle
Size
1 × 61
Fill
status/danger
Group
Marks · 37

Layers

061 / Event barcode

chart/061-barcode-requests
plot · event barcode
Layer
event
Type
Rectangle
Size
1 × 24
Fill
status/danger
Group
Marks · 37

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

Labels88

Marks3737

Height212 px246 px

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

When to use

Every event, in time.

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

Is every event shown?

Counts per hour.

Yes: Keep the event barcode

Is the outcome a status?

Durations per run.

Yes: Keep the event barcode

Is it one day?

Uptime over weeks.

Yes: Keep the event barcode

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/061-barcode-requests

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/event-barcode
event-barcode.tsx
import { EventBarcode } from "@/components/chartory/event-barcode"import { serviceRequests } from "./service-requests"export function ServiceRequests() {  return (    <EventBarcode      data={serviceRequests}      size="m"      legend={true}    />  )}

Hearth widget

Event barcode as a widget.

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

Code
Get the code

EmberPreset

ChartoryDefault preset

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

Read the Hearth widget docs

FAQ

Event barcode questions.

What people ask before they put an event barcode in a dashboard.

Something else?

hello@usechartory.com
  • OK, slow and error, named in the legend.

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.