From d6bafe31d354e12c8a2828d954647f8311dadd9e Mon Sep 17 00:00:00 2001 From: Artem Fetishev <149964189+rtm0@users.noreply.github.com> Date: Thu, 17 Oct 2024 18:50:25 +0200 Subject: [PATCH] docs/troubleshooting: add reduce_mem_usage=1 to export query (#7286) ### Describe Your Changes When debugging unexpected query results, add reduce_mem_usage=1 param to export query to preserve duplicates. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: Artem Fetishev --- docs/Troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Troubleshooting.md b/docs/Troubleshooting.md index 9c71b30c2..1dcffe051 100644 --- a/docs/Troubleshooting.md +++ b/docs/Troubleshooting.md @@ -129,9 +129,9 @@ If you see unexpected or unreliable query results from VictoriaMetrics, then try on the given `[start..end]` time range and check whether they are expected: ```sh - single-node: curl http://victoriametrics:8428/api/v1/export -d 'match[]=http_requests_total' -d 'start=...' -d 'end=...' + single-node: curl http://victoriametrics:8428/api/v1/export -d 'match[]=http_requests_total' -d 'start=...' -d 'end=...' -d 'reduce_mem_usage=1' - cluster: curl http://:8481/select//prometheus/api/v1/export -d 'match[]=http_requests_total' -d 'start=...' -d 'end=...' + cluster: curl http://:8481/select//prometheus/api/v1/export -d 'match[]=http_requests_total' -d 'start=...' -d 'end=...' -d 'reduce_mem_usage=1' ``` Note that responses returned from [/api/v1/query](https://docs.victoriametrics.com/keyconcepts/#instant-query) and from [/api/v1/query_range](https://docs.victoriametrics.com/keyconcepts/#range-query) contain **evaluated** data