Every event as a thin line, by service. Sample data: requests to chat API, embeddings and agents over 24 hours, OK, slow and error.
Installation
- 1
Set up the registry once
This chart is free in Hearth and MIT licensed: no token. Add @chartory to components.json once (the URL alone, no headers), or skip this when another chart is already installed.
Installation guide - 2
Add the chart
One command adds the Event barcode component to your project.
npx shadcn add @chartory/event-barcode - 3
Use it
Pass your rows. The props are the Figma properties.
usage.tsximport { EventBarcode } from "@/components/chartory/event-barcode"<EventBarcode data={serviceRequests} size="m" legend/>
Props
<EventBarcode>
Every prop but data is a Figma property with the same name and values.
EventBarcodeData
The data prop: one object for the whole chart.
EventBarcodeRow
One object per entry in rows.
The data as a JSON Schema: schemas/event-barcode.json
Event barcode: a React and Figma chart in four sizes
What does an event barcode show?
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.
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 Event barcode component?
It is one <EventBarcode> component. Its props are the Figma properties with the same names and values, and the props table above lists them. The data is a count, error and slow shares per row, plus an hourly pattern; the events are generated from them.
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 every event shown? Yes means the event barcode fits.
- Is the outcome a status? Yes means the event barcode fits.
- Is it one day? Yes means the event barcode fits.
When does another type fit better?
- Counts per hour. Use Bars instead.
- Durations per run. Use Latency field instead.
- Uptime over weeks. Use Uptime bars instead.
Event barcode questions
Installing, data, Figma and plans.
Yes. It installs through the shadcn registry with the shadcn CLI, and the file lands in your project.
It is free in Hearth and MIT licensed: add the @chartory registry URL once, no token, then run npx shadcn add @chartory/event-barcode. The Installation guide has the steps.
Yes. Connect the Chartory MCP server and ask for the event barcode chart; the agent runs the same command and you review the diff.
A count, error and slow shares per row, plus an hourly pattern; the events are generated from them. The sample data comes with the component, and the props table lists every field.
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.
Yes. chart/061-barcode-requests has the same properties as the component.
Yes. Every paint is a token, so the chart follows light and dark mode and the collection you pick.
None for Hearth: it is free in the public registry, no token. The Signal collection (@chartory/signal) comes with Code and Complete.