Jakub Warczarek

I'd like to see something like this. Let's go for it @trilopin, I can help if you need

Or just suggest some predefined and allow implementations to do they own

Both Sloth and Pyrra support only Prometheus which makes things much easier. OpenSLO aims to be flexible enough to support every data source. As described in https://github.com/OpenSLO/OpenSLO/issues/107, different data sources...

It's a really interesting idea @kenfinnigan & @proffalken, we need to discuss this further. I've seen https://github.com/OpenSLO/OpenSLO/issues/146. It should help with SLO adoption and cross-department understanding in bigger organizations that...

> The approach of "one failed they all failed" seems reasonable, I think there might be various ways of calculating the aggregated SLO - how the error budget will be...

Let's make it as flexible as needed. But referencing the whole SLO may be tricky because SLO can have multiple basically independent objectives thus we don't have one output of...

One more thing worth note is that the model of `Point` differs among different packages: - [influxdb-client-go/v2](https://pkg.go.dev/github.com/influxdata/influxdb-client-go/v2/api/write#Point) (from this package differs a lot from those listed below e.g missing sorting...

Howdy @Horgix @k1LoW What is the status of this issue? This feature will be useful also for me ;) Could @Horgix send this PR? I think `localDir` can be reused...

Yeah, using [scratch](https://hub.docker.com/_/scratch/) would be ideal, or at least using maybe something like [distroless](https://github.com/GoogleContainerTools/distroless). It requires some more testing thus I consider it the next step

Why do you suggest making `timeWindow[]` deprecated? There are real-world examples of use cases where you want to have defined multiple time windows per SLO. For example, a calendar-aligned window...