diff --git a/docs/Troubleshooting.md b/docs/Troubleshooting.md
index c7a369a97..e7d9192ac 100644
--- a/docs/Troubleshooting.md
+++ b/docs/Troubleshooting.md
@@ -42,9 +42,10 @@ 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:
 
    ```console
-   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=...'
+   
+   cluster: curl http://<vmselect>:8481/select/<tenantID>/prometheus/api/v1/export -d 'match[]=http_requests_total' -d 'start=...' -d 'end=...'
    ```
-
    Note that responses returned from [/api/v1/query](https://docs.victoriametrics.com/keyConcepts.html#instant-query)
    and from [/api/v1/query_range](https://docs.victoriametrics.com/keyConcepts.html#range-query) contain **evaluated** data
    instead of raw samples stored in VictoriaMetrics. See [these docs](https://prometheus.io/docs/prometheus/latest/querying/basics/#staleness)