prometheus/wal
beorn7 90a7612df3 Make objectives of Summaries explicit
With the next release of client_golang, Summaries will not have
objectives by default.

As it turns out, for prometheus_tsdb_head_gc_duration_seconds and
prometheus_tsdb_wal_truncate_duration_seconds, the objective-less
default makes more sense then the current default.

To make sure we do the right thing before and after the upcoming
release of client_golang, I have set the objectives explicitly
wherever that was not the case so far:

- prometheus_tsdb_head_gc_duration_seconds and
  prometheus_tsdb_wal_truncate_duration_seconds now have no objectives
  explicitly.
- prometheus_tsdb_wal_fsync_duration_seconds now explicitly uses the
  previous default objectives.

Signed-off-by: beorn7 <beorn@grafana.com>
2019-06-14 14:17:24 +02:00
..
live_reader.go wal: Add _total suffix as metric is a counter 2019-06-05 09:24:25 +02:00
reader.go LiveReader can get into an infinite loop on corrupt WALs. (#524) 2019-02-19 14:33:57 +00:00
reader_test.go wal: Replace promauto with injected registry 2019-06-03 12:29:52 +02:00
wal.go Make objectives of Summaries explicit 2019-06-14 14:17:24 +02:00
wal_test.go Always create a new clean segment when starting the WAL. (#608) 2019-05-24 19:33:27 +01:00