> ## Documentation Index
> Fetch the complete documentation index at: https://docs.use.observer/llms.txt
> Use this file to discover all available pages before exploring further.

# SLA methodology

> How Observer measures SLA attainment, applies contract terms and calculates credits on SLA statements.

> [!NOTE]
>
> **In short**
>
> * **Attainment** = available samples ÷ counted samples, per objective, over the contract period.
> * **Met** when attainment is not below the target. Exactly on target is met.
> * **Figures are truncated, never rounded up**, so a miss never displays as a met.
> * **Credits** come from the contract's tiers. A line with too little monitoring coverage has its credit held for you to apply or waive.
> * **Changes to terms apply from the next period.** A period always uses the terms in force at its start.

SLA Ledger turns a customer contract into a signed statement for each
period: attainment per line, met or missed, and any calculated credit.
Every statement names the methodology version it follows. The current
version is **version 1**, effective from 26 October 2026.

SLA Ledger is available on the Business and Enterprise plans.

## Worked example

A contract with one line: API availability, target **99.9%**, credit
tiers of 10% below 99.9% and 25% below 99%, fee \$2,000 per month.

| | |
| - | - |
| Period | October, 30 days, the check reports every minute |
| Counted samples | 43,200 |
| Unhealthy samples | 50 |
| Attainment | 43,150 ÷ 43,200 = 99.88425...% |
| Shown as | **99.884%** (truncated to three decimals) |
| Result | **Missed** (below 99.9%) |
| Credit | **10%** (below 99.9%, not below 99%) |
| Calculated amount | $2,000 × 10% = **$200\*\* |

## How attainment is measured

**1. Samples**

Each objective is measured from the status samples of the check behind
it: healthy, degraded, unhealthy or no data. Thresholds are strict: a
value exactly on a threshold does not match it.

**2. One line per objective**

Samples are never combined across objectives. Where statuses are rolled
up, the worst wins: unhealthy, then degraded, then healthy, then
unknown.

**3. What counts as downtime**

Unhealthy counts as downtime. Degraded counts as available, unless the
contract counts degraded as downtime.

**4. Exclusions**

When the contract excludes maintenance, published maintenance for the
affected service is removed: both its samples and its time.

* The contract chooses the **scheduled window** (overruns count) or the **actual start and end**.
* Unpublished maintenance is never removed. A canceled window is removed only up to its cancellation.
* With a **minimum notice**, a window published too late is not removed.
* Every window that touched a line is listed on the statement, with whether it was removed.

**5. Missing data**

* **No data samples** (the check could not reach its target) first take the check's own no data setting. That setting is recorded on each line.
* **Silence** is a gap longer than the check's reporting cadence allows, judged by the cadence in force when the gap started. It counts only after the check's first sample, never while the check was suspended, and only for checks that report on a fixed schedule or run without an agent.
* Silent time becomes samples at the rate the check reported in its observed hours.
* Unknown samples follow the contract's policy: **excluded** (coverage disclosed), **counted as downtime**, or **counted as available**.

**Coverage** is the share of measured clock hours that had at least one
sample. It does not depend on how often the check reports.

**6. Measured period**

A period runs from local midnight on its first day to local midnight
on the first day of the next period, in the contract time zone. Time
before the objective or the contract existed, and time that has not
happened yet, is not measured. Each line is measured over the time its
terms were in force.

**7. Records used**

Recent periods use individual samples. Older periods use status counts
kept for every 15 minutes, which hold the same totals. A boundary inside
a 15 minute block applies at the end of that block. Time with no records
left counts as unobserved and is disclosed.

**8. Met or missed**

Attainment = available samples ÷ counted samples. A line is met when
attainment is not below the target, compared at full precision.

**9. Displayed figures**

Three decimal places, truncated. 99.8996% shows as 99.899%.

**10. Daily figures**

Each day is measured on its own, as a guide to how the period went.
Daily figures are estimates and need not add up to the period figure.

