# OpenSLO/OpenSLO

Open specification for defining and expressing service level objectives (SLO)

Repository: https://github.com/OpenSLO/OpenSLO
Canonical: https://ross.abutalabs.com/products/openslo
Homepage: https://www.openslo.com
Language: Makefile
License: Apache-2.0
License Family: permissive
Topics: slo, spec, specification
Last push: 2025-11-25T09:00:50+00:00

## Health v2 (maintenance only)
Score: 57/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 54, release rhythm 35, longevity 100
- inputs: {"age_days": 1954, "days_push": 281, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1515, forks 69 (observed 2026-08-28T04:04:56.540678+00:00)

## What it is
OpenSLO is an open, vendor-agnostic specification for defining service level objectives (SLOs) declaratively in YAML, covering SLOs, SLIs, data sources, alert policies, and services. It enables SLO-as-code workflows with GitOps and CI/CD validation, and is accompanied by SDKs and a validation CLI.

## Use cases
- define service level objectives as code in yaml
- standardize SLO definitions across monitoring vendors
- validate SLO config files in CI/CD pipelines
- manage reliability targets via GitOps workflows
- share SLO definitions between teams and tools
- implement SLO tooling against an open spec

## When to choose
- you want vendor-neutral, portable SLO definitions
- you practice SLO-as-code with GitOps and want declarative YAML
- you're building SLO tooling and need a common interchange format

## When to avoid
- you need a turnkey SLO monitoring or alerting product - this is only a specification
- you want platform-specific metric collection and error budget tracking out of the box

## Facets
- artifact type: learning-resource
- maturity: active
- function: monitoring, alerting, configuration-management, documentation
- domain: monitoring, apis, cloud-computing
- platform: cross-platform, cli
- tags: slo, specification, reliability-engineering, sre, yaml, observability, vendor-agnostic, slo-as-code, devops

## Member repositories
- OpenSLO/OpenSLO (main) score 57

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:56.540678+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:32:08.267730+00:00, confidence not recorded.
  - readme: https://github.com/OpenSLO/OpenSLO (fetched 2026-08-28T04:04:56.540678+00:00, sha f7939fb34571)
  - homepage: https://www.openslo.com (fetched 2026-08-29T11:35:35.477388+00:00, sha 276259702349)
- Data as of 2026-08-30T08:39:29.467469+00:00.