SLOs: excluded time

Embed
Preview of the card
<a href="https://watchtowerops.net/docs/slos"><img src="https://watchtowerops.net/docs/_api/public/orgs/aa5959cb-1a0b-4a9a-bc9a-913e7ac31cd9/spaces/b7aac181-9916-4805-b253-becc5fd2ca62/pages/70d5b79f-3a64-4bc6-8dec-be11c341ff3b/social-card.svg?v=3e7ae33eec8b" alt="SLOs: excluded time" width="600" height="315"></a>

An SLO's good and total counts leave out three kinds of time. All three apply alike to the burn rules (page and ticket), GET /v1/projects/{prj}/slos/{slo}/budget, monthly history, reports and SLAs that exclude maintenance.

  • Corrections: spans you add under slos/{slo}/corrections (at most 50 per SLO).

  • Maintenance windows: the project's maintenance windows.

  • Deploy windows (on by default): new SLOs have exclude_deploy_windows: true; send false on the SLO (POST/PUT /v1/projects/{prj}/slos[/{slo}]) to count failures during rollouts. SLOs backed by a monitor were switched on when this became the default. Every deployment (POST /v1/projects/{prj}/deployments, the deploy markers) of the SLO's environment and service then excludes [started_at, finished_at + deploy_window_s); a running deployment counts from its start. deploy_window_s is 60 to 86400 seconds, default 900. An SLO without an environment matches every environment; a deployment without a service matches every SLO.

In the console the toggle and the window length are on the SLO's Corrections tab, under Deploy windows.

Updated