> [accordion] Status marks shown beside a statement
>
> Hourly and daily status marks are not used for attainment. An hour is
> unhealthy when its unhealthy time reaches a threshold: two minutes for
> each minute of the check's interval, at least two and at most thirty,
> and never more than the time the hour was measured. A day shows its
> worst hour.

## Credits

A tier applies when attainment is **strictly below** its threshold.
When several tiers apply, the highest credit wins. Tiers are not
cumulative.

With tiers of 10% below 99.9%, 25% below 99% and 50% below 95%:

| Attainment | Credit |
| - | - |
| 99.95% | None |
| 99.9% | None (exactly on the threshold) |
| 99.5% | 10% |
| 98.2% | 25% |
| 94% | 50% |

* **Across lines**, the statement credit is the highest line credit or the sum of line credits, as the contract says, then capped.
* **Low coverage:** a line below the contract's minimum coverage keeps its credit as a proposal. You apply or waive it per line when approving, and the statement shows each decision.
* **Amount:** the fee per period (not prorated for a partial period) × the credit percentage, rounded to the currency's minor unit. It is a calculated amount, not an invoice.

## Contract settings

| Setting | Default | Options |
| - | - | - |
| Period | Calendar month | Calendar month or calendar quarter |
| Time zone | UTC | Any IANA time zone. Periods start at local midnight. |
| Close grace | 72 hours | Wait after a period ends, so late samples are included |
| Minimum coverage | 95% | Below this, a line's credit is held for your decision |
| Missing data | Excluded, coverage disclosed | Excluded, counted as downtime, or counted as available. A line can override it. |
| Downtime | Unhealthy only | Per line: unhealthy only, or unhealthy and degraded |
| Maintenance | Scheduled window | Scheduled window, or actual start and end. Set per line. |
| Minimum notice | None | Hours of notice a maintenance window needs to be excluded |
| Approval | Required | A statement is approved before it is delivered |
| Credit aggregation | Highest line credit | Highest line credit, or sum of line credits |
| Credit cap | 100% | The contract credit never exceeds this |
| Fee | None | With a currency. Shows the credit as an amount too. |

### Changing terms

* **Edits apply from the next period.** This covers line edits and removals, and the credit, fee, missing data, maintenance and coverage settings. The period in progress keeps the terms it started with.
* **Period and time zone are fixed** once a statement exists, or while a change is waiting for the next period. To change them, end the contract and start a new one.
* **Ending a contract** ends its lines with it. A new contract measures its own lines from its own start.

## Statements

| State | Meaning |
| - | - |
| Draft | Calculated, open for review |
| In review | Submitted for approval |
| Approved | Ready to deliver |
| Delivered | Sent to the contract's contacts |
| Superseded | Replaced by a later delivered revision |
| Void | Withdrawn before delivery, with a reason |

A delivered statement is never edited. To correct one, reopen it with a
reason: that creates a new draft revision and leaves the original as it
was. An issued or waived credit carries over to the new revision when
the recalculated credit is the same; if it changed, the credit is owed
again and flagged for review.

Every statement carries this line, with the provider's name:

> Measured by Observer from \<provider>'s configured checks.
> Calculated credits reflect the configured terms and are not an
> invoice.

## Verifying a statement

Each statement's payload is serialized in a canonical form and hashed
with SHA-256; the statement shows the hash. When signing is enabled for
your organization, statements are also signed with Ed25519 and show the
signing key id. Public keys, including retired ones, are published at
[use.observer/.well-known/observer-signing-keys](https://use.observer/.well-known/observer-signing-keys),
so a statement can be verified without Observer.

## Versions

A statement keeps citing the version it was issued under, and a
published version is never edited. A new version is published only when
the way attainment is calculated changes.

## Related

* [SLOs and error budgets](https://docs.use.observer/docs/concepts/slos-and-error-budgets.md)
* [How status is calculated](https://docs.use.observer/docs/concepts/how-status-is-calculated.md)
* [Threshold operators](https://docs.use.observer/docs/reference/threshold-operators.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.