You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

James Ravn e15d8c5802 reload: copy state on both name and labels (#5368) ... * reload: copy state on both name and labels Fix https://github.com/prometheus/prometheus/issues/5193 Using just name causes the linked issue - if new rules are inserted with the same name (but different labels), the reordering will cause stale markers to be inserted in the next eval for all shifted rules, despite them not being stale. Ideally we want to avoid stale markers for time series that still exist in the new rules, with name and labels being the unique identifer. This change adds labels to the internal map when copying the old rule data to the new rule data. This prevents the problem of staling rules that simply shifted order. If labels change, it is a new time series and the old series will stale regardless. So it should be safe to always match on name and labels when copying state. Signed-off-by: James Ravn <james@r-vn.org>		6 years ago
..
fixtures	…
alerting.go	*: use latest release of staticcheck (#5057)	6 years ago
alerting_test.go	*: apply gofmt -s	6 years ago
manager.go	reload: copy state on both name and labels (#5368)	6 years ago
manager_test.go	reload: copy state on both name and labels (#5368)	6 years ago
recording.go	…
recording_test.go	…