Skip to main content
APIContext
Talk to salesStart free
Start HereGuidesConceptsCLIReferenceChangelogStatus

SLO and SLA Management

APIContext lets you define Service Level Objectives (SLOs) for your monitors and projects, then track compliance over time in the Quality Analytics dashboard. For an overview of SLO/SLA capabilities including burn-rate alerting and vendor attribution, see SLO/SLA Management on the platform site.

For background on SLOs, SLAs, and how they relate to the CASC Quality Score, see SLA Model.

What you can configure​

Objective typeDescription
Availability SLOMinimum percentage of passing calls over a rolling window
Latency SLOMaximum acceptable response time (P50, P95, P99, or average)
Conformance SLOMinimum conformance pass rate for schema and security profiles
CASC Quality Score SLOMinimum Quality Score threshold (0–9.99) for the project

Setting up a CASC-based SLO​

Step 1: Open conformance and SLO settings​

  1. In the left sidebar, under CONFIGURE MONITORING, click SLA Settings (or find it under Project Settings → SLA).
  2. You will see the current SLO configuration for the project.

Step 2: Configure the threshold​

Set the Minimum Quality Score threshold. The default is ≥ 7.99 (the "healthy" range). See CASC Score concept for the full scale definition.

RangeHealth status
8.00 – 9.99Healthy
5.00 – 7.99Degraded
0 – 4.99Critical

Step 3: Set the evaluation window​

Choose how the SLO is evaluated:

  • Rolling 24 hours — the most recent 24 hours of data
  • Rolling 7 days — trailing week
  • Calendar month — resets at the start of each month

Step 4: Configure alerts​

Enable alerts so you are notified when the SLO is at risk or breached:

  1. Go to Alerting → SLO Alert.
  2. Configure alert thresholds (e.g., alert when Quality Score drops below 8.00 for more than 30 minutes).
  3. Choose your notification channel (email, Slack, webhook).

See Setting up alerts.

Performance Change Thresholds​

In addition to SLOs, you can configure Performance Change Thresholds that alert when a monitor's performance degrades relative to its historical baseline — even if it hasn't breached an absolute SLO.

Configure these under Project Settings → Performance Thresholds:

  • Latency change: alert if response time increases by more than N% over the baseline
  • Error rate change: alert if failure rate increases by more than N percentage points

Viewing SLA compliance​

The Quality Analytics dashboard (INVESTIGATE → Quality Analytics) shows:

  • Current Quality Score and trend
  • SLO compliance percentage for each configured objective
  • Time-in-breach breakdown by monitor and time window
  • Export to CSV for SLA reporting

See also​