Julien Duchesne 8855c2e626 Add prometheus_tsdb_clean_start metric (#8824) ... Add cleanup of the lockfile when the db is cleanly closed The metric describes the status of the lockfile on startup 0: Already existed 1: Did not exist -1: Disabled Therefore, if the min value over time of this metric is 0, that means that executions have exited uncleanly We can then use that metric to have a much lower threshold on the crashlooping alert: If the metric exists and it has been zero, two restarts is enough to trigger the alarm If it does not exist (old prom version for example), the current five restarts threshold remains Signed-off-by: Julien Duchesne <julien.duchesne@grafana.com> * Change metric name + set unset value to -1 Signed-off-by: Julien Duchesne <julien.duchesne@grafana.com> * Only check the last value of the clean start alert Signed-off-by: Julien Duchesne <julien.duchesne@grafana.com> * Fix test + nit Signed-off-by: Julien Duchesne <julien.duchesne@grafana.com>		2021-06-16 15:03:02 +05:30
..
examples	Switched to go-kit/log	2021-06-11 12:28:36 -04:00
images	update redirected url	2021-04-14 13:54:40 +08:00
prometheus-mixin	Add prometheus_tsdb_clean_start metric (#8824)	2021-06-16 15:03:02 +05:30
internal_architecture.md	Rename default branch to main	2021-02-22 20:28:02 +01:00