You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
There are multiple ways to specify a target/budget:
latencyburn
haslatencyTarget
andlatencyBudget
, target being the threshold of "too high duration", budget being the 1- value.errorburn
hastarget
being the targeted availability like99.99
(and a deprecatederrorBudget
, that works likelatencyBudget
.errorlatencyburn
hastarget
which is like the non-deprecatedtarget
oferrorburn
.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 in99.99
for example. And renamelatencyTarget
tolatencyThreshold
. Wdyt?@metalmatze
The text was updated successfully, but these errors were encountered: