Skip to content
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

Target/Budget configuration confusing #45

Open
brancz opened this issue Dec 29, 2020 · 1 comment
Open

Target/Budget configuration confusing #45

brancz opened this issue Dec 29, 2020 · 1 comment

Comments

@brancz
Copy link
Contributor

brancz commented Dec 29, 2020

There are multiple ways to specify a target/budget:

  • latencyburn has latencyTarget and latencyBudget, target being the threshold of "too high duration", budget being the 1- value.
  • errorburn has target being the targeted availability like 99.99 (and a deprecated errorBudget, that works like latencyBudget.
  • errorlatencyburn has target which is like the non-deprecated target of errorburn.

It would be great if all of these could be consistent in their language and use. I'd be more than happy to make the changes once agreed on the details.

I would propose:

Use target everywhere to specify the availability target, as in 99.99 for example. And rename latencyTarget to latencyThreshold. Wdyt?

@metalmatze

@metalmatze
Copy link
Owner

Yes, these have been in a limbo state where we were migrating from one to the other.
target should be the way forward, as can be seen here:
https://github.com/metalmatze/slo-libsonnet/blob/master/slo-libsonnet/error-burn.libsonnet#L12-L16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants