mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-23 12:31:07 +01:00
Add description for retention and how it works (#297)
This commit is contained in:
parent
8074c10590
commit
1a3626bbe1
@ -95,6 +95,7 @@ Cluster version is available [here](https://github.com/VictoriaMetrics/VictoriaM
|
|||||||
- [Federation](#federation)
|
- [Federation](#federation)
|
||||||
- [Capacity planning](#capacity-planning)
|
- [Capacity planning](#capacity-planning)
|
||||||
- [High availability](#high-availability)
|
- [High availability](#high-availability)
|
||||||
|
- [Retention](#retention)
|
||||||
- [Multiple retentions](#multiple-retentions)
|
- [Multiple retentions](#multiple-retentions)
|
||||||
- [Downsampling](#downsampling)
|
- [Downsampling](#downsampling)
|
||||||
- [Multi-tenancy](#multi-tenancy)
|
- [Multi-tenancy](#multi-tenancy)
|
||||||
@ -700,6 +701,12 @@ kill -HUP `pidof prometheus`
|
|||||||
If you have Prometheus HA pairs with replicas `r1` and `r2` in each pair, then configure each `r1`
|
If you have Prometheus HA pairs with replicas `r1` and `r2` in each pair, then configure each `r1`
|
||||||
to write data to `victoriametrics-addr-1`, while each `r2` should write data to `victoriametrics-addr-2`.
|
to write data to `victoriametrics-addr-1`, while each `r2` should write data to `victoriametrics-addr-2`.
|
||||||
|
|
||||||
|
### Retention
|
||||||
|
|
||||||
|
Metrics is stored in directories per month. Retention occurs on the first day of the new month.
|
||||||
|
In order to keep data according to `retentionPeriod` max disk usage is going to be `retentionPeriod` + 1 month.
|
||||||
|
For example if you have `retentionPeriod` set to 1, january data will be deleted at March 1st.
|
||||||
|
|
||||||
|
|
||||||
### Multiple retentions
|
### Multiple retentions
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user