Service Levels: Dashboard

Updated

Service Levels: Dashboard

Overview

Use this page to review Service Level Objective (SLO) readiness and jump into the setup steps that remain. An SLO is a measurable target, such as uptime or response time, that a service is expected to meet over time. Operators use this dashboard to see, in one place, whether services are being tracked, whether objectives exist for them, whether those objectives are actually mapped to a service, and whether a database is connected to store the historical snapshots SLO calculations depend on.

This dashboard sits downstream of the Service Levels configuration pages. Services and objectives must already exist, created in Configuration: Service Levels: Services and Configuration: Service Levels: Objectives, before they appear here. Mapping a service to an objective in Configuration: Service Levels: Mappings, and connecting a SQL Server or PostgreSQL datasource in Configuration: Service Levels: Storage, are what move the KPI cards here from open to resolved. Once coverage and mapping are complete, pages such as Service Levels: Health and Service Levels: Violations consume that mapped data to report ongoing SLO performance.

On this page itself, you can read KPI cards for service count, objective count, storage status, and overall readiness, check the Service coverage table for which services still need an objective, work through the Setup checklist's open items, and see the Source mix of monitoring data currently feeding your objectives. From here you can also open the Manage, Set up new SLO, and Mappings controls to act directly on any gap you find.

Key concepts

  • Service Level Objective (SLO) - A measurable target, such as uptime or response time, that a service is expected to meet over a tracked period. (related: Configuration: Service Levels: Objectives)
  • Mapping - The link between a service and the objective or objectives that apply to it; a service shows as Unmapped until at least one mapping exists. (related: Configuration: Service Levels: Mappings)
  • Snapshot store - The SQL Server or PostgreSQL database connected to Service Levels that stores historical SLO calculation snapshots over time. (related: Configuration: Service Levels: Storage)
  • Service coverage - The proportion of your services that have at least one objective mapped to them, shown as a ratio on this dashboard.
  • Source mix - A breakdown of which monitoring data sources, such as Uptime, are currently available to supply data for your objectives. (related: Uptime Monitoring: Checks)

When to use it

  • When you want a single overview of whether Service Levels setup is complete or still needs work.
  • When you need to confirm how many services have mapped objectives before relying on Service Levels: Health or Service Levels: Violations data.
  • When onboarding Service Levels for the first time and need to see which configuration steps remain.
  • When checking whether a snapshot datasource is connected before historical SLO trend data can be retained.
  • When a new service was added elsewhere and you want to confirm it now has coverage.

Before you begin

  • At least one service must exist for it to appear in the Service coverage table; add services in Configuration: Service Levels: Services.
  • At least one objective must be defined before it can be mapped; create objectives in Configuration: Service Levels: Objectives.
  • To clear a service's Unmapped or Needs mapping status, map it to an objective in Configuration: Service Levels: Mappings.
  • To record historical SLO snapshots, connect a SQL Server or PostgreSQL datasource in Configuration: Service Levels: Storage.

Common workflows

Review readiness and resolve an open setup item

Persona: Load-test admin configuring Service Levels for the first time

  1. Open the Service Levels: Dashboard page.
    • Expect: KPI cards show the current SERVICES, OBJECTIVES, STORAGE, and READINESS counts, and the Setup checklist lists any open items.
  2. Read the READINESS card and Setup checklist to identify the next open item.
    • Expect: You see which step is blocking readiness, for example selecting a datasource or mapping a service.
  3. Select the relevant checklist item, such as Map every service to one or more objectives.
    • Expect: You're taken to the Service Levels mappings page to complete that step.
  4. Return to the dashboard and select Refresh.
    • Expect: The SERVICE COVERAGE, MAPPED OBJECTIVES, and READINESS cards update to reflect the change.

Verify: The Setup checklist's open-item count decreases, and the resolved row's STATE in the Service coverage table changes from Needs mapping to a mapped state.

Steps

Step 1

Open the Service Levels: Dashboard page.

Expected result: The KPI cards load showing SERVICES (1), OBJECTIVES (2), STORAGE (Not selected), READINESS (Needs setup, 2 open items), SERVICE COVERAGE (0 / 1), MAPPED OBJECTIVES (0 / 2), and SNAPSHOT STORE (Not selected). The Service coverage table lists Digital Workspace as Unmapped / Needs mapping, the Setup checklist shows 2 open items, and Source mix shows Uptime at 2.

This gives you the current readiness snapshot before you act on any checklist item.

  • READINESS reads Needs setup with 2 open items.
  • Service coverage table lists Digital Workspace as Unmapped / Needs mapping.
  • Setup checklist shows 2 open items: select a datasource and map services. Service Levels: Dashboard - step 1

Step 2

Select Refresh in the page header.

Expected result: The dashboard reloads with the same KPI and table values, and the Manage and Set up new SLO header buttons become visible, along with the Readiness card's chevron link.

Refreshing confirms you're looking at live readiness data and reveals the header actions you need to act on the open items.

  • Manage button (gear icon) is now visible in the header.
  • Set up new SLO button (primary, plus icon) is now visible in the header.
  • Readiness card's chevron link is visible, linking to the open-items detail. Service Levels: Dashboard - step 2

Column reference

