Julius Volz

Thanks for the pointers! For now I'm pretty happy with how it's working and hope to avoid diving deeper into the search rabbit hole, but going to stay tuned :)

@aanthony1243 Coming here from your comment on https://github.com/influxdata/flux/issues/1045... Questions/remarks on this proposal: - For PromQL binops, this would need to support non-existent `on` columns (if one side has a column...

Makes sense. It's interesting to note that so far, comparison operators have applied to sample values, which in classic histograms would have been the bucket counts and not the bucket...

I don't know yet which syntax I prefer, but I think I'd want to have two operators. When it's a word like `trim`, I'll have trouble remembering which way it...

> The `or` operator is the only exception to that, but that's only because that is basically its entire purpose. Just to add and clarify: I was talking about vector-to-vector...

> and strictly require the histogram to be first and the float (from vector or scalar) to be second. Since we currently allow `42 > my_vector`, it would seem odd...

I might at some point and often do, but at the moment I'm several layers of yak shaving deep into a side project of a side project and didn't immediately...

Not objecting to being able to silence on it, but to the statement that that is the primary purpose of the generatorURL :) My intent when sending this field to...

> Does this functionality exist in some other way? Being able to silence based on the source of the alert would be really useful. At least in many cases you...

I'll take a look - it's been a while and I think there is going to be a bunch more PromQL stuff that would need to be updated by now...