Charts

Tracker

Uptime / status grid — each block represents a time unit coloured by status.

Quick Preview

API Service81.1% uptime

Operational

Outage

Degraded

Maintenance

Installation

# No extra dependencies

// Copy component from
src/components/charts/Tracker.tsx

Usage

import Tracker from '@/components/charts/Tracker'

const data = days.map((d) => ({
  status: 'up' as const, // 'up' | 'degraded' | 'down'
  date: d,
}))

<Tracker data={data} label="API Service" showLegend />

Examples

Database — 90 Day Uptime

Database Cluster70% uptime

Multi-Service Status (30 Days)

Web App90% uptime

CDN83.3% uptime

Auth Service73.3% uptime

Prompt Preview

Copy a prompt that recreates this UI

Paste this into your AI coding assistant to generate code that closely matches the reference, including color, size, shape, typography, spacing, and polish.

Copy-ready AI prompt

Starts from the current visual reference and project constraints.

Build a charts component named Tracker in React/Next.js.
Goal: recreate the same overall UI and behavior as the Tracker reference from a component gallery.
What it needs to communicate: Uptime / status grid — each block represents a time unit coloured by status..

Project constraints:
- Use Next.js 16.2.6 with the App Router, React 19, TypeScript strict mode, and Tailwind CSS v4.
- Do not create a tailwind.config.js file. Use Tailwind v4 utilities and CSS variables where design tokens are needed.
- If you are implementing this inside the same project, use the Prompt font via next/font/google. If not, use the closest equivalent typeface.
- Return production-ready code with imports, responsive behavior, keyboard accessibility, and polished empty, hover, focus, active, and disabled states where relevant.
- Match the reference closely: color palette, spacing scale, border radius, shadows, icon scale, typography hierarchy, and motion timing.

Component-specific expectations:
- Use SVG or lightweight primitives unless a charting library is truly necessary.
- Keep axes, labels, legends, and thresholds visually clear and consistent.
- Avoid unnecessary dependencies unless the behavior truly requires them.
- No explicit color literals were found in the examples. Match the live reference and the project accent color when appropriate.

Props to support:
- data: TrackerItem[] — required — Array of {status, tooltip?, date?}
- label: string — Service label shown above tracker
- showLegend: boolean — default true — Show status legend

Reference usage patterns:
- No examples were documented. Infer a sensible default presentation and one richer usage example.

Feature expectations:
- 4 status states
- Tooltip per block
- Uptime % calculation
- Legend toggle

Output requirements:
- Return complete code, not pseudocode.
- Include all necessary imports and helper types.
- Keep the implementation accessible, responsive, and visually finished.
- Match the reference for color, size, shape, typography, spacing, and interaction states as closely as possible.
- If multiple files are needed, organize them cleanly and explain the file structure briefly.

Tweak only product-specific copy or data after the first generation pass.

Props

Prop	Type	Default	Description
`data`*	`TrackerItem[]`	-	Array of {status, tooltip?, date?}
`label`	`string`	-	Service label shown above tracker
`showLegend`	`boolean`	`true`	Show status legend