From 2c41f25fb8f33a0678e97287cf58efc8ec4dd01c Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Wed, 1 Dec 2021 12:48:30 +0200 Subject: [PATCH] README.md: add a link to https://docs.victoriametrics.com/guides/guide-vmcluster-multiple-retention-setup.html for multi-retention setups --- README.md | 3 ++- docs/README.md | 3 ++- docs/Single-server-VictoriaMetrics.md | 3 ++- 3 files changed, 6 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 3292a46ba..a767fdd7e 100644 --- a/README.md +++ b/README.md @@ -1148,7 +1148,7 @@ Older data is eventually deleted during [background merge](https://medium.com/@v ## 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` * `-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, 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). +See [these docs](https://docs.victoriametrics.com/guides/guide-vmcluster-multiple-retention-setup.html) for multi-retention setup details. ## Downsampling diff --git a/docs/README.md b/docs/README.md index 3292a46ba..a767fdd7e 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1148,7 +1148,7 @@ Older data is eventually deleted during [background merge](https://medium.com/@v ## 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` * `-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, 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). +See [these docs](https://docs.victoriametrics.com/guides/guide-vmcluster-multiple-retention-setup.html) for multi-retention setup details. ## Downsampling diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index 2a253f638..5728a1fd6 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -1152,7 +1152,7 @@ Older data is eventually deleted during [background merge](https://medium.com/@v ## 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` * `-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, 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). +See [these docs](https://docs.victoriametrics.com/guides/guide-vmcluster-multiple-retention-setup.html) for multi-retention setup details. ## Downsampling