Service Levels: Violations
Overview
Use this page to diagnose breach and no-data violations for a service over a selected time window. A breach is a period where a monitored service failed to meet its configured thresholds; a no-data result means the window lacked enough telemetry to evaluate the service, which can hide a real outage behind a blank result. This page checks one service and period at a time, instead of scanning aggregate dashboards for anomalies.
Violations depends on setup elsewhere: the service and its objective thresholds from Configuration: Service Levels: Services and Configuration: Service Levels: Objectives, plus the snapshot storage datasource provisioned on Configuration: Service Levels: Storage. The results it surfaces feed the broader status on Service Levels: Dashboard and Service Levels: Health, and can justify a status page update or a ticket.
On this page, you pick a service and a lookback window, then refresh to see the latest computed results or evaluate on demand for current status. Until a ServiceLevels datasource is provisioned, the page shows an empty state linking directly to the storage configuration page instead of a results table.
Key concepts
- Service - The monitored system or application tracked under Service Levels; selecting one scopes the diagnostics on this page to its data. (related: Configuration: Service Levels: Services)
- Window - The number of days of history to evaluate for breaches and no-data gaps when you refresh or evaluate.
- Breach - A period within the window where the service failed to meet the thresholds configured for it. (related: Configuration: Service Levels: Objectives)
- NoData - A period within the window where there was not enough telemetry to evaluate the service at all, distinct from a pass or a breach.
- Snapshot storage - The SQL Server or PostgreSQL ServiceLevels datasource that stores the computed data this page queries; without it, violation data cannot be retrieved. (related: Configuration: Service Levels: Storage)
When to use it
- You need to confirm whether a specific service breached its service-level objectives during a recent period.
- You want to rule out a telemetry gap (no data) as the cause of an apparent incident, rather than an actual breach.
- You are investigating an anomaly flagged on Service Levels: Dashboard or Service Levels: Health and need window-level detail.
- You are preparing evidence for a status page update or an internal report covering an incident window.
Before you begin
- At least one service exists for your environment, configured on Configuration: Service Levels: Services (the Service dropdown lists it, for example Digital Workspace (Prod)).
- The service has objective thresholds configured on Configuration: Service Levels: Objectives, since a breach is measured against those thresholds.
- A SQL Server or PostgreSQL ServiceLevels datasource is selected and provisioned on Configuration: Service Levels: Storage; until it is, this page shows Snapshot storage is not selected instead of results.
- Your account has access to the Service Levels module.
Common workflows
Diagnose breaches for a service over a time window
Persona: Service Levels operator or admin
- Select the service to diagnose from the Service dropdown.
- Expect: The diagnostics scope changes to that service, so the next refresh or evaluation applies to it.
- Set the Window field to the number of days you want to check.
- Expect: The lookback period used for the next evaluation changes to match the value you entered.
- Select Evaluate now to run an on-demand check.
- Expect: LoadGen evaluates the service against its objectives for the chosen window and the Violation diagnostics results update with breach and no-data entries.
Verify: The empty-state panel is replaced by Violation diagnostics results for the selected Service and Window, listing breach and no-data periods if any occurred.
Provision snapshot storage to unlock violation diagnostics
Persona: Service Levels admin
- Select Open storage from the empty-state panel.
- Expect: LoadGen 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 configured ServiceLevels storage.
- Return to Service Levels: Violations and select Refresh.
- Expect: The Snapshot storage is not selected message is replaced by the Service and Window diagnostics panel, now able to query violation data.
Verify: The Snapshot storage is not selected message no longer appears, and Evaluate now produces diagnostic results instead of being blocked.
Steps
Step 1
Open the Service Levels: Violations page from the Service Levels section.
Expected result: The page loads with Service defaulted to Digital Workspace (Prod) and Window defaulted to 30, but shows an empty-state panel reading Snapshot storage is not selected instead of diagnostic results, because no ServiceLevels datasource has been provisioned yet.
This is the starting point for diagnosing breach and no-data violations once the prerequisite storage is configured.
- Service and Window are preset but cannot be evaluated until storage is provisioned.
-
Open storage is the only way forward from this empty state.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Service | Selects which monitored service's breach and no-data diagnostics this page queries; choosing a different service changes the objectives and historical snapshots evaluated. | dropdown, populated from configured services | No | Digital Workspace (Prod) |
| Window | Sets how many days of history to evaluate for breaches and no-data gaps. A larger window checks a longer period and can surface chronic or intermittent issues; a smaller window isolates a narrow recent period for drilling into a specific incident. | number (days) | No | 30 |
Controls reference
Refresh (page header)
Reloads the current page view.
When to use: Use after making a change elsewhere, such as provisioning storage, to confirm whether this page now shows results.
Side effects: Read-only: reloads the view with the same Service and Window values; does not change any configuration or data.
Refresh (Window panel)
Re-queries diagnostics for the currently selected Service and Window.
When to use: Use after changing Service or Window to pull the latest already-computed results for that combination.
Side effects: Read-only: re-queries existing results; does not trigger a new evaluation.
Evaluate now
Runs an on-demand evaluation of the selected service against its objectives for the chosen window.
When to use: Use when you need current status immediately rather than whatever was last computed on a schedule.
Side effects: Mutating: runs the evaluation and updates the stored results for the selected Service and Window, instead of just displaying the last computed snapshot.
Open storage
Navigates to the Service Levels storage configuration page.
When to use: Use when the page shows Snapshot storage is not selected and you need to set up the datasource it depends on.
Side effects: Navigation only: takes you to another page and does not itself provision anything.
Verify the result
Once a ServiceLevels datasource is provisioned and you select Evaluate now or Refresh, the empty-state panel is replaced by the Violation diagnostics results for the selected Service and Window. If no service is selected, the page shows a No service selected message instead of results. If you still see Snapshot storage is not selected after provisioning a datasource, return to this page and select Refresh rather than assuming the setup failed. The first thing to check when diagnostics do not appear is whether a service is selected and whether the datasource was actually saved on the storage configuration page.
Troubleshooting
- Symptom: The page shows Snapshot storage is not selected instead of diagnostics. Fix: Select Open storage, provision a SQL Server or PostgreSQL ServiceLevels datasource, then return and select Refresh.
- Symptom: Evaluate now appears to do nothing and the diagnostics panel stays empty. Fix: Confirm the ServiceLevels snapshot storage is provisioned; Evaluate now cannot query or write results without a configured datasource.
-
Symptom: The service you expect to check, for example a service named
svc.lg.fulmar, isn't listed in the Service dropdown. Fix: Add and configure it first on Configuration: Service Levels: Services. - Symptom: Increasing Window doesn't surface breaches you know occurred. Fix: Confirm the service's objectives are configured correctly on Configuration: Service Levels: Objectives; this page only diagnoses against existing objective thresholds.
- Symptom: Selecting Refresh next to Window reloads but still shows the empty state. Fix: This control re-queries with the current Service and Window values only; it cannot unlock data until storage is provisioned via Open storage.
Related articles
- Prerequisite: Configuration: Service Levels: Storage - provisions the SQL Server or PostgreSQL datasource this page needs before it can query violation data
- Prerequisite: Configuration: Service Levels: Services - defines the services selectable in the Service dropdown
- Prerequisite: Configuration: Service Levels: Objectives - defines the thresholds a breach is measured against
- See also: Service Levels: Dashboard - gives an aggregate view of service-level status that this page lets you drill into
- See also: Service Levels: Health - complements violation diagnostics with ongoing service health status