From 9c5f9984386de3906d54693efa47ff431c5fe036 Mon Sep 17 00:00:00 2001 From: Howie Date: Mon, 30 May 2022 14:16:07 +0800 Subject: [PATCH] fix: docs (#2658) Signed-off-by: lihaowei --- app/vmalert/README.md | 2 +- docs/vmalert.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/app/vmalert/README.md b/app/vmalert/README.md index 3e15ca122..3db89ac37 100644 --- a/app/vmalert/README.md +++ b/app/vmalert/README.md @@ -68,7 +68,7 @@ Then configure `vmalert` accordingly: -external.label=replica=a # Multiple external labels may be set ``` -Note there's a separate `remoteRead.url` to allow writing results of +Note there's a separate `remoteWrite.url` to allow writing results of alerting/recording rules into a different storage than the initial data that's queried. This allows using `vmalert` to aggregate data from a short-term, high-frequency, high-cardinality storage into a long-term storage with diff --git a/docs/vmalert.md b/docs/vmalert.md index ebb337ff1..208552a3f 100644 --- a/docs/vmalert.md +++ b/docs/vmalert.md @@ -72,7 +72,7 @@ Then configure `vmalert` accordingly: -external.label=replica=a # Multiple external labels may be set ``` -Note there's a separate `remoteRead.url` to allow writing results of +Note there's a separate `remoteWrite.url` to allow writing results of alerting/recording rules into a different storage than the initial data that's queried. This allows using `vmalert` to aggregate data from a short-term, high-frequency, high-cardinality storage into a long-term storage with @@ -529,7 +529,7 @@ There are following non-required `replay` flags: (rules which depend on each other) rules. It is expected, that remote storage will be able to persist previously accepted data during the delay, so data will be available for the subsequent queries. Keep it equal or bigger than `-remoteWrite.flushInterval`. -* `replay.disableProgressBar` - whether to disable progress bar which shows progress work. +* `-replay.disableProgressBar` - whether to disable progress bar which shows progress work. Progress bar may generate a lot of log records, which is not formatted as standard VictoriaMetrics logger. It could break logs parsing by external system and generate additional load on it.