-
### Summary
I've been reading the spec, and noticed within the `SLO` type, the docs say `timeWindow` is *optional*. This is echoed in the [OpenAPI spec](https://github.com/OpenSLO/OpenSLO/blob/main…
-
### Summary
The JSON schema provided contains references that do not load / resolve. This prevents users from writing schemas with help from JSON / YAML language servers to provide inline-hinting f…
-
The [openslo.com](https://openslo.com/) uses Hugo under the hood which works with Markdown files. The raw Markdown file for [the specification from GitHub](github.com/OpenSLO/OpenSLO) is available und…
-
OpenSLO has released its v1 API at [https://github.com/OpenSLO/oslo/tree/main/pkg/manifest/v1](https://github.com/OpenSLO/oslo/tree/main/pkg/manifest/v1).
Currently, sloth only supports `openslo/v1…
-
On last SLOConf was announced by Nobl9 the OpenSLO, which aims to be an industry standard to define reliability and performance targets using a simple YAML specification.
The OpenSLO High lights ar…
-
API + SLA + SLO are things that go together. This spec links API (Rest) via OpenAPI.
What I can't see out there is a link between this spec and [OpenSLO](https://github.com/OpenSLO/OpenSLO).
Woul…
smoya updated
3 years ago
-
Hi team,
I am trying to generate some prometheus rules based on OpenSLO specification but even though my yaml is slightly different from the one provided by you, I am getting the following error:
…
-
It would be nice to use [OpenSLO](https://openslo.com/) format to define SLO instead or alongside the current specification.
-
Recently the OpensLO added support to define alerting for a SLO. See also this commit in OpensLO repo:
https://github.com/OpenSLO/OpenSLO/commit/08adc441a75b0043394849d65bdf853fc5349ead
-
### Problem to solve
Right now `oslo validate` relies on [govalidator](https://github.com/asaskevich/govalidator) and it's struct level annotations to run the validation of the selected specs.
Thi…