From 380a6250d042cc5e087ace752626ba68b302a755 Mon Sep 17 00:00:00 2001 From: Vika Date: Wed, 17 Jan 2024 15:00:56 +0000 Subject: [PATCH] update wiki pages --- README.md | 6 +++--- Single-server-VictoriaMetrics.md | 6 +++--- guides/k8s-monitoring-via-vm-single.md | 2 +- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 8bde09a..f316f39 100644 --- a/README.md +++ b/README.md @@ -1858,7 +1858,7 @@ This increases overhead during data querying, since VictoriaMetrics needs to rea bigger number of parts per each request. That's why it is recommended to have at least 20% of free disk space under directory pointed by `-storageDataPath` command-line flag. -Information about merging process is available in [the dashboard for single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics/) +Information about merging process is available in [the dashboard for single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics-single-node/) and [the dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/). See more details in [monitoring docs](#monitoring). @@ -2061,7 +2061,7 @@ with 10 seconds interval. _Please note, never use loadbalancer address for scraping metrics. All monitored components should be scraped directly by their address._ -Official Grafana dashboards available for [single-node](https://grafana.com/grafana/dashboards/10229-victoriametrics/) +Official Grafana dashboards available for [single-node](https://grafana.com/grafana/dashboards/10229-victoriametrics-single-node/) and [clustered](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/) VictoriaMetrics. See an [alternative dashboard for clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11831) created by community. @@ -2332,7 +2332,7 @@ The following metrics for each type of cache are exported at [`/metrics` page](# * `vm_cache_misses_total` - the number of cache misses * `vm_cache_entries` - the number of entries in the cache -Both Grafana dashboards for [single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics/) +Both Grafana dashboards for [single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics-single-node/) and [clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/) contain `Caches` section with cache metrics visualized. The panels show the current memory usage by each type of cache, and also a cache hit rate. If hit rate is close to 100% diff --git a/Single-server-VictoriaMetrics.md b/Single-server-VictoriaMetrics.md index a0cd9b5..cae949f 100644 --- a/Single-server-VictoriaMetrics.md +++ b/Single-server-VictoriaMetrics.md @@ -1866,7 +1866,7 @@ This increases overhead during data querying, since VictoriaMetrics needs to rea bigger number of parts per each request. That's why it is recommended to have at least 20% of free disk space under directory pointed by `-storageDataPath` command-line flag. -Information about merging process is available in [the dashboard for single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics/) +Information about merging process is available in [the dashboard for single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics-single-node/) and [the dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/). See more details in [monitoring docs](#monitoring). @@ -2069,7 +2069,7 @@ with 10 seconds interval. _Please note, never use loadbalancer address for scraping metrics. All monitored components should be scraped directly by their address._ -Official Grafana dashboards available for [single-node](https://grafana.com/grafana/dashboards/10229-victoriametrics/) +Official Grafana dashboards available for [single-node](https://grafana.com/grafana/dashboards/10229-victoriametrics-single-node/) and [clustered](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/) VictoriaMetrics. See an [alternative dashboard for clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11831) created by community. @@ -2340,7 +2340,7 @@ The following metrics for each type of cache are exported at [`/metrics` page](# * `vm_cache_misses_total` - the number of cache misses * `vm_cache_entries` - the number of entries in the cache -Both Grafana dashboards for [single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics/) +Both Grafana dashboards for [single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics-single-node/) and [clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/) contain `Caches` section with cache metrics visualized. The panels show the current memory usage by each type of cache, and also a cache hit rate. If hit rate is close to 100% diff --git a/guides/k8s-monitoring-via-vm-single.md b/guides/k8s-monitoring-via-vm-single.md index 85e5cee..c21cd4b 100644 --- a/guides/k8s-monitoring-via-vm-single.md +++ b/guides/k8s-monitoring-via-vm-single.md @@ -306,7 +306,7 @@ EOF By running this command we: * Install Grafana from Helm repository. * Provision VictoriaMetrics datasource with the url from the output above which we copied before. -* Add this [https://grafana.com/grafana/dashboards/10229-victoriametrics/](https://grafana.com/grafana/dashboards/10229-victoriametrics/) dashboard for VictoriaMetrics. +* Add this [https://grafana.com/grafana/dashboards/10229-victoriametrics/](https://grafana.com/grafana/dashboards/10229-victoriametrics-single-node/) dashboard for VictoriaMetrics. * Add this [https://grafana.com/grafana/dashboards/14205-kubernetes-cluster-monitoring-via-prometheus/](https://grafana.com/grafana/dashboards/14205-kubernetes-cluster-monitoring-via-prometheus/) dashboard to see Kubernetes cluster metrics.