Björn Rabenstein

My apologies. I'm caught between medical procedures, vacations, and a ton of very urgent tasks. I tried to explain [above](https://github.com/prometheus/prometheus/pull/15809#discussion_r2155559981) what the remaining problem is. For a qualified suggestion how...

Another option would be to leave the current behavior (including using the global registry) in place for just that one remote-read case so that we can thoroughly test and merge...

Just a note: This is still on my list. I'm overwhelmed with tasks of various priorities. I'll come to this eventually but cannot provide an ETA right now (but of...

This looks super promising (modulo the bugs, of course :). However, with the intense review and debugging activity by @krajorama (and given my growing review backlog), I'll withdraw from my...

🤔 I think this is more about creating a formal spec from all the not-so-formal documentation, checked against the actual behavior of the implementation. I would say that the current...

Hello from the bug scrub! We had some discussion about this. Creating a formal spec seems mostly relevant for implementers of alternative PromQL engines. So the question is how often...

We discussed this at the dev-summit. @bwplotka will summarize the result here. 😁

See https://github.com/prometheus/node_exporter/pull/1448/files#r1741178030 for the normalization for the number of cores.

So this is a makeshift setup: My laptop with 16 "11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz" cores, running the Promtheus unit tests, using the _original_ query from the mixin....

And in case that was misunderstood: The query is meant to go up to 1 for the _stacked_ result. So on a 16 core system, every single number in the...