Skip to main content
Version: 1.4 (Current)

Overview

The KPI Dashboard gives you a single place to monitor service uptime KPIs: summary counts, grouped cards or tables, and quick access to alerts that affect each KPI. KPI definitions themselves are managed under Service KPIs; the dashboard focuses on current status and target compliance.

StepWhat you doMenu / routeDocumentation
1Define KPIs — service, filters, targets, groupsMetrics & KPIs → Service KPIs → /service-kpiService KPIs
2Monitor status — summary cards, search, filters, cards or tableMetrics & KPIs → KPIs → /kpi-dashboardKPI dashboard
3Investigate alerts — alerts that match a KPI’s filtersView Alerts on a KPI card → /kpi-alertsViewing KPI alerts

KPI dashboard — cards view with summary and filters

Where to find it in the UI​

In the sidebar under Metrics & KPIs:

  • KPIs — /kpi-dashboard (page title: KPI Dashboard)
  • Service KPIs — /service-kpi (create, edit, and calculate KPI definitions)

The dashboard toolbar includes Search KPIs by name, service, or group, filters for service, group, and status, a cards / table view toggle, and Refresh.

Permissions

Viewing the dashboard (painted uptime) requires read:kpis (or higher KPI permissions). On-demand calculate is a separate run:kpis permission; the dashboard does not require it. Allowed KPI Groups on the role decides which KPIs appear: All (Full Access) shows every KPI; named groups show those groups plus KPIs with no group; empty shows only KPIs with no group. admin and admin:kpis see every KPI. Create KPI on an empty dashboard requires write:kpis. See Creating and managing roles and Permissions reference — Services and KPIs.

How the parts fit together​

Typical workflow:

  1. An administrator defines Service KPIs for production services — each KPI specifies alert filters (severity, status, environment, resource), a target uptime, date range preset, and optional KPI groups for dashboard organization.
  2. Operators open KPIs (/kpi-dashboard) to see which KPIs meet target or are below target, filtered by service or group.
  3. When a KPI shows alert counts, View Alerts opens the alert list for that KPI’s filter set (requires service history capability in your license — see Viewing KPI alerts).

KPI groups on the dashboard mirror group tags assigned when KPIs are created or edited in Service KPIs. KPIs without a group appear under Ungrouped.

Availability limits​

CapabilityWhen limited
View AlertsButton is disabled with a premium indicator when your license does not include service history. You can still see alert counts on the dashboard.
KPI visibilityRole Allowed KPI Groups empty — only KPIs with no group appear. Named groups add those groups. All (Full Access) (or admin / admin:kpis) shows every KPI
ModuleRelationship
Service KPIsCreate and edit KPI definitions; Create KPI on the dashboard navigates here
MetricsAggregate open-alert and history analytics — complementary to per-KPI uptime
Alerts dashboardLive alerts; View Alerts opens a KPI-filtered subset
Service TopologyOptional Service KPI link per topology for aligned uptime views
Services catalogKPIs reference services from the shared catalog
Roles — Allowed KPI GroupsRestricts grouped KPIs; empty still shows KPIs with no group

Best practices​

  1. Assign KPI groups when creating KPIs so the dashboard stays organized by team, environment, or application.
  2. Use summary cards (Total KPIs, Meeting Target, Below Target) as quick filters before narrowing with service or group dropdowns.
  3. Switch to table view when comparing many KPIs across groups; use cards view for at-a-glance uptime and thresholds.
  4. Refresh after bulk alert changes or KPI edits so uptime percentages reflect the latest data.
  5. Pair dashboard monitoring with Service KPIs — edit targets, filters, or thresholds in Service KPIs, then return to the dashboard to verify impact.
  6. Review role KPI groups whenever you grant read:kpis — empty Allowed KPI Groups still shows KPIs with no group.