Skip to content

Alerting

Thresholds with how often each has actually fired, what that produced, where it went — and the digest settings that exist because of the answer.

5 blocks54 lineslucide-reactAdded 10 Sept 2026

What's included

  • app/alerting-page.tsx
  • 5 blocks it is built from, installed with it
  • Needs lucide-react

Works with

  • React
  • Next.js
  • Tailwind CSS
  • TypeScript

npx hoverlab add alerting-page

Or over MCP, from your editor's agent — no account needed.

License

Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.

Was this useful?

Preview

Alerting

The rules, how often they have fired, where that went — and the batching that exists because of the answer.

Alert rules

4 of 5 active · 1 delivering nowhere

  • critical

    API error rate

    Alert when API error rate stays above 2% for 5 minutes.

    #incidentsFired 3 times in the last 30 days
  • warning

    p95 latency

    Alert when p95 latency stays above 800ms for 15 minutes.

    #platform-alertsFired 27 times in the last 30 days

    This rule is on, but #platform-alerts is muted — nothing has been delivered since it was muted.

  • warning

    Signups per hour

    Alert when Signups per hour stays below 4 for 1 hour.

    growth@acme.comFired 142 times in the last 30 days

    Firing 142 times a month is usually a threshold problem rather than an incident. Consider raising it before muting the channel.

  • critical

    Job queue depth

    Alert when Job queue depth stays above 5,000 for 10 minutes.

    pagerduty.com/…/v2Fired 1 times in the last 30 days
  • info

    Storage used

    Alert when Storage used stays above 85% for 1 day.

    ops@acme.comFired 0 times in the last 30 days

Alerts, and how close they are

An alert that has never fired looks identical to an alert that is broken. Showing the current distance to the threshold is what tells the two apart at a glance.

Where each thing goes

The all-or-nothing toggle is why people mute products. Routing by event lets the two that matter stay loud while the rest go somewhere quiet.

Yesterday, in one message

The alternative is fourteen separate emails, which is how a notification system trains people to filter it into a folder they never open.

Send it all at once instead

The alternative offered by most products is on or off, so everyone picks off. A time and a floor turns the same stream into one predictable message.

Your local time. Nothing arrives outside this except an outage.

Fewer events than this and no message is sent at all. An empty digest is still an interruption.

The real page, rendered in your current theme — every section below is a live block, not a screenshot.

Built from

All blocks
  1. Alert Rule ListThreshold alerts with the two facts most rule lists omit: how often each has fired, and whether its channel is muted — so a rule that is on but delivering nowhere reads as its own state.
  2. Metric Alert ListAlert thresholds with their current distance from firing, so a quiet alert is visibly armed rather than possibly broken.
  3. Notification Channel ListWhich channel carries which event, so the loud ones can be moved rather than muted entirely.
  4. Notification DigestA day's notifications collapsed into one digest, grouped by what they are rather than when they arrived.
  5. Digest Schedule FormThe control that turns notification volume down instead of off, which is the choice most people actually want.

Only want one section? Open it and copy that block instead — browse Dashboards.

Source

app/alerting-page.tsx
/**
 * Alerting, as the loop it actually is: a rule fires, something happens to
 * a person, and someone eventually decides it was firing too often.
 *
 * Most alert settings screens are a list of thresholds and a list of email
 * addresses, on separate tabs, with nothing joining them. The join is the
 * whole subject. A threshold nobody has tuned and a channel nobody reads
 * produce the same outcome — an incident nobody saw — and you cannot tell
 * which one you have unless the two are on the same screen.
 *
 *   rules        thresholds, with how often each has fired. That number is
 *                the one most rule lists omit and the only one that says
 *                whether the rule is any good
 *   fired        what those rules produced
 *   channels     where it went
 *   digest       what got batched instead of sent immediately
 *   schedule     and when the batch goes out
 *
 * The digest pair is at the end because batching is the answer to the
 * problem the first three sections describe, and an answer read before the
 * problem is just another setting. Someone arriving here because they are
 * being paged too much should scroll through the evidence for that on the
 * way to the control that fixes it.
 */

import * as React from 'react'
import { DashboardAlertRules } from '@/components/dashboard-alert-rules'
import { MetricAlertList } from '@/components/metric-alert-list'
import { NotificationChannelList } from '@/components/notification-channel-list'
import { NotificationDigestList } from '@/components/notification-digest-list'
import { DigestScheduleForm } from '@/components/digest-schedule-form'

