Bartlomiej Plotka

Another idea is a CLI tool that will validate different theories per specific PodMonitoring

Hi 👋🏽 Unfortunately all of those recording rules you show lead to broken counters as explained to https://www.robustperception.io/rate-then-sum-never-sum-then-rate/. This is because you use aggregate (see `sum` operation) that will be...

Yup, https://github.com/prometheus/prometheus/pull/14526#pullrequestreview-2209290018 solves it.

We switched a bit our idea to make it super simple, so I assume this is no longer needed.

Also cc @pstibrany as you had strong opinions on iterators behavior on edge cases :hugs:

> That specific requirement is already stated, as it's a seriesset. I think it's not clear enough, so I assume comment does not harm (:

>> Accessing At after some Next more than once. > This is completely valid, as are the subsequent ones. You can call At as many times as you like. I...

Disagree @pstibrany **There should not be something like undefined ideally** Undefined means surprises to me :thinking: Think about cases of bug where a user accidentally use undefined behavior. Suddenly you...

>> Accessing At after some Next more than once. >> Accessing At.Iterator() after some Next more than once. >> Accessing At.Labels() after some Next more that once. > Are you...

> I don't think it's practical to have all iterators behave in the same way for undefined behavior. (Eg. errSeriesSet will need lot of extra code to do all this)...