Service Levels: Violations

Updated

Service Levels: Violations

Overview

Use this page to review breach and no-data violation diagnostics for a service and time window. A breach is a period when a monitored service failed its configured service-level objective; NoData is a period when no measurement data was available to evaluate that objective. Together these diagnostics tell you not just whether a service is failing its targets, but whether the underlying monitoring itself produced usable data.

Service Levels: Violations sits downstream of the service and objective definitions you configure elsewhere: a service must exist, with at least one objective, before this page has anything to evaluate. It also depends on a dedicated SQL Server or PostgreSQL ServiceLevels datasource to store evaluated snapshots; without one, violation data cannot be queried at all. The diagnostics produced here reflect the same service-level evaluation that drives the service's overall status elsewhere in Service Levels.

On this page, you select a Service and a Window in days, then either refresh the current view or run a new evaluation with Evaluate now. If storage isn't yet configured, the page replaces diagnostics with a prompt to provision one via Open storage.

Key concepts

  • Service - The monitored application or system whose service-level objective is evaluated for violations on this page. (related: Configuration: Service Levels: Services)
  • Window - The number of days of history included when evaluating the selected service for breaches and no-data periods.
  • Breach and NoData diagnostics - The two outcomes this page reports: a Breach is a period when the service failed its objective threshold, and NoData is a period when no measurement data existed to evaluate the objective. (related: Service Levels: Objectives)
  • Snapshot storage - The SQL Server or PostgreSQL ServiceLevels datasource that holds evaluated service-level snapshots; it must be selected and provisioned before this page can query violation data. (related: Configuration: Service Levels: Storage)

When to use it

  • When you need to confirm whether a service breached its service-level objective within a recent window.
  • When you're investigating missing or incomplete monitoring data (NoData) for a service.
  • Before citing violation history in a status page update or report.
  • When troubleshooting an alert that fired for a service, to see the underlying breach or no-data pattern.
  • After changing an objective's threshold, to re-evaluate and confirm the change is reflected.

Before you begin

  • At least one service must be defined in Configuration: Service Levels: Services.
  • A service-level objective must be configured for that service in Configuration: Service Levels: Objectives, so there is a threshold to evaluate breaches against.
  • A SQL Server or PostgreSQL ServiceLevels datasource must be selected and provisioned in Configuration: Service Levels: Storage; until it exists, this page cannot query violation data.
  • Credentials used for data collection should be current; a token nearing expiry surfaces as a warning banner on this page and should be reissued under Configuration: Credential Profiles.

Common workflows

Check a service for recent violations

Persona: Load-test operator or SRE

  1. Select the service to check from the Service dropdown, for example svc.lg.fulmar.
    • Expect: The page's evaluation context switches to the selected service.
  2. Set the Window field to the number of days you want to evaluate.
    • Expect: The window value used for the next evaluation or query updates to the entered number.
  3. Select Evaluate now.
    • Expect: A new evaluation run starts for the selected service and window.
  4. Select Refresh once the evaluation has had time to complete.
    • Expect: The page reloads its status; if a ServiceLevels datasource is configured, Breach and NoData diagnostics appear in place of the empty-state panel.

Verify: The empty-state panel is replaced by violation diagnostics for the selected service and window. If 'Snapshot storage is not selected' still appears after Refresh, the evaluation could not be queried.

Provision storage to unblock violation queries

Persona: Admin

  1. Select Open storage from the empty-state panel.
    • Expect: You navigate to the Service Levels storage configuration page.
  2. Select and provision a SQL Server or PostgreSQL ServiceLevels datasource on that page.
    • Expect: A datasource is now configured to store evaluated service-level snapshots.
  3. Return to Service Levels: Violations and select Refresh.
    • Expect: The 'Snapshot storage is not selected' message clears because violation data can now be queried.

Verify: The empty-state message and Open storage button are gone, replaced by violation diagnostics for the selected Service and Window.

Steps

Step 1

Open Service Levels: Violations.

Expected result: The page loads with Digital Workspace (Prod) selected in the Service dropdown and Window set to 30; because no ServiceLevels datasource is configured yet, a 'Snapshot storage is not selected' panel appears in place of violation diagnostics, alongside a banner warning that the Orders API token expires in 4 days.

