SLO Dashboard

Track SLO compliance, error budgets, burn rate, service reliability, and policy breaches across critical services. This example brings Overview and Services together so engineering teams can find the next task without losing context.

It includes representative records such as identity-api · 99.95% and billing-api · 99.9%. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

SLO Dashboard
Use this template in Figr

Template facts

Screen

Analytics

Primary action

Add SLO

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Engineering and security teams need to add slo while keeping slos met, budget remaining and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Overview gives users an obvious place to start.
  • Supporting view: Services keeps the related context close.
  • Primary action: Add SLO stays visible when people need it.
  • First signal: SLOs met shows a useful value (93%).
  • Second signal: Budget remaining gives additional context (68%).
  • Sample record: identity-api · 99.95%.
  • Next record: billing-api · 99.9%.

States worth designing

  • No results for the selected range: say what changed, protect progress, and offer a clear next step.
  • Refreshing with old values visible: say what changed, protect progress, and offer a clear next step.
  • Metric source unavailable: say what changed, protect progress, and offer a clear next step.
  • Filter changed the interpretation: say what changed, protect progress, and offer a clear next step.
  • Export preparing: say what changed, protect progress, and offer a clear next step.
  • Restricted data hidden: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Overview → Services → Add SLO → Review outcome

Patterns used

Analytics, Overview, Services, contextual actions, error recovery

Why these choices work

Keep the time range and metric definition visible. Let people see which segment or filter produced the result, then explain missing or delayed data.

Pay attention to overview and services. People need to distinguish identity-api · 99.95% from billing-api · 99.9%. Keep slos met visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Add SLO”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Environment Configuration, Certificate Management, Job Scheduler.

Start from this in Figr

Design a slo dashboard screen inside our existing product. Use our current components, tokens and content language. Include Overview and Services views, credible records like identity-api · 99.95%, and a clear “Add SLO” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr