Service Levels: Health
Overview
Use this page to review per-service SLA compliance and recent health snapshots. Service Levels: Health reports whether a monitored service is currently meeting the objectives defined for it, based on periodic health snapshots recorded for that service, so you can confirm SLA status without digging through raw test or monitoring data.
This page sits downstream of the rest of the Service Levels setup: a service must already exist in Configuration: Service Levels: Services, objectives must be attached to it in Configuration: Service Levels: Objectives, and a snapshot storage datasource must be provisioned in Configuration: Service Levels: Storage before any compliance data can be queried here. What you see on this page feeds the broader Service Levels: Dashboard and helps you decide whether to investigate further in Service Levels: Violations.
Key concepts
- Service - A monitored system or workload tracked under Service Levels, such as a production environment, whose SLA compliance this page reports on. (related: Configuration: Service Levels: Services)
- Objective - A measurable SLA target, for example an uptime or performance threshold, attached to a service. The Objective health section reports whether each one is currently being met. (related: Configuration: Service Levels: Objectives)
- Snapshot storage - The SQL Server or PostgreSQL datasource where periodic health snapshots are recorded. Health data cannot be queried on this page until one is selected and provisioned. (related: Configuration: Service Levels: Storage)
- Window - The lookback period used when evaluating objectives and listing recent snapshots for the selected service.
- Health snapshot - A recorded evaluation result that captures a service's objective compliance status at a point in time. The most recent ones appear under Latest active snapshots.
When to use it
- Check whether a specific service is currently meeting its SLA objectives.
- Review the most recent health snapshots for a service before escalating or closing an incident.
- Confirm that snapshot storage has been provisioned before relying on Service Levels reporting elsewhere.
- Narrow a compliance review to a particular service and time window rather than scanning the full dashboard.
Before you begin
- The service you want to review must exist in Configuration: Service Levels: Services.
- At least one objective must be attached to that service in Configuration: Service Levels: Objectives, otherwise there is nothing for Objective health to evaluate.
- A SQL Server or PostgreSQL ServiceLevels datasource must be selected and provisioned in Configuration: Service Levels: Storage; until then this page cannot query health data.
- You need access to the Service Levels module (shown here under a GlobalAdmin account).
Common workflows
Resolve the missing snapshot storage warning
Persona: Platform admin
- Read the Snapshot storage is not selected message on the Health page.
- Expect: The message explains that a SQL Server or PostgreSQL ServiceLevels datasource must be selected and provisioned before health data can be queried.
- Select Open storage.
- Expect: The browser navigates to the Service Levels storage configuration page.
- Select and provision a SQL Server or PostgreSQL ServiceLevels datasource on that page.
- Expect: The datasource is saved as the active snapshot storage for Service Levels.
Verify: Return to Service Levels: Health; the Snapshot storage is not selected panel is replaced by the Objective health and Latest active snapshots sections for the selected service.
Review compliance for a specific service and time window
Persona: Load-test operator or SLA owner
- Choose a service from the Service dropdown, for example svc.lg.fulmar.
- Expect: The page reloads to reflect the selected service's objectives and snapshots.
- Set the Window value to the lookback period you want to review.
- Expect: The field updates to the new number, ready to be applied on the next refresh or evaluation.
- Select Evaluate now.
- Expect: A fresh evaluation runs for the selected service and window, updating the Objective health status.
Verify: The Objective health section lists each objective's current status for the selected service, and Latest active snapshots shows evaluation results within the chosen Window.
Steps
Step 1
Open the Service Levels: Health page.
Expected result: The page loads with the Service filter set to Digital Workspace (Prod) and Window set to 30. Because no snapshot storage datasource is configured, a Snapshot storage is not selected panel appears in place of the Objective health and Latest active snapshots sections, with an Open storage button to resolve it.
This is the starting point for reviewing a service's SLA compliance, and it surfaces the one prerequisite you must satisfy before any health data can appear.
- The Service filter defaults to Digital Workspace (Prod) until you choose another configured service.
- The Window field defaults to 30; increase it to look further back, decrease it to focus on recent evaluations.
- The empty-state panel with Open storage replaces Objective health and Latest active snapshots until a ServiceLevels datasource is provisioned.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Service | Selects which configured service's compliance status and snapshots are shown. Choose a different service to switch the entire page to that service's objectives and history. | dropdown of services configured in Configuration: Service Levels: Services | No | Digital Workspace (Prod) |
| Window | Sets the lookback period used when evaluating objectives and listing recent snapshots. Increase it to see a longer compliance trend; decrease it to focus only on the most recent evaluations. | number | No | 30 |
Controls reference
Refresh (header)
Reloads the page's data using the current Service and Window selections.
Side effects: Read-only: it re-fetches and re-renders data, it does not change objectives, services, or storage configuration.
Refresh (filter row)
Reloads health data for the currently selected Service and Window, positioned directly next to the filters.
When to use: Use it right after changing the Service or Window value to confirm the new filter took effect.
Side effects: Read-only: reloads the current view, no data is created or modified.
Evaluate now
When to use: Use it after changing an objective's configuration or when you need current compliance status immediately rather than on the regular schedule.
Side effects: Mutating: it triggers a new evaluation and can add a new health snapshot. It requires snapshot storage to be provisioned before it can record or return results.
Open storage
Navigates to the Service Levels storage configuration page so you can select and provision a snapshot datasource.
When to use: Use it when this page shows Snapshot storage is not selected and you need to resolve that before any health data can be queried.
Side effects: Read-only on this page: it only navigates away. Provisioning the datasource itself happens on the storage configuration page.
Verify the result
When snapshot storage is provisioned and a service is selected, the Objective health section lists each objective attached to that service along with its current compliance status, and Latest active snapshots lists the most recent evaluation records within the chosen Window. Until snapshot storage is configured, the page instead shows Snapshot storage is not selected with an Open storage button, and neither section renders. If you expected compliance data but see the empty-state panel, the first thing to check is whether a SQL Server or PostgreSQL ServiceLevels datasource has actually been provisioned in Configuration: Service Levels: Storage, not just created. If data still does not appear after storage is configured, confirm the correct service is selected and that it has at least one objective attached.
Troubleshooting
- Symptom: The page keeps showing Snapshot storage is not selected even after creating a datasource. Fix: Confirm the datasource is specifically a ServiceLevels-type SQL Server or PostgreSQL connection in Configuration: Service Levels: Storage and that it has been selected as active there, not just created.
- Symptom: Clicking Evaluate now produces no new results. Fix: Verify snapshot storage is provisioned first; evaluation cannot record or return results without it, and confirm a service is selected.
- Symptom: The service you expect is missing from the Service dropdown. Fix: Confirm the service is defined in Configuration: Service Levels: Services.
- Symptom: Objective health has no entries for a selected service. Fix: Check that objectives have been attached to that service in Configuration: Service Levels: Objectives.
- Symptom: Refresh appears to do nothing on an empty page. Fix: Refresh only reloads data using the current Service and Window selections; it does not provision storage or create objectives, use Open storage or Configuration: Service Levels: Objectives for that.
- Symptom: The Window value is rejected or has no effect. Fix: Enter a positive whole number; a zero, negative, or non-numeric value is not a valid lookback window.
Related articles
- Prerequisite: Configuration: Service Levels: Storage - snapshot storage must be selected and provisioned here before health data can be queried
- Prerequisite: Configuration: Service Levels: Services - a service must be defined here before it appears in the Service filter
- Prerequisite: Configuration: Service Levels: Objectives - objectives attached to a service determine what Objective health measures
- See also: Service Levels: Dashboard - gives a broader view of SLA status across all services
- Next step: Service Levels: Violations - investigate specific breaches surfaced after reviewing health status
- See also: Configuration: Service Levels: Scheduler - controls automatic evaluations as an alternative to using Evaluate now manually