# slok/sloth

🦥 Easy and simple Prometheus SLO (service level objectives) generator

Repository: https://github.com/slok/sloth
Canonical: https://ross.abutalabs.com/products/slok-sloth
Homepage: https://sloth.dev
Language: Go
License: Apache-2.0
License Family: permissive
Topics: slo, service-level-objective, service-level, sli, sla, prometheus, monitoring, oncall, observability, alerts, alerting, metrics, google-slo, kubernetes, controller, operator, prometheus-operator, autogenerates-prometheus-slo, openslo
Last push: 2026-06-19T07:22:10+00:00

## Health v2 (maintenance only)
Score: 78/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 88, release rhythm 54, longevity 100
- inputs: {"age_days": 1975, "days_push": 75, "days_rel": 151, "gap_med": 94.0, "n_releases_24m": 5}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2541, forks 225 (observed 2026-08-28T04:06:59.426582+00:00)

## What it is
Sloth is a Go CLI and Kubernetes operator that generates Prometheus SLO recording rules and multi-window multi-burn alert rules from a simple SLO spec (YAML, OpenSLO, or Kubernetes CRDs). It also provides Grafana dashboards, a built-in web UI, and a Go library for integration.

## Use cases
- generate prometheus SLO recording rules from a simple spec
- set up multi window multi burn alerts for error budgets
- manage SLOs as Kubernetes CRDs with prometheus-operator
- validate SLO definitions in CI and GitOps pipelines
- auto-generate Grafana dashboards for SLO status
- standardize SLO definitions across teams
- convert OpenSLO specs into prometheus rules

## When to choose
- you use Prometheus and want reliable, uniform SLO metrics and burn-rate alerts without hand-writing rules
- you run Kubernetes with prometheus-operator and want SLOs managed via CRDs
- you want GitOps-friendly SLO spec validation and standardized conventions across services

## When to avoid
- you don't use Prometheus as your metrics backend
- you need a full SLO management platform with error-budget reporting and business dashboards rather than rule generation
- you want SLO tracking without defining PromQL SLI queries yourself

## Facets
- artifact type: cli-tool
- maturity: active
- function: monitoring, alerting, cli, configuration-management, developer-tools
- domain: monitoring, self-hosted
- platform: windows, cli, go
- tags: prometheus, slo, sli, error-budget, openslo, prometheus-operator, grafana-dashboards, kubernetes-operator, gitops, devops, sre, linux, macos, kubernetes, docker

## Member repositories
- slok/sloth (main) score 78

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:59.426582+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-30T02:25:08.424773+00:00, confidence not recorded.
  - readme: https://github.com/slok/sloth (fetched 2026-08-28T04:06:59.426582+00:00, sha e13415b39e7b)
  - homepage: https://sloth.dev (fetched 2026-08-29T10:07:15.487495+00:00, sha 50d2d78fae5d)
  - site_page: https://sloth.dev/examples/default/getting-started (fetched 2026-08-29T10:07:15.496513+00:00, sha 0c2e0447e065)
  - site_page: https://sloth.dev/introduction/features (fetched 2026-08-29T10:07:15.500699+00:00, sha 35ad9805bd05)
  - site_page: https://sloth.dev/introduction/install (fetched 2026-08-29T10:07:15.502309+00:00, sha 181a1202e9e7)
  - site_page: https://sloth.dev/examples/kubernetes/getting-started (fetched 2026-08-29T10:07:15.503988+00:00, sha 4a63f2da546c)
  - site_page: https://sloth.dev/examples/openslo/getting-started (fetched 2026-08-29T10:07:15.505815+00:00, sha a1777d077e20)
  - site_page: https://sloth.dev/faq (fetched 2026-08-29T10:07:15.498686+00:00, sha 8c796630b6de)
- Data as of 2026-08-30T08:39:29.467469+00:00.