From 527bee4b1e114a98d7a727da763fb6c5b39addc1 Mon Sep 17 00:00:00 2001 From: Denys Holius <5650611+denisgolius@users.noreply.github.com> Date: Thu, 27 Jan 2022 20:35:16 +0200 Subject: [PATCH] FAQ update (#2111) * FAQ update: how downsampling and deduplication will work at the same time * Update docs/FAQ.md Co-authored-by: Aliaksandr Valialkin --- docs/FAQ.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/FAQ.md b/docs/FAQ.md index c62cfad60..c820aff90 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -356,3 +356,7 @@ There could be a slight difference in stored values for time series. Due to diff The query engine may behave differently for some functions. Please see [this article](https://medium.com/@romanhavronenko/victoriametrics-promql-compliance-d4318203f51e). + +## If downsampling and deduplication are enabled how will this work? + +[Deduplication](https://docs.victoriametrics.com/#deduplication) is a special case of zero-offset [downsampling](https://docs.victoriametrics.com/#downsampling). So, if both downsampling and deduplication are enabled, then deduplication is replaced by zero-offset downsampling \ No newline at end of file