Alerting Center

Review metric anomalies, threshold breaches, owners, and notification status without burying signal in a wall of alerts. The screen connects Alerts and Rules so product analysts can find the “New alert” action while checking open alerts and critical.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Activation dropped 11% and API latency above threshold, rather than an empty visual shell.

Alerting Center
Use this template in Figr

Template facts

Screen

Inbox

Primary action

New alert

Pattern

Inbox

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Product analysts need a clear “New alert” action without losing sight of open alerts, critical and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: New alert is clearly available where the task happens.
  • Main view: Alerts keeps the starting point obvious.
  • Connected view: Rules supplies nearby context.
  • Metric: Open alerts is visible with a meaningful value.
  • Another signal: Critical helps people judge what to do next.
  • Representative record: Activation dropped 11% makes the example specific.
  • Second record: API latency above threshold shows the pattern works beyond one item.

States worth designing

  • Inbox empty after filters; show what people can do instead of leaving a blank panel.
  • Loading alerts without changing the layout unexpectedly.
  • Attachment or reply failed; explain the problem and preserve work.
  • Permission denied for rules; clarify who can continue.
  • Success after choosing New alert; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Alerts → Rules → New alert → Review outcome

Patterns used

Inbox, Alerts, Rules, Incidents, accessible states, contextual actions

Why these choices work

Keep the active record close to its history, owner and status. Make urgent items easy to find without hiding the rest.

In this design, people should be able to compare Activation dropped 11% with API latency above threshold. Make open alerts clear, then use critical to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “New alert” action. The happy path alone is not enough.

Related UI examples: Metrics Catalog, Executive BI, Data Explorer.

Start from this in Figr

Design a alerting center screen for our existing software product. Use our real design-system tokens, components and product language. Show Alerts and Rules, include believable records such as Activation dropped 11%, and make new alert easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr