Hi there,
I was reading about the functions offered by Prometheus and came across the following:
"Note that when combining
irate() with an
aggregation operator (e.g.
sum())
or a function aggregating over time (any function ending in
_over_time),
always take a
irate() first, then aggregate. Otherwise
irate() cannot detect
counter resets when your target restarts."
In a system that has hierarchical federation, how would aggregation work? For example, let's say I have server A and server B, and server C collects data from A and B. If I want to evaluate a rule that requires aggregating data from servers A and B, would Prometheus compute the sum of rates instead of the rate of sums, so as to defend against counter resets and missing data?
Thanks,
Ilina