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
{{ message }}
This repository has been archived by the owner on Nov 29, 2024. It is now read-only.
I was also thinking about this recently.
We had a situation where the average latency of one broker was consistently >1000ms. This led to the performance index just omitting that broker's time series, because it resulted in NaN since the dividend was 0.
The line of the performance index was still a straight 100%, just with the values from the "bad" broker missing. That is pretty useless I feel.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I don't think this query makes sense. It always returns 100%, even on a stricter bucket like
le="5"
.I think a more appropriate query would be:
The text was updated successfully, but these errors were encountered: