From a57f125c672190e9967ef3112ea21ea22d5a52fc Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Wed, 13 Dec 2023 23:06:46 +0200 Subject: [PATCH] docs/Single-server-VictoriaMetrics.md: cross-link HA docs with the corresponding chapter at vmauth docs --- docs/README.md | 7 ++++--- docs/Single-server-VictoriaMetrics.md | 7 ++++--- 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/docs/README.md b/docs/README.md index 5916e2343..518541efb 100644 --- a/docs/README.md +++ b/docs/README.md @@ -1725,9 +1725,10 @@ See also [resource usage limits at VictoriaMetrics cluster](https://docs.victori The general approach for achieving high availability is the following: -- to run two identically configured VictoriaMetrics instances in distinct datacenters (availability zones) -- to store the collected data simultaneously into these instances via [vmagent](https://docs.victoriametrics.com/vmagent.html) or Prometheus -- to query the first VictoriaMetrics instance and to fail over to the second instance when the first instance becomes temporarily unavailable. +- To run two identically configured VictoriaMetrics instances in distinct datacenters (availability zones); +- To store the collected data simultaneously into these instances via [vmagent](https://docs.victoriametrics.com/vmagent.html) or Prometheus. +- To query the first VictoriaMetrics instance and to fail over to the second instance when the first instance becomes temporarily unavailable. + This can be done via [vmauth](https://docs.victoriametrics.com/vmauth.html) according to [these docs](https://docs.victoriametrics.com/vmauth.html#high-availability). Such a setup guarantees that the collected data isn't lost when one of VictoriaMetrics instance becomes unavailable. The collected data continues to be written to the available VictoriaMetrics instance, so it should be available for querying. diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index 16e54fe38..8b9d70f0a 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -1733,9 +1733,10 @@ See also [resource usage limits at VictoriaMetrics cluster](https://docs.victori The general approach for achieving high availability is the following: -- to run two identically configured VictoriaMetrics instances in distinct datacenters (availability zones) -- to store the collected data simultaneously into these instances via [vmagent](https://docs.victoriametrics.com/vmagent.html) or Prometheus -- to query the first VictoriaMetrics instance and to fail over to the second instance when the first instance becomes temporarily unavailable. +- To run two identically configured VictoriaMetrics instances in distinct datacenters (availability zones); +- To store the collected data simultaneously into these instances via [vmagent](https://docs.victoriametrics.com/vmagent.html) or Prometheus. +- To query the first VictoriaMetrics instance and to fail over to the second instance when the first instance becomes temporarily unavailable. + This can be done via [vmauth](https://docs.victoriametrics.com/vmauth.html) according to [these docs](https://docs.victoriametrics.com/vmauth.html#high-availability). Such a setup guarantees that the collected data isn't lost when one of VictoriaMetrics instance becomes unavailable. The collected data continues to be written to the available VictoriaMetrics instance, so it should be available for querying.