This is the starting point for reviewing breach and no-data diagnostics once storage is in place.

  • Service defaults to Digital Workspace (Prod).
  • Window defaults to 30 (days).
  • Evaluate now and Open storage remain enabled even though no data can be queried yet.
  • The credentials-expiring banner includes a Dismiss (close) control. Service Levels: Violations - step 1

Step 2

Select Refresh.

Expected result: The page reloads its status checks: the credentials-expiring banner closes, leaving only the 'Snapshot storage is not selected' message and its reminder to select and provision a SQL Server or PostgreSQL ServiceLevels datasource.

Refreshing re-runs the page's checks so you can confirm whether a newly provisioned datasource or renewed credential has resolved the warnings.

  • Refresh now appears in both the header and the panel after reload.
  • The credentials-expiring banner and its Dismiss control are no longer shown. Service Levels: Violations - step 2

Field reference

Field Purpose Format / Validation Required Default
Service Selects which monitored service's violation history to display. Changing it switches diagnostics to the objective and data configured for that service. dropdown, list of configured services No Digital Workspace (Prod)
Window Sets how many days of history to evaluate for breaches and no-data periods. A larger window surfaces more historical violations but can dilute recent patterns; a smaller window isolates recent incidents. number, days No 30

Controls reference

Refresh

Reloads the page's status checks and current data without changing the Service or Window selection.

When to use: Use to pick up changes made elsewhere, such as a newly provisioned datasource or a renewed credential, without re-selecting Service and Window.

Side effects: Read-only: re-runs the page's checks. In this capture, clicking Refresh also cleared the credentials-expiring banner, suggesting that warning is re-evaluated on refresh rather than permanently dismissed. It does not modify any service-level configuration.

Evaluate now

Triggers a fresh evaluation of the selected service against its objective for the chosen Window, to produce the Breach and NoData diagnostics for the page.

When to use: Use after changing the Service or Window, or when you want up-to-date diagnostics rather than the last stored evaluation.

Side effects: Mutating: starts a new evaluation run. In this capture, snapshot storage was not selected, so evaluation results could not be queried until a ServiceLevels datasource is provisioned.

Open storage

Navigates to the storage configuration page where you select and provision a SQL Server or PostgreSQL ServiceLevels datasource.

When to use: Use when the page shows 'Snapshot storage is not selected', before you can query any violation data.

Side effects: Read-only navigation: leaves this page without changing any Violations settings.

Dismiss

Closes the credentials-expiring warning banner for the current view.

When to use: Use to clear the warning after you've noted it or already reissued the credential.

Side effects: Read-only: hides the banner only; it does not reissue or renew the credential itself.

Verify the result

When this page is working as intended, selecting a Service and Window and running Evaluate now replaces the empty-state panel with Breach and NoData diagnostics for that service and window. If instead you see 'Snapshot storage is not selected', no ServiceLevels datasource has been provisioned yet, and no violation data can be returned regardless of which Service or Window you choose. Check Configuration: Service Levels: Storage first when diagnostics don't appear. If storage is configured but diagnostics still look wrong, confirm the selected Service has an objective configured in Configuration: Service Levels: Objectives.

Troubleshooting

  • Symptom: The page shows 'Snapshot storage is not selected' instead of violation diagnostics. Fix: Select Open storage and provision a SQL Server or PostgreSQL ServiceLevels datasource, then return and select Refresh.
  • Symptom: A banner warns that a credential used for data collection is expiring soon. Fix: Reissue the named credential under Configuration: Credential Profiles before it expires; dismissing the banner only hides it in this view.
  • Symptom: Selecting Evaluate now doesn't produce any visible diagnostics. Fix: Confirm a ServiceLevels datasource is selected and provisioned; evaluation results cannot be queried without one.
  • Symptom: Changing Window doesn't seem to affect what's shown. Fix: Select Refresh or Evaluate now after changing Window; the value only takes effect on the next evaluation or query, not as you type.
  • Symptom: The credentials-expiring banner reappears after you dismissed it. Fix: The credential still hasn't been reissued; complete that step under Configuration: Credential Profiles rather than dismissing the banner again.
Was this article helpful?
0 out of 0 found this helpful