export default function AlertingPage() {
  return (
    <main className="min-h-screen bg-background text-foreground">
      <section className="mx-auto w-full max-w-5xl px-6 pb-2 pt-12">
        <h1 className="text-2xl font-bold tracking-tight">Alerting</h1>
        <p className="mt-1 text-sm text-muted-foreground">
          The rules, how often they have fired, where that went — and the
          batching that exists because of the answer.
        </p>
      </section>

      <DashboardAlertRules />
      <MetricAlertList />
      <NotificationChannelList />

      {/* The fix for everything above it, so it comes after. */}
      <NotificationDigestList />
      <DigestScheduleForm />
    </main>
  )
}

How to use it

  1. 1. Copy each of the 5 blocks above into components/ — each block page has its own copy button.
  2. 2. Drop this file at app/alerting-page.tsx. The imports already point at @/components/…, so they resolve with no edits.
  3. 3. Delete the sections you do not want. Every block takes props, so the copy changes without the layout moving.

For AI

The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.

See the prompt

More App Screens

Open the full page for this page

Dashboard Overview

The screen an app opens on: shell, header, KPI row, chart and activity feed — numbers first, shape second, changes last.

App Screens5 blocks47 lines
Open the full page for this page

AI Assistant Screen

An agent working inside a real app: a transcript down the middle — reasoning, answer, then the one card that can act — with what it may read and what it noticed demoted to a rail.

App Screens7 blocks110 lines
Open the full page for this page

Project Board

A kanban board inside the app shell, with tabs that admit the board is one view among several and a header whose primary action is creating work.

App Screens3 blocks42 lines
Open the full page for this page

Customer List Screen

The canonical CRUD list — header, toolbar, sortable table and pagination framed as one panel instead of three stacked cards.

App Screens5 blocks37 lines
Open the full page for this page

Onboarding

A wizard for the session someone finishes and a checklist for the one they do not, with the only genuinely blocking step in front of both.

App Screens3 blocks45 lines
Open the full page for this page

Search Results

Built around the state a search page is in most of the time — empty — so recent queries lead and the facets sit in a sidebar that survives growing to twelve.

App Screens4 blocks47 lines
Open the full page for this page

Agent Run Detail

One run opened up in the order you would debug it — intent, actions, the retries that are invisible in both, then cost.

App Screens4 blocks49 lines
Open the full page for this page

Approvals Inbox

The queue, the same queue sorted by how long things have waited, and the policy that decided both — with the policy last so it is not scrolled past forever.

App Screens3 blocks45 lines
Open the full page for this page

Assistant Chat

The blank thread answered with real starter prompts, the model picker with the three numbers the choice turns on, and the four surfaces a session grows into — attachments, branches, canvas, threads.

App Screens6 blocks68 lines
Open the full page for this page

Agent Run Inspector

The three states an agent screen usually omits: the wait before the first token, the trace after something broke with retries costed in the open, and the diff it wants a person to accept.

App Screens5 blocks61 lines
Open the full page for this page

Retrieval Console

Why the answer said what it said: what is connected, how stale it is, what the query was allowed to see, what fitted in the window and what fell out — plus the failed-search state a debugging tool is most needed in.

App Screens7 blocks66 lines
Open the full page for this page

AI Editor

Five ways to reach a model without the cursor leaving the sentence — slash menu, inline completion, selection toolbar, action menu, property inspector — and the two surfaces that say where the answer came from.

App Screens7 blocks64 lines
Open the full page for this page

Records Table

A table after real people have used it — columns reordered from the keyboard, a selection bar that asks page-or-all, subtotals that survive collapsing, cells edited in place, and the empty state its own filters produced.

App Screens8 blocks71 lines
Open the full page for this page

Analytics

The saved view and the comparison window first, because every figure below depends on both — then six charts, none of which load a charting library.

App Screens8 blocks68 lines
Open the full page for this page

Import Data

The flow between an empty product and a useful one, in the order it goes wrong: sample data offered with equal weight, a file, a URL, the column mapping everything stalls on, and an upload that survives the connection dropping.

App Screens7 blocks64 lines
Open the full page for this page

Account Setup

A profile form where the role options state what they actually change, the avatar crop works from the keyboard, and a navigation guard names the fields it is about to throw away.

App Screens4 blocks53 lines
Open the full page for this page

App Shell

The furniture that is on every screen and belongs to none — navbar, mobile drawer, command palette, shortcut sheet, header search, scope switcher, and the two shapes a detail view takes without losing the list.

App Screens8 blocks68 lines
Open the full page for this page

Workspace Activity

Backwards from now and forwards from it on one screen — a day-grouped timeline, a month grid where a busy Tuesday never changes the row height, and the state both are in on day one.

App Screens3 blocks51 lines
Open the full page for this page

First Run

What the product looks like while onboarding happens: a tour step anchored to the control it explains, the skeletons of the slowest load it will ever do, and the checklist that outlives both.

App Screens3 blocks50 lines