SLO burn rate

[melchiormoulin]

Hello, since there a customressource to define SLO #807
How can we define burn rate alert based on this SLO CR ?
It seems there is some internal discussions ( this comment #807 (comment) )

[vlinevych]

I've found an example of slo alert, but the problem is that it requires slo-hash-id in the query.

For burn rate alert the query would be something like this:

query: "burn_rate(\"slo-hash-id\").over(\"30d\").long_window(\"1h\").short_window(\"5m\") > 14.4"

It would be great to have slo burn rate alert implemented in the operator.

[melchiormoulin]

Hello do you think there is any chance to see this feature please @fanny-jiang @ddjamesfrullo ? :)

[jurabek]

There is possibility to create CRD only for burn rate and pass those values as attributes instead of hard-coded string query: "burn_rate(\"slo-hash-id\").over(\"30d\").long_window(\"1h\").short_window(\"5m\") > 14.4" value, and this gives us referencing parent SLO into this alert more natively, k8s operator does provide such functionality I will try work on that, in my free time.

[melchiormoulin]

Hey do you think it can be implemented ? Maybe @jurabek ?
It would be super nice :)

[melchiormoulin]

i've created #1871 wdyt ?