From c9837de9cdddb36da84833571219d42ff51f7993 Mon Sep 17 00:00:00 2001 From: hagen1778 Date: Sun, 24 Nov 2024 14:18:26 +0100 Subject: [PATCH] docs: add vmui section to cluster docs It looks like users get confused with vmui availability in vmselect. Adding a note about it to cluster docs should improve situation. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7631 Signed-off-by: hagen1778 --- docs/Cluster-VictoriaMetrics.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/Cluster-VictoriaMetrics.md b/docs/Cluster-VictoriaMetrics.md index 992973bd7..1f238574a 100644 --- a/docs/Cluster-VictoriaMetrics.md +++ b/docs/Cluster-VictoriaMetrics.md @@ -58,6 +58,12 @@ It increases cluster availability, and simplifies cluster maintenance as well as > Note that `vmselect` despite being stateless still requires some disk space (a few GBs) for temporary caches. Refer to the `-cacheDataPath` command-line flag for more details. +## vmui + +VictoriaMetrics cluster version provides UI for query troubleshooting and exploration. The UI is available at +`http://:8481/select//vmui/` in each `vmeselect` service. +The UI allows exploring query results via graphs and tables. See more details about [vmui](https://docs.victoriametrics.com/#vmui). + ## Multitenancy VictoriaMetrics cluster supports multiple isolated tenants (aka namespaces).