SLOs
Service-level objectives, error budgets, and scheduled uptime reports
List service-level objectives
List service-level objectives
Create a service-level objective
Create a service-level objective
Get a service-level objective
Get a service-level objective
Update a service-level objective
Update a service-level objective
Delete a service-level objective
Delete a service-level objective
Evaluate an objective over the current calendar window
Evaluate an objective over the current calendar window
Past monthly windows for an objective
Past monthly windows for an objective
Error-budget burn-down for the current window
Cumulative series. Consumption is accrued per step and summed forward, so `budgetRemainingSeconds` is monotonically non-increasing by construction — it cannot climb back up when probe density changes. It is not clamped at zero: an overspent budget reports a negative remainder. A step with no countable probe spends nothing (no data is not downtime).
List an objective's burn-rate alert policies
Two built-in multiwindow burn-rate policies (`fast` and `slow`), materialized on demand so an objective created before the feature existed answers exactly like a new one. Both start disabled — alerting is opt-in. `longBurnRate` / `shortBurnRate` are recomputed for the request rather than read back from the stored readout, and are null (never 0) when a window carries no countable probe.
Get one burn-rate alert policy
Get one burn-rate alert policy
Tune a burn-rate alert policy
`kind` is not writable — there are exactly two built-ins. Changing a threshold or either window clears the auto-resolve hysteresis anchor, which was measured against the old numbers.
List scheduled uptime reports
List scheduled uptime reports
Create a scheduled uptime report
Create a scheduled uptime report
Get a scheduled uptime report
Get a scheduled uptime report
Update a scheduled uptime report
Update a scheduled uptime report
Delete a scheduled uptime report
Delete a scheduled uptime report
Send the report immediately to the caller
Renders the report for the period that most recently closed and mails it to the authenticated caller (or to `recipient`). It never fans out to the schedule's recipient list. Returns 409 instead of 202 when the resolved recipient is on the organization's suppression list, since nothing is actually queued in that case.