Thanks for the pointer Brian.
>From what you suggested; I updated my query to include `service` rather
than `job` to cover the different values (representing either redis service
on each `instance`), however I'm still not getting the results I expect:
query:
redis_cluster_known_nodes != on (instance, service, group) count by
(instance, service, group) (up{service=~"exporter-redis-.*"})
result:
{group="group-a", instance="node-1", service="exporter-redis-6379"} 10
{group="group-a", instance="node-1", service="exporter-redis-6380"} 10
{group="group-a", instance="node-2", service="exporter-redis-6379"} 11
{group="group-a", instance="node-2", service="exporter-redis-6380"} 16
{group="group-a", instance="node-3", service="exporter-redis-6379"} 16
{group="group-a", instance="node-3", service="exporter-redis-6380"} 16
{group="group-a", instance="node-4", service="exporter-redis-6379"} 16
{group="group-a", instance="node-4", service="exporter-redis-6380"} 16
{group="group-a", instance="node-5", service="exporter-redis-6379"} 16
{group="group-a", instance="node-5", service="exporter-redis-6380"} 16
I would expect only those who's count is != 10 be included in the result.
Here's a metric sample of those used in the query:
```
up{group="group-a", instance="node-1", job="redis-cluster",
service="exporter-redis-6379", team="sre"} 1
up{group="group-a", instance="node-1", job="redis-cluster",
service="exporter-redis-6380", team="sre"} 1
up{group="group-a", instance="node-2", job="redis-cluster",
service="exporter-redis-6379"} 1
up{group="group-a", instance="node-2", job="redis-cluster",
service="exporter-redis-6380"} 1
up{group="group-a", instance="node-3", job="redis-cluster",
service="exporter-redis-6379"} 1
up{group="group-a", instance="node-3", job="redis-cluster",
service="exporter-redis-6380"} 1
up{group="group-a", instance="node-4", job="redis-cluster",
service="exporter-redis-6379"} 1
up{group="group-a", instance="node-4", job="redis-cluster",
service="exporter-redis-6380"} 1
up{group="group-a", instance="node-5", job="redis-cluster",
service="exporter-redis-6379"} 1
up{group="group-a", instance="node-5", job="redis-cluster",
service="exporter-redis-6380"} 1
redis_cluster_known_nodes{group="group-a", instance="node-1",
job="redis-cluster", service="exporter-redis-6379", team="sre"} 10
redis_cluster_known_nodes{group="group-a", instance="node-1",
job="redis-cluster", service="exporter-redis-6380", team="sre"} 10
redis_cluster_known_nodes{group="group-a", instance="node-2",
job="redis-cluster", service="exporter-redis-6379"} 11
redis_cluster_known_nodes{group="group-a", instance="node-2",
job="redis-cluster", service="exporter-redis-6380"} 16
redis_cluster_known_nodes{group="group-a", instance="node-3",
job="redis-cluster", service="exporter-redis-6379"} 16
redis_cluster_known_nodes{group="group-a", instance="node-3",
job="redis-cluster", service="exporter-redis-6380"} 16
redis_cluster_known_nodes{group="group-a", instance="node-4",
job="redis-cluster", service="exporter-redis-6379"} 16
redis_cluster_known_nodes{group="group-a", instance="node-4",
job="redis-cluster", service="exporter-redis-6380"} 16
redis_cluster_known_nodes{group="group-a", instance="node-5",
job="redis-cluster", service="exporter-redis-6379"} 16
redis_cluster_known_nodes{group="group-a", instance="node-5",
job="redis-cluster", service="exporter-redis-6380"} 16
```
On Thursday, October 13, 2022 at 9:17:55 AM UTC-4 Brian Candler wrote:
> Sorry, second to last sentence was unclear. What I meant was:
>
>
> *If the LHS vector contains N metrics with a particular value of the
> "group" label, which correspond to exactly 1 metric on the RHS with the
> matching label value, or vice versa, then you can use N:1 matching.*
> On Thursday, 13 October 2022 at 14:13:42 UTC+1 Brian Candler wrote:
>
>> > Is it possible to have one side of a query limit the results of another
>> part of the same query?
>>
>> Yes, but it depends on exactly what you mean. The details are here:
>> https://prometheus.io/docs/prometheus/latest/querying/operators/
>> It depends on whether you can construct vectors for the LHS and RHS which
>> have corresponding labels.
>>
>> If you can give some specific examples of the metrics themselves -
>> including all their labels - then we can see whether it's possible to do
>> what you want in PromQL. Right now the requirements are unclear.
>>
>>
>> *> redis_cluster_known_nodes !=
>> scalar(count(up{service=~"redis-exporter"}))*
>> >
>> > The shared label value would be something like, *group="cluster-a" *and
>> should not evaluate metrics where *group="cluster-b"*
>>
>> You need to arrange both LHS and RHS to have some corresponding labels
>> before you can combine them with any operator such as !=. The RHS has no
>> "group" label at the moment, in fact it's not even a vector, but you could
>> do:
>>
>> count by (group) (up{service="redis-exporter"})
>>
>> Then, assuming that redis_cluster_known_nodes also has a "group" label,
>> you can do:
>>
>> redis_cluster_known_nodes != on (group) count by (group)
>> (up{service="redis-exporter"})
>>
>> This will work as long as the LHS and RHS both have exactly *one* metric
>> for a given value of the "group" label.
>>
>> If the LHS has N values of "group" for 1 on the RHS, or vice versa, then
>> you can use N:1 matching as described in the documentation ("group left" or
>> "group right").
>>
>> If there are multiple matches on both LHS and RHS for the same value of
>> group, then the query will fail. You will have to include some more labels
>> in the on(...) list to get a unique match.
>>
>
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to prometheus-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/b7d753d6-d9e1-4a7e-8a9d-ff756c1eb531n%40googlegroups.com.
