New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global external_labels for vmalert #622
Comments
Hi @ofen! |
Hi @hagen1778 , I assume global for each configured file. In our current set-up we have vmalert in each cluster (to have separate configuration per cluster) that processing recording rules on remote VictoriaMetrics DB and send it back after processing. We are adding cluster specific labels (name, type, location) to each recording rules but we would like to have ability to apply those cluster wide labels per vmalert instead of per rule. |
Also I noticed that Prometheus adding global labels (external_labels) to alerts too (it's useful when you can add labels to know from which cluster you got alert) |
…all rules #622 `external.label` flag supposed to help to distinguish alert or recording rules source in situations when more than one `vmalert` runs for the same datasource or AlertManager.
Please implement ability to set external_labels globally to vmalert (same functionality as in vmagent https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config).
This feature required for adding additional labels (e.g. cluster name, location, ...) to each recording rule.
The text was updated successfully, but these errors were encountered: