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
..
vmagent	lib/httpserver: expose command-line flags at /flags page	2021-10-20 00:46:54 +03:00
vmalert	vmalert: correctly calculate alert ID including extra labels (#1734)	2021-10-22 12:31:35 +03:00
vmauth	app/vmauth: fix metric name prefixes: vmagent -> vmauth	2021-10-19 15:30:16 +03:00
vmbackup	app/{vmbackup,vmrestore}: switch from gcs://... to gs://... urls for backups to GCS	2021-09-29 12:12:37 +03:00
vmbackupmanager	app/{vmbackup,vmrestore}: switch from gcs://... to gs://... urls for backups to GCS	2021-09-29 12:12:37 +03:00
vmctl	vmctl: follow-up after 95d1d38595 (#1718)	2021-10-18 15:19:01 +03:00
vmgateway	docs/{vmgateway,vmbackupmanager}: mention that enterprise binaries are free for download and evaluation	2021-08-27 14:53:48 +03:00
vminsert	app/{vminsert,vmstorage}: follow-up after a171916ef5	2021-10-08 14:09:51 +03:00
vmrestore	app/{vmbackup,vmrestore}: switch from gcs://... to gs://... urls for backups to GCS	2021-09-29 12:12:37 +03:00
vmselect	vmui: query history (#1732)	2021-10-22 12:29:27 +03:00
vmstorage	app/{vminsert,vmstorage}: follow-up after a171916ef5	2021-10-08 14:09:51 +03:00
vmui	vmui: query history (#1732)	2021-10-22 12:29:27 +03:00