Service Levels: Health
Overview
Use this page to check service objective compliance and review the latest active snapshots. Service Levels: Health is the operational read-out for your SLOs (service level objectives): for a chosen service and time window, it reports whether each objective is currently being met and surfaces the most recent recorded evaluations, called snapshots. Without this page you would have no single place to confirm, at a glance, whether a production service is meeting the targets you have defined for it.
Health depends on work done elsewhere: a service and its objectives must already exist in Configuration: Service Levels: Services and Configuration: Service Levels: Objectives, and a SQL Server or PostgreSQL ServiceLevels datasource must be selected in Configuration: Service Levels: Storage so evaluation snapshots have somewhere to be recorded. Once objectives are evaluated, either on a schedule or manually from this page, the resulting compliance status feeds Service Levels: Dashboard and Service Levels: Violations, where breaches are investigated further.
Key concepts
- Service - A logical application or system whose service level objectives are tracked together, defined elsewhere in the platform. (related: Configuration: Service Levels: Services)
- Window - The number of days of history the page evaluates when computing compliance for the selected service.
- Snapshot storage - The SQL Server or PostgreSQL ServiceLevels datasource where evaluation results are recorded; health data cannot be queried until one is selected. (related: Configuration: Service Levels: Storage)
- Objective health - The per-objective compliance status for the selected service, computed from stored snapshots within the chosen Window. (related: Configuration: Service Levels: Objectives)
- Snapshot - A recorded evaluation of a service's objectives at a point in time, produced by the schedule or by Evaluate now. (related: Service Levels: Dashboard)
When to use it
- To check whether a specific service is currently meeting its service level objectives.
- To review the most recent snapshot evaluations while investigating a reported incident.
- When the page reports that snapshot storage is not selected, to jump straight to storage setup.
- To widen or narrow the Window and see whether a compliance issue is a recent blip or a longer-term trend.
Before you begin
- The service you want to check has been created in Configuration: Service Levels: Services.
- The service has at least one objective configured in Configuration: Service Levels: Objectives.
- A SQL Server or PostgreSQL ServiceLevels datasource has been selected and provisioned in Configuration: Service Levels: Storage.
- At least one evaluation (scheduled or manual) has run so a snapshot exists to display.
Common workflows
Set up snapshot storage to unblock health reporting
Persona: Service Levels admin
- Confirm the Service you intend to monitor is selected.
- Expect: The empty-state message persists because no snapshot storage has been selected yet, regardless of which service is chosen.
- Select Open storage.
- Expect: You're taken to Configuration: Service Levels: Storage to select or provision a SQL Server or PostgreSQL ServiceLevels datasource.
- Return to Service Levels: Health after storage is provisioned and select Evaluate now.
- Expect: An on-demand evaluation runs and records a new snapshot; Objective health and Latest active snapshots populate with compliance data.
Verify: The Snapshot storage is not selected message is gone, and the page shows objective health rows with a status alongside the latest active snapshots for the selected service.
Review per-objective compliance for a service
Persona: load-test operator
- Select the target service from Service (for example, svc.lg.fulmar).
- Expect: The page loads that service's objective health and latest active snapshots once storage is configured.
- Adjust Window to the number of days you want to evaluate.
- Expect: Objective health recalculates over the new period; widening Window from 30 to a larger value surfaces longer-term trend instead of just recent days.
- Select Refresh.
- Expect: The displayed compliance status and snapshot list reload for the chosen Service and Window.
Verify: Objective health lists each objective's current compliance status for the selected service, and Latest active snapshots shows the most recent recorded evaluations within the chosen window.
Steps
Step 1
Open the Service Levels: Health page.
Expected result: The page loads with Service and Window set to their last-used values, but because no ServiceLevels snapshot datasource is selected, the panel shows Snapshot storage is not selected instead of objective health data.
This confirms whether health reporting is unblocked before you try to evaluate compliance.
- Service shows the last-selected service, for example Digital Workspace (Prod).
- Window defaults to 30 days.
-
Open storage routes to storage setup when data can't be queried.
Step 2
Select Refresh.
Expected result: The page re-queries compliance data for the current Service and Window selection; the Credentials expiring banner is no longer shown, and the panel still displays Snapshot storage is not selected because no datasource has been chosen yet.
Refreshing confirms whether storage has been configured without leaving the page.
- Refresh re-runs the query using the current Service and Window values.
- The empty-state message and Open storage persist until a datasource is selected.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Service | Selects which configured service's compliance and snapshots are displayed. Switching services replaces all displayed objective health and snapshot data with that service's results. | dropdown of configured services | No | - |
| Window | Sets how many days of history are evaluated. A smaller Window makes compliance more sensitive to recent breaches; a larger Window smooths out short blips and shows the longer-term trend. | integer, days | No | 30 |
Controls reference
Refresh
Re-queries compliance data for the currently selected Service and Window without changing any filter values.
When to use: After changing Service or Window, or when checking whether a scheduled evaluation has completed.
Side effects: Read-only; reloads the displayed data but does not change any configuration or create a new snapshot.
Evaluate now
When to use: When you need up-to-date health status right away, for example right after resolving an incident.
Side effects: Mutating; runs an evaluation and records a new snapshot once snapshot storage is configured.
Open storage
Navigates to Configuration: Service Levels: Storage to select or provision the SQL Server or PostgreSQL datasource.
When to use: When the page shows that snapshot storage is not selected and health data cannot be queried.
Side effects: Navigation only; no data on this page is changed.
Dismiss (X)
Closes the Credentials expiring warning banner.
When to use: Once you've noted the expiring credential or already reissued it.
Side effects: UI-only; hides the banner for the session but does not renew or change the underlying credential.
Verify the result
When the primary task succeeds, selecting a Service and clicking Refresh or Evaluate now populates an Objective health list showing each objective's current compliance status for the chosen Window, and a Latest active snapshots list showing the most recent evaluation results. If you instead still see Snapshot storage is not selected, no ServiceLevels datasource has been selected under Configuration: Service Levels: Storage, so health data cannot be computed. Check that the Service and Window values shown in the filter row match the service and period you intended before concluding compliance is good or bad.
Troubleshooting
- Symptom: The panel always shows Snapshot storage is not selected even after clicking Refresh or Evaluate now. Fix: Select Open storage and provision a SQL Server or PostgreSQL ServiceLevels datasource under Configuration: Service Levels: Storage; health data can't be queried until one is selected.
- Symptom: Evaluate now runs but the Objective health list stays empty. Fix: Confirm the selected service has at least one objective configured in Configuration: Service Levels: Objectives; an evaluation has nothing to compute without objectives.
- Symptom: The Credentials expiring banner reappears after you dismiss it. Fix: Reissue the expiring credential under Configuration: Credential Profiles; the banner keeps surfacing each session until the token is renewed.
- Symptom: Compliance looks worse or better than expected after changing Window. Fix: Remember a smaller Window only evaluates recent days, so a single recent breach dominates the result; widen it to see the longer-term trend before concluding there is a chronic issue.
Related articles
- Prerequisite: Configuration: Service Levels: Storage - snapshot storage must be selected before health data can be queried
- Prerequisite: Configuration: Service Levels: Services - the Service dropdown lists services defined here
- Prerequisite: Configuration: Service Levels: Objectives - objective health is computed from objectives configured here
- See also: Service Levels: Dashboard - aggregated service level status across all services
- Next step: Service Levels: Violations - investigate objectives that fail the compliance shown on this page
- See also: Configuration: Credential Profiles - reissue credentials flagged by the expiring-credentials banner