-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
lib/streamaggr: added rate and rate_avg output #6243
Conversation
5ebc793
to
1944c62
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changelog line is missing :)
399aed9
to
b66106d
Compare
dc642e3
to
4cca78b
Compare
29ebf00
to
e082d3e
Compare
@hagen1778 tested on a sandbox, resource usage for rate is almost the same as for increase |
bbc916d
to
6843e11
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@AndrewChubatiuk would you mind checking 8b10330 ? If you agree with changes then we can merge this pr. |
* rename `rate` to `rate_sum` for sake of consistency * rename `startTimestamp` to `prevTimestamp` for clarity * capture number of unique series for `rate_avg` calculation after stale series were removed Signed-off-by: hagen1778 <roman@victoriametrics.com>
Signed-off-by: hagen1778 <roman@victoriametrics.com>
Added `rate` and `rate_avg` output Resource usage is the same as for increase output, tested on a benchmark --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9c3d44c)
Describe Your Changes
Added
rate
andrate_avg
outputResource usage is the same as for increase output, tested on a benchmark
Checklist
The following checks are mandatory: