Rate as a Streaming Aggregation

[rbizos]

Is your question request related to a specific component?

vmagent

Describe the question in detail

I'm trying to replicate our current Prometheus recording rules with vmagent to make a cheaper drop-in replacement of our Prometheus. So far I have great results (the total is absolutely a game changer).
I've seen that the documentation indicates to use increase and divide by the time window at query time. I'm not sure to understand why its unsafe to aggregate afterwards as the only difference is a common factor.

Would it be acceptable to implement the rate ? I'm willing to do it as well.

Troubleshooting docs

• General - https://docs.victoriametrics.com/troubleshooting/
• vmagent - https://docs.victoriametrics.com/vmagent/#troubleshooting
• vmalert - https://docs.victoriametrics.com/vmalert/#troubleshooting

[Haleygo]

dup with #5641

[rbizos]

Oh sorry, I missed it thanks !

[Haleygo]

Hello @rbizos ,

I'm not sure to understand why its unsafe to aggregate afterwards as the only difference is a common factor.

About this statement "Please note, opposite to rate, increase aggregations can be
combined safely afterwards", I think it's wrong and should be removed in #6207.

[AndrewChubatiuk]

hey @rbizos
rate_sum and rate_avg outputs are available in v1.102.0-rc1