OpenSLO/OpenSLO resource

Health v2 · maintenance only

Flags: no_releases

Adoption not part of the score

1515 stars · 69 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

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

learning-resource · maturity active

monitoring alerting configuration-management documentation monitoring apis cloud-computing cross-platform cli slo specification reliability-engineering sre yaml observability vendor-agnostic slo-as-code devops

Member repositories

For agents

markdown · JSON · MCP: product_card(name="OpenSLO/OpenSLO")