mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-15 16:30:55 +01:00
4de1b2b74a
To improve compatibility with Prometheus alerting the order of templates processing has changed. Before, vmalert did all labels processing beforehand. It meant all extra labels (such as `alertname`, `alertgroup` or rule labels) were available in templating. All collisions were resolved in favour of extra labels. In Prometheus, only labels from the received metric are available in templating, so no collisions are possible. This change makes vmalert's behaviour similar to Prometheus. For example, consider alerting rule which is triggered by time series with `alertname` label. In vmalert, this label would be overriden by alerting rule's name everywhere: for alert labels, for annotations, etc. In Prometheus, it would be overriden for alert's labels only, but in annotations the original label value would be available. See more details here https://github.com/prometheus/compliance/issues/80 Signed-off-by: hagen1778 <roman@victoriametrics.com> |
||
|---|---|---|
| .. | ||
| testdata | ||
| alert_test.go | ||
| alert.go | ||
| alertmanager_request.qtpl | ||
| alertmanager_request.qtpl.go | ||
| alertmanager_test.go | ||
| alertmanager.go | ||
| config_test.go | ||
| config_watcher_test.go | ||
| config_watcher.go | ||
| config.go | ||
| init.go | ||
| notifier.go | ||
| package_test.go | ||
| template_func.go | ||