beorn7 2628320292 promql: Fix when to emit a HistogramCounterResetCollisionWarning ...

So far, we emitted a `HistogramCounterResetCollisionWarning` when
encountering conflicting counter resets in the calculation of (i)rate
and friends. We even tested for that. However, in the rate
calculation, we are not interested in those collisions. They are
actually expected.

On the other hand, we did not warn about those collisions when doing a
`sum` aggregation, where such a warning would be appropriate.

This commit removes the warning in the former case and adds it in the
latter. Sadly, we cannot really test this as we still remove the
counter reset hint for the first sample in a chunk. (And that's the
only sample where we could get a `NotCounterReset` hint.)

Signed-off-by: beorn7 <beorn@grafana.com>

2025-09-03 18:00:03 +02:00

..

annotations.go

promql: Fix when to emit a HistogramCounterResetCollisionWarning

2025-09-03 18:00:03 +02:00