On Tuesday, 7 March 2023 at 16:47:34 UTC Nick Carlton wrote: I suppose that if there are for example no nodes that are enabled but not available, would Prometheus actually know the pools that don’t match this because they theory they would not be returned at all in the query, nevermind the count by.
That's what I mean by having a stable metric, one which is always present, that you can combine with "or" or "unless". If you just care about the 'instance' label, then the "up" metric can perform this purpose, which is created by Prometheus for every target it attempts to scrape. This allows you to alert on the *absence* of a particular metric from any target, since you know which targets are being scraped: https://www.robustperception.io/absent-alerting-for-scraped-metrics/ In your case, you need to identify a particular metric which is always present for each load balancer pool (or whatever it is you're monitoring) regardless of its state. But no, sorry, I am not going to write this for you :-) It would involve digging down too far into the details of these F5 metrics than I care to. Good luck! -- 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/4b1199ef-4dc5-4479-b04d-28d372ea0dd7n%40googlegroups.com.
