Björn Rabenstein

Changed title according to my hypothesis. And also raised to P1 because this seems to affect every range selector with `@` if used in a range query.

Thank you very much. I'll put #13504 on my review list and will try to get to it ASAP.

Maybe I'm missing something, but isn't that what the `for` clause is for in alerting rules? (I'm sure you thought about it already, but could you explain for everybody why...

Very generally, I'm deeply concerned about implementing (the beginnings of) another expression language inside of PromQL. Can't we do better and utilize existing PromQL syntax for it? Brainstorming: Maybe `streak`...

Thanks for the explanation. I still think implementing "yet another expression language" (YAEL) should be avoided if at all possible. What do you think about my suggestion [above](https://github.com/prometheus/prometheus/pull/12063#issuecomment-1462037343)? Doesn't that...

Allowing comparison operators on range vectors will be a fairly invasive change of PromQL. Unfortunately, even if we decided now to do it, it will take some time to make...

Thanks for the illustrated example. That helps a lot. From the discussion above, I assumed you would like `streak((some_metric{label="value"} > bool 10)[5m:15s])` to return 4 (for the length of the...

Maybe I'm still misunderstanding your use case, but here is my train of thought: Let's come back to your original alerting condition from #12062, namely "to alert if the spike...

I think you can increase the accuracy by reducing the sampling interval of the subquery. I'm very reluctant to add a dedicated function for a fairly specific use case if...

The work-around query you described in #12062 contained a subquery within a subquery. Plus it didn't catch certain conditions, as you described. The work-around query I suggested above only contains...