Skip to main content
APIContext
Talk to salesStart free
Start HereGuidesConceptsCLIReferenceChangelogStatus

SLO and SLA Management

APIContext lets you define Service Level Objectives (SLOs) for a project and track whether its monitors meet them. For an overview of SLO/SLA capabilities, 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​

SLOs are set per project. Each one is a metric and a threshold:

GroupMetrics
Core MetricsAvailability, Pass Rate (greater than); Slow Rate, Warning Rate, Fail Rate (less than); DNS Lookup, TCP Connect, SSL Handshake, Network time, Upload time, Processing time, Download time, Server time, Total latency excluding DNS, Total latency (less than); Quality score, Apdex score (greater than)
Core Web VitalsFor browser monitors

Performance Change Thresholds catch a monitor getting worse even while it still meets its SLOs:

ThresholdUnit
Decrease in pass / fail gradepercentage points
Increase in any latency componentmilliseconds or percent

Setting up an SLO​

Step 1: Open the SLO settings​

  1. Open Conformance Settings: in the left sidebar, select Conformance, then the Settings tab.
  2. Find the Manage Service Level Objectives and Performance Change Thresholds section.

Step 2: Add an SLO​

  1. Under Service Level Objectives, pick a metric from Core Metrics (or Core Web Vitals).
  2. Set the threshold, for example Availability greater than 99.9 percent, or Quality score greater than 8.
  3. Click Add SLO, then Save.

For the Quality score scale, see CASC Score:

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

Step 3: Add a Performance Change Threshold​

  1. Under Performance Change Thresholds, choose Decrease in pass / fail grade or Increase in any latency component.
  2. Set the amount and unit.
  3. Click Add Threshold.

To return every SLO in the project to the defaults, use Reset SLOs in Project and confirm.

Step 4: Get alerted and check results​

  • Alerts. Set up notifications in Alerts & Webhooks (under Configure Monitoring in the sidebar). See Setting up alerts.
  • Results. The Conformance Summary has a row each for Availability SLOs, Performance SLOs, and Performance Thresholds, with pass or fail and issue counts. Use Download as CSV for SLA reporting.

Edit or delete an SLO​

You can change or remove an SLO at any time. Both changes apply to the project's SLOs, not to individual monitors.

  1. Open the Manage Service Level Objectives and Performance Change Thresholds section of Conformance Settings, as in Step 1.
  2. Under Service Level Objectives, find the SLO in Core Metrics or Core Web Vitals. Each row shows the metric, its threshold, and, for most metrics, the unit.
  3. To edit the SLO, change the threshold in the row. You can also pick a different metric or unit from the same row. The row shows a message if the value is out of range, for example "Please enter a whole number between 0 and 120000" for a latency threshold.
  4. To delete the SLO, select the red trash icon at the end of its row.
  5. Click Save. The button is available once you have changed something and every value is valid, and an edit or a delete takes effect only after you save.

Performance Change Thresholds work the same way: edit the amount or select the trash icon, then click Save.

See also​