VictoriaMetrics/app/vmalert/notifier
Roman Khavronenko e0f21d6000
vmalert: correctly calculate alert ID including extra labels (#1734)
Previously, ID for alert entity was generated without alertname or groupname.
This led to collision, when multiple alerting rules within the same group
producing same labelsets. E.g. expr: `sum(metric1) by (job) > 0` and
expr: `sum(metric2) by (job) > 0` could result into same labelset `job: "job"`.

The issue affects only UI and Web API parts of vmalert, because alert ID is used
only for displaying and finding active alerts. It does not affect state restore
procedure, since this label was added right before pushing to remote storage.

The change now adds all extra labels right after receiving response from the datasource.
And removes adding extra labels before pushing to remote storage.

Additionally, change introduces a new flag `Restored` which will be displayed in UI
for alerts which have been restored from remote storage on restart.
2021-10-22 12:31:35 +03:00
..
alert_test.go vmalert: support rules backfilling (aka replay) (#1358) 2021-06-09 12:30:54 +03:00
alert.go vmalert: correctly calculate alert ID including extra labels (#1734) 2021-10-22 12:31:35 +03:00
alertmanager_request.qtpl Support of custom URL path for alert (#560) 2020-06-21 16:33:58 +03:00
alertmanager_request.qtpl.go Support of custom URL path for alert (#560) 2020-06-21 16:33:58 +03:00
alertmanager_test.go Vmalert metrics update (#1580) 2021-09-01 12:19:34 +03:00
alertmanager.go Vmalert metrics update (#1580) 2021-09-01 12:19:34 +03:00
init.go app/vmalert: typo fix in descriptions for notifier.basicAuth.username and notifier.basicAuth.password command-line flags 2020-12-24 12:49:40 +02:00
notifier.go Vmalert metrics update (#1580) 2021-09-01 12:19:34 +03:00
package_test.go Support of custom URL path for alert (#560) 2020-06-21 16:33:58 +03:00
template_func.go vmalert: support rules backfilling (aka replay) (#1358) 2021-06-09 12:30:54 +03:00