Skip to main content
APIContext
Talk to salesStart free
Start HereGuidesConceptsCLIReferenceChangelogStatus

Setting up performance SLOs/SLAs and thresholds

Key Concepts​

You can set project-level Service Level Objectives (SLOs), which can also be used to track Service Level Agreements (SLAs). When a monitor sequence does not conform to the SLO thresholds you have defined, the system will trigger alerts; you'll also see violations in the reporting interface.

SLOs can be created based on the timing of the whole monitor, or based on the timing for a single component of the call. You can set SLOs and receive alerts based on the following metrics (individually or in combination):

  • Overall availability rate (as a percent of all monitors run)
  • Overall pass rate (as a percent of all monitors run)
  • Overall slow rate (as a percent of all monitors run)
  • Overall warning rate (as a percent of all monitors run)
  • Overall fail rate (as a percent of all monitors run)
  • Total latency (in milliseconds)
  • DNS lookup time (in milliseconds)
  • TCP connect time (in milliseconds)
  • SSL handshake time (in milliseconds)
  • Total network time (in milliseconds)
  • Upload time (in milliseconds)
  • Processing time (in milliseconds)
  • Download time (in milliseconds)
  • Overall server time (in milliseconds)
  • CASC quality score (based on score range)
  • Apdex score (based on score range)

Conformance Settings page listing Service Level Objective criteria such as availability, slow rate, latency and quality score thresholds

To add, change, or delete SLOs and thresholds, follow the steps in SLO and SLA Management.

You can also set performance change thresholds, which evaluates changes in various performance components and trigger alerts when those thresholds are exceeded.

Thresholds can be set against the following criteria:

  • Increase in any latency component (in milliseconds or percent)
  • Decrease in pass / fail grade (in percentage points)

For a broader overview of APIContext's SLO/SLA capabilities (including burn-rate alerting, multi-supplier workflow tracing, and regulator-ready evidence), see SLO/SLA Management.