On the recordRead 14 Nov 202615 facts
OpenSLO
Plans and prices
Apache License 2.0
Free
perpetual worldwide copyright license · no-charge and royalty-free · provided as is without warranty
Read 14 Nov 2026 · github.com
On the record
- Alert destinations
- Alert notification targets are implementation-specific, and the examples include email, Slack, a webhook, and Opsgenie.openslo.com · read 14 Nov 2026
- Alert limit
- An alert policy allows only one alert condition, which is a burn-rate comparison.openslo.com · read 14 Nov 2026
- Budgeting methods
- An SLO must use Occurrences, Timeslices, or RatioTimeslices budgeting.openslo.com · read 14 Nov 2026
- CLI platforms
- The Oslo release configuration builds Windows, Linux, and Darwin binaries for amd64 and arm64.raw.githubusercontent.com · read 14 Nov 2026
- Go SDK status
- The Go SDK decodes, validates, and encodes OpenSLO objects, is still in active development before v1, and expects breaking API changes.github.com · read 14 Nov 2026
- Metric integrations
- Data source type is implementation-defined, with Prometheus and Datadog given as examples, and connection details may include endpoints or authentication.openslo.com · read 14 Nov 2026
- Name limit
- Object names must be 1 to 63 characters and match an RFC-1123 label.openslo.com · read 14 Nov 2026
- Object model
- Version 1 defines Service, SLO, SLI, DataSource, AlertPolicy, AlertCondition, and AlertNotificationTarget objects.openslo.com · read 14 Nov 2026
- Oslo CLI
- Oslo validates and formats OpenSLO YAML and JSON locally or in CI/CD, and it can be installed with prebuilt binaries, Go, Homebrew, Docker, or from source.openslo.com · read 14 Nov 2026
- Scope limit
- Platform-specific implementation details are outside the specification, which is meant to stay vendor-agnostic, Kubernetes-YAML compliant, and extensible.openslo.com · read 14 Nov 2026
- SLOs as code
- Users define thresholds, metrics, and goals for applications and infrastructure in a Git-oriented workflow.openslo.com · read 14 Nov 2026
- Support
- Contributions are reviewed by maintainers, and community discussion is directed to the Slack linked from openslo.com.github.com · read 14 Nov 2026
- Vendor neutrality
- The specification is implementation neutral so multiple vendors and projects can share SLOs in one format.openslo.com · read 14 Nov 2026
- What it is
- OpenSLO is a YAML language for declaring service level objective reliability and performance targets.openslo.com · read 14 Nov 2026
- Who it is for
- It is aimed at the reliability engineering ecosystem and at organizations that create, operate, and run cloud services and applications.openslo.com · read 14 Nov 2026
