Skip to main content
PreparationZone Logo
PrepZone

SLI, SLO, and Error Budgets

Measure what users feel, set targets, and spend error budget on risky launches.

Pass checkpoint below

Why this matters

  • SRE interviews center on SLI/SLO design — not "we aim for 99.9%" without defining what is measured.
  • Error budgets gate risky releases: when ShardPay burns budget on transfer failures, feature freezes until reliability recovers.
  • SLAs with financial remedies (merchant credits) must be backed by SLOs you actually monitor — not aspirational dashboards.
  • Picking SLIs users feel separates senior answers from uptime-of-CPU metrics nobody notices.
SLI99.2% transfers succeed
SLOTarget 99.95%
SLAContract + credits
SLI is what you measure; SLO is your internal target; SLA is the customer contract with consequences.

From metric to contract

The hierarchy flows downward: define what users experience (SLI), set an internal target (SLO), then optionally contract with remedies (SLA). ShardPay's transfer path uses this chain consistently.

SLI example: (successful transfers within 200ms) / (total transfer attempts) measured over a rolling 30-day window at the API gateway — the user-facing edge, not internal shard latency.

SLO example: 99.95% of transfer attempts succeed within 200ms, measured monthly. This is ShardPay's internal target; on-call pages when burn rate threatens the monthly budget.

SLA example: Merchant enterprise contract guarantees 99.9% monthly availability with service credits of 10% MRR per 0.1% miss. The SLA is lower than the SLO — ShardPay aims for 99.95% internally to absorb variance before SLA breach.

Key points

  • SLI (Service Level Indicator) — a quantitative measure of some aspect of service behavior. ShardPay's primary transfer SLI is success rate within latency threshold, not CPU utilization or pod restart count.
  • SLO (Service Level Objective) — an internal target value for an SLI over a time window. ShardPay's transfer SLO is 99.95% monthly; fraud scoring has a separate SLO of 99.9% under 100ms.
  • SLA (Service Level Agreement) — a business contract with remedies when SLO-like thresholds are missed. ShardPay's enterprise SLA triggers credits at 99.9%; consumer merchants have best-effort terms only.
  • Error budget — the allowed bad events before SLO breach: 1 - SLO. At 99.95% SLO, ShardPay allows 0.05% failed-or-slow transfers per month — roughly 1,500 failures at current volume.

The rest of this guide is part of Pro

Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.

Still to come · 2 sections

  • Designing ShardPay SLIs
  • Error budget policy

Test yourself

Answer these before moving on — recall is what makes it stick.