Column What it shows How to read it
SERVICES Shows how many services are currently defined for Service Levels tracking. A count of 0 means no services have been added yet in Configuration: Service Levels: Services; the figure updates on refresh.
OBJECTIVES Shows the total number of SLO targets defined, whether or not they are mapped to a service yet. Reflects everything created in Configuration: Service Levels: Objectives, independent of mapping status.
STORAGE Shows whether a datasource is connected to receive SLO snapshot writes. Not selected blocks historical trend data from being stored anywhere. Not selected means no datasource is attached; use the Add a ServiceLevels datasource link to connect one.
READINESS Rolls up overall Service Levels setup status with a count of outstanding open items. An amber dot next to Needs setup with a nonzero open-items count means configuration steps remain; select the card's chevron to see which ones.
SERVICE COVERAGE Shows the ratio of services that have at least one mapped objective out of all services. A low ratio means services are being tracked but not yet protected by any SLO. The bar fills as more services gain at least one mapped objective; 0 / 1 means the one known service has none mapped yet.
MAPPED OBJECTIVES Shows the ratio of objectives that are mapped to at least one service out of all objectives defined. Distinguishes objectives that exist in configuration from ones actually in effect. 0 / 2 means both defined objectives still need to be mapped to a service before they take effect.
SNAPSHOT STORE Shows which database engine stores SLO history snapshots, SQL Server or PostgreSQL. Not selected means no historical snapshots are being recorded. Matches the STORAGE card; both read Not selected until you connect a datasource.
SERVICE (Service coverage table) Identifies the monitored service along with its environment and timezone context. The parenthetical shows which environment and timezone the service's objectives are evaluated against.
OBJECTIVES (Service coverage table) Shows whether this specific service has an objective mapped to it. Unmapped means no objective is attached to this service yet; map one in Configuration: Service Levels: Mappings to clear it.
SOURCES (Service coverage table) Lists which monitoring sources feed data for this service's objectives. A dash means no source is linked yet, consistent with an Unmapped objective status on the same row.
STATE (Service coverage table) Shows the overall per-service setup state. Needs mapping indicates the service is visible to Service Levels but has no objective applied; it is the row-level counterpart to the dashboard's READINESS card.
Uptime (Source mix) Shows how many of the current data sources feeding Service Levels objectives come from Uptime Monitoring checks. A nonzero count means sources are available to supply objective data; it does not by itself mean an objective is mapped to a service.

Controls reference

Refresh

Reloads the dashboard's KPI cards, Service coverage table, Setup checklist, and Source mix panel with current data.

When to use: After you've changed services, objectives, mappings, or storage configuration elsewhere and want this dashboard to reflect it.

Side effects: Read-only: re-fetches and re-renders data, does not change any configuration.

Manage

Navigates to the Service Levels services management page.

When to use: When you need to add, edit, or remove a service that should be tracked.

Side effects: Navigation only; no data changes happen on this page.

Set up new SLO

Opens the guided SLO setup flow for defining a new objective.

When to use: When the READINESS card or Setup checklist indicates an objective still needs to be created and mapped.

Side effects: Navigation only from this page; the destination flow creates and maps objectives.

Mappings

Navigates to the Service Levels mappings page where services are linked to objectives.

When to use: When the Service coverage table shows a service as Unmapped or Needs mapping.

Side effects: Navigation only; mapping changes are made on the destination page.

Opens the detail behind the current readiness status and its open items.

When to use: When you want to see exactly which setup steps are still outstanding before acting on them.

Side effects: Navigation only.

Setup checklist items (Select a ServiceLevels datasource, Map every service to one or more objectives)

Each item links directly to the configuration page needed to resolve that specific open item.

When to use: Use these as a guided to-do list whenever the checklist shows open items.

Side effects: Navigation only; resolving the underlying task happens on the destination page.

Navigates to the Service Levels storage configuration page.

When to use: When STORAGE or SNAPSHOT STORE read Not selected and you need to connect a SQL Server or PostgreSQL datasource.

Side effects: Navigation only.

Start setup / Or configure manually

Start setup launches the guided SLO setup wizard from a zero-services state; Or configure manually goes straight to the services management page instead.

When to use: Shown only when no services have been added yet; use Start setup for a guided flow, or Or configure manually if you prefer to add services yourself first.

Side effects: Navigation only.

Verify the result

You've confirmed current SLO readiness: the KPI cards show 1 service and 2 objectives, with SERVICE COVERAGE at 0 / 1 and MAPPED OBJECTIVES at 0 / 2, and the READINESS card still reads Needs setup with 2 open items. Once setup is complete, SERVICE COVERAGE and MAPPED OBJECTIVES reach their full ratio, STORAGE and SNAPSHOT STORE show a connected datasource instead of Not selected, and READINESS shows 0 open items. If the counts don't change after you believe setup is done, select Refresh first; if they still don't match, check Configuration: Service Levels: Mappings and Configuration: Service Levels: Storage for unsaved changes.

Troubleshooting

  • Symptom: STORAGE and SNAPSHOT STORE both read Not selected. Fix: Select the Add a ServiceLevels datasource link and connect a SQL Server or PostgreSQL datasource in Configuration: Service Levels: Storage.
  • Symptom: SERVICE COVERAGE stays at 0 / 1 even after you believe mapping is done. Fix: Confirm the mapping was saved in Configuration: Service Levels: Mappings, then select Refresh on this dashboard to recalculate the ratio.
  • Symptom: A new service such as svc.lg.fulmar doesn't appear in the Service coverage table after you add it. Fix: Select Refresh; if it's still missing, verify the service was saved in Configuration: Service Levels: Services.
  • Symptom: READINESS still reads Needs setup with open items after you've worked through the checklist. Fix: Select each checklist item's chevron to confirm the underlying step, datasource selection or service-to-objective mapping, was actually saved.
  • Symptom: MAPPED OBJECTIVES shows fewer than the total OBJECTIVES count. Fix: Go to Configuration: Service Levels: Mappings and map any unmapped objective to at least one service.
Was this article helpful?
0 out of 0 found this helpful