When I use a label multiple times in a filter, they are all applied (as though they were implicitly ANDed together).In other words, if I ask for:metric{a=~x, a!=y}I get all the metrics where a=~x AND a!=y.So my question is: should this considered as part of the promql "specification"?
In particular, should a remote read implementation handle repeated matchers in this way?
Ok thanks.(Btw I had read that page and just re-read it again, but don't see anything that mentions multiple selectors.)
On Fri, 10 Aug 2018 at 14:24, Brian Brazil <brian.brazil@robustperception.io> wrote:On 10 August 2018 at 20:02, Henri Dubois-Ferriere <hen...@gmail.com> wrote:When I use a label multiple times in a filter, they are all applied (as though they were implicitly ANDed together).In other words, if I ask for:metric{a=~x, a!=y}I get all the metrics where a=~x AND a!=y.So my question is: should this considered as part of the promql "specification"?Yes, this is part of the spec. See https://prometheus.io/docs/prometheus/latest/querying/basics/#time-series-selectorsIn particular, should a remote read implementation handle repeated matchers in this way?Yes, it should.--Brian Brazil