Add downtime recording rules for moving time windows - #31
Conversation
| - record: downtime | ||
| labels: | ||
| kind: moving | ||
| in: four_weeks |
There was a problem hiding this comment.
One open question is if we should do 4 weeks or 30 days for the moving window "month". 4 weeks is nice because it builds on the previous recording rule, but 30 days is usually closer to the length of a month.
There was a problem hiding this comment.
I think I chose 4 weeks because I remember reading something about it in the SRE book. I looked it up now:
https://sre.google/workbook/implementing-slos/
We recommend defining this period as an integral number of weeks so it always contains the same number of weekends. For example, if you use a 30-day window, some periods might include four weekends while others include five weekends. If weekend traffic differs significantly from weekday traffic, your SLIs may vary for uninteresting reasons.
Co-authored-by: Wesley Bermbach <wesley.bermbach@sap.com> Co-authored-by: Istvan Zoltan Ballok <istvan.zoltan.ballok@sap.com>
a5ddcb5 to
39f39f4
Compare
Co-authored-by: Wesley Bermbach <wesley.bermbach@sap.com> Co-authored-by: Istvan Zoltan Ballok <istvan.zoltan.ballok@sap.com>
The previous name error budget didn't capture it well that actually the downtime of the sni-s is calculated. Co-authored-by: Wesley Bermbach <wesley.bermbach@sap.com> Co-authored-by: Istvan Zoltan Ballok <istvan.zoltan.ballok@sap.com>
39f39f4 to
931e632
Compare
What this PR does / why we need it:
Add downtime recording rules for moving time windows