Thanks for the info, yeah I was hoping to do this all on the alertmanager 
side if I could. We use a lot of rules from this upstream and I was hoping 
to not have to modify them just to get this to 
work https://github.com/kubernetes-monitoring/kubernetes-mixin

On Sunday, November 1, 2020 at 3:39:52 PM UTC-5 [email protected] wrote:

> If you have one timeseries kube_pod_container_status_restarts_total, and 
> another timeseries which has a 'team_name' label, and there is some common 
> label between the two (pod id?), then you can join them in your alerting 
> rule expr so that the PromQL result includes the 'team_name' label.
>
> For more info:
> https://www.robustperception.io/how-to-have-labels-for-machine-roles
> https://www.robustperception.io/exposing-the-software-version-to-prometheus
> https://www.robustperception.io/left-joins-in-promql
>
> https://prometheus.io/docs/prometheus/latest/querying/operators/#many-to-one-and-one-to-many-vector-matches
>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/8dbc6b13-f901-4a54-a903-f5d2b5f91da8n%40googlegroups.com.

Reply via email to