-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only 0.0 - 1.0 objectives? #24
Comments
Can you give an example of an objective target where the availability would be something outside of 0-100%? |
Not for availability. I have only ever saw availability being 0-100%. But I thought this definition of
|
This should still be a 0-100% target. With TimeSliceTarget you'd be counting up the number of intervals per rolling window where the p95 was < your target divided by the total number of intervals per window.
This should presumably include a threshold that's acceptable, ex. 10 failed transactions per minute is 🆗 but beyond that isn't acceptable. |
This assumes the values will be only between 0% and 100% which seems to match the typical availability service level indicators. And generally a good practice. Although I saw other kind of SLIs in real-life.
Relevant SRE book chapter:
https://sre.google/workbook/implementing-slos/
which generally advocates for defining the 0%-100% ones. And even introduce the notions of "SLI specification" and "SLI implementations" with only the latter ones matching 0%-100%.
TLDR: I suggest to open up for other kind of SLIs, not only the [0,1] ones.
The text was updated successfully, but these errors were encountered: