From 195b9386cb0fc2caec7e80ab9cf48a371d4ff625 Mon Sep 17 00:00:00 2001 From: Zakhar Bessarab <z.bessarab@victoriametrics.com> Date: Tue, 11 Jul 2023 13:19:05 +0400 Subject: [PATCH] doc: fix image src after b67bd156 (#4612) Followup for https://github.com/VictoriaMetrics/VictoriaMetrics/commit/b67bd156d59775d93251f0f00dabb76766d9b8c0 Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> --- docs/keyConcepts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/keyConcepts.md b/docs/keyConcepts.md index b7de39dec5..f8191803e3 100644 --- a/docs/keyConcepts.md +++ b/docs/keyConcepts.md @@ -751,12 +751,12 @@ But this flag avoids non-consistent results due to the fact that only part of th Here is an illustration of a potential problem when `search.latencyOffset` is set to zero: -<img src="keyConcepts_withoutLatencyOffset.png"> +<img src="keyConcepts_without_LatencyOffset.png"> When this flag is set, the VM will return the last metric value collected before the `search.latencyOffset` duration throughout the `search.latencyOffset` duration: -<img src="keyConcepts_withLatencyOffset.png"> +<img src="keyConcepts_with_LatencyOffset.png"> It can be overridden on per-query basis via `latency_offset` arg.