You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though we didn't have a big need of going way back, it might be useful for some more high-level data like what flight_recorder or an SLI runner could give us.
--
Regarding disk, at the moment we're at a constant 20% utilization:
My guess is that going up in terms of retention would proportionally make this grow.
The text was updated successfully, but these errors were encountered:
cirocosta
changed the title
metrics: increase prometheus retentio
metrics: increase prometheus n
Jun 17, 2019
cirocosta
changed the title
metrics: increase prometheus n
metrics: increase prometheus retetion
Jun 17, 2019
cirocosta
changed the title
metrics: increase prometheus retetion
metrics: increase prometheus retention
Jun 17, 2019
Hey,
At the moment, the
metrics
Prometheus server is configured with a retention policy that allows us to store only 15d of data:Which, having a default of
15d
when0
(see https://prometheus.io/docs/prometheus/latest/storage/), means that we end up being able to go back a max of 15d.Even though we didn't have a big need of going way back, it might be useful for some more high-level data like what
flight_recorder
or an SLI runner could give us.--
Regarding disk, at the moment we're at a constant 20% utilization:
My guess is that going up in terms of retention would proportionally make this grow.
The text was updated successfully, but these errors were encountered: