mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-23 20:37:12 +01:00
README.md: add a link to https://docs.victoriametrics.com/guides/guide-vmcluster-multiple-retention-setup.html for multi-retention setups
This commit is contained in:
parent
0afec0259b
commit
2c41f25fb8
@ -1148,7 +1148,7 @@ Older data is eventually deleted during [background merge](https://medium.com/@v
|
|||||||
|
|
||||||
## Multiple retentions
|
## Multiple retentions
|
||||||
|
|
||||||
Just start multiple VictoriaMetrics instances with distinct values for the following flags:
|
A single instance of VictoriaMetrics supports only a single retention, which can be configured via `-retentionPeriod` command-line flag. If you need multiple retentions, then you may start multiple VictoriaMetrics instances with distinct values for the following flags:
|
||||||
|
|
||||||
* `-retentionPeriod`
|
* `-retentionPeriod`
|
||||||
* `-storageDataPath`, so the data for each retention period is saved in a separate directory
|
* `-storageDataPath`, so the data for each retention period is saved in a separate directory
|
||||||
@ -1157,6 +1157,7 @@ Just start multiple VictoriaMetrics instances with distinct values for the follo
|
|||||||
Then set up [vmauth](https://docs.victoriametrics.com/vmauth.html) in front of VictoriaMetrics instances,
|
Then set up [vmauth](https://docs.victoriametrics.com/vmauth.html) in front of VictoriaMetrics instances,
|
||||||
so it could route requests from particular user to VictoriaMetrics with the desired retention.
|
so it could route requests from particular user to VictoriaMetrics with the desired retention.
|
||||||
The same scheme could be implemented for multiple tenants in [VictoriaMetrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html).
|
The same scheme could be implemented for multiple tenants in [VictoriaMetrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html).
|
||||||
|
See [these docs](https://docs.victoriametrics.com/guides/guide-vmcluster-multiple-retention-setup.html) for multi-retention setup details.
|
||||||
|
|
||||||
|
|
||||||
## Downsampling
|
## Downsampling
|
||||||
|
@ -1148,7 +1148,7 @@ Older data is eventually deleted during [background merge](https://medium.com/@v
|
|||||||
|
|
||||||
## Multiple retentions
|
## Multiple retentions
|
||||||
|
|
||||||
Just start multiple VictoriaMetrics instances with distinct values for the following flags:
|
A single instance of VictoriaMetrics supports only a single retention, which can be configured via `-retentionPeriod` command-line flag. If you need multiple retentions, then you may start multiple VictoriaMetrics instances with distinct values for the following flags:
|
||||||
|
|
||||||
* `-retentionPeriod`
|
* `-retentionPeriod`
|
||||||
* `-storageDataPath`, so the data for each retention period is saved in a separate directory
|
* `-storageDataPath`, so the data for each retention period is saved in a separate directory
|
||||||
@ -1157,6 +1157,7 @@ Just start multiple VictoriaMetrics instances with distinct values for the follo
|
|||||||
Then set up [vmauth](https://docs.victoriametrics.com/vmauth.html) in front of VictoriaMetrics instances,
|
Then set up [vmauth](https://docs.victoriametrics.com/vmauth.html) in front of VictoriaMetrics instances,
|
||||||
so it could route requests from particular user to VictoriaMetrics with the desired retention.
|
so it could route requests from particular user to VictoriaMetrics with the desired retention.
|
||||||
The same scheme could be implemented for multiple tenants in [VictoriaMetrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html).
|
The same scheme could be implemented for multiple tenants in [VictoriaMetrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html).
|
||||||
|
See [these docs](https://docs.victoriametrics.com/guides/guide-vmcluster-multiple-retention-setup.html) for multi-retention setup details.
|
||||||
|
|
||||||
|
|
||||||
## Downsampling
|
## Downsampling
|
||||||
|
@ -1152,7 +1152,7 @@ Older data is eventually deleted during [background merge](https://medium.com/@v
|
|||||||
|
|
||||||
## Multiple retentions
|
## Multiple retentions
|
||||||
|
|
||||||
Just start multiple VictoriaMetrics instances with distinct values for the following flags:
|
A single instance of VictoriaMetrics supports only a single retention, which can be configured via `-retentionPeriod` command-line flag. If you need multiple retentions, then you may start multiple VictoriaMetrics instances with distinct values for the following flags:
|
||||||
|
|
||||||
* `-retentionPeriod`
|
* `-retentionPeriod`
|
||||||
* `-storageDataPath`, so the data for each retention period is saved in a separate directory
|
* `-storageDataPath`, so the data for each retention period is saved in a separate directory
|
||||||
@ -1161,6 +1161,7 @@ Just start multiple VictoriaMetrics instances with distinct values for the follo
|
|||||||
Then set up [vmauth](https://docs.victoriametrics.com/vmauth.html) in front of VictoriaMetrics instances,
|
Then set up [vmauth](https://docs.victoriametrics.com/vmauth.html) in front of VictoriaMetrics instances,
|
||||||
so it could route requests from particular user to VictoriaMetrics with the desired retention.
|
so it could route requests from particular user to VictoriaMetrics with the desired retention.
|
||||||
The same scheme could be implemented for multiple tenants in [VictoriaMetrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html).
|
The same scheme could be implemented for multiple tenants in [VictoriaMetrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html).
|
||||||
|
See [these docs](https://docs.victoriametrics.com/guides/guide-vmcluster-multiple-retention-setup.html) for multi-retention setup details.
|
||||||
|
|
||||||
|
|
||||||
## Downsampling
|
## Downsampling
|
||||||
|
Loading…
Reference in New Issue
Block a user