diff --git a/Cluster-VictoriaMetrics.md b/Cluster-VictoriaMetrics.md index 8026146..81e5fac 100644 --- a/Cluster-VictoriaMetrics.md +++ b/Cluster-VictoriaMetrics.md @@ -264,7 +264,7 @@ By default the following TCP ports are used: It is recommended setting up [vmagent](https://docs.victoriametrics.com/vmagent.html) or Prometheus to scrape `/metrics` pages from all the cluster components, so they can be monitored and analyzed -with [the official Grafana dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11176) +with [the official Grafana dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/) or [an alternative dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11831). Graphs on these dashboards contain useful hints - hover the `i` icon at the top left corner of each graph in order to read it. It is recommended setting up alerts in [vmalert](https://docs.victoriametrics.com/vmalert.html) or in Prometheus from [this config](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/cluster/deployment/docker/alerts.yml). diff --git a/README.md b/README.md index 7e91926..3b62c4c 100644 --- a/README.md +++ b/README.md @@ -1441,8 +1441,8 @@ 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/dashboards/10229) -and [the dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11176). +Information about merging process is available in [the dashboard for single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics/) +and [the dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/). See more details in [monitoring docs](#monitoring). See [this article](https://valyala.medium.com/how-victoriametrics-makes-instant-snapshots-for-multi-terabyte-time-series-data-e1f3fb0e0282) for more details. @@ -1609,8 +1609,8 @@ Alternatively, single-node VictoriaMetrics can self-scrape the metrics when `-se set to duration greater than 0. For example, `-selfScrapeInterval=10s` would enable self-scraping of `/metrics` page with 10 seconds interval. -Official Grafana dashboards available for [single-node](https://grafana.com/dashboards/10229) -and [clustered](https://grafana.com/grafana/dashboards/11176) VictoriaMetrics. +Official Grafana dashboards available for [single-node](https://grafana.com/grafana/dashboards/10229-victoriametrics/) +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. @@ -1859,8 +1859,8 @@ 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/dashboards/10229) -and [clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11176) +Both Grafana dashboards for [single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics/) +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% then cache efficiency is already very high and does not need any tuning. diff --git a/Single-server-VictoriaMetrics.md b/Single-server-VictoriaMetrics.md index bd678e3..34c1c5e 100644 --- a/Single-server-VictoriaMetrics.md +++ b/Single-server-VictoriaMetrics.md @@ -1444,8 +1444,8 @@ 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/dashboards/10229) -and [the dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11176). +Information about merging process is available in [the dashboard for single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics/) +and [the dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/). See more details in [monitoring docs](#monitoring). See [this article](https://valyala.medium.com/how-victoriametrics-makes-instant-snapshots-for-multi-terabyte-time-series-data-e1f3fb0e0282) for more details. @@ -1612,8 +1612,8 @@ Alternatively, single-node VictoriaMetrics can self-scrape the metrics when `-se set to duration greater than 0. For example, `-selfScrapeInterval=10s` would enable self-scraping of `/metrics` page with 10 seconds interval. -Official Grafana dashboards available for [single-node](https://grafana.com/dashboards/10229) -and [clustered](https://grafana.com/grafana/dashboards/11176) VictoriaMetrics. +Official Grafana dashboards available for [single-node](https://grafana.com/grafana/dashboards/10229-victoriametrics/) +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. @@ -1862,8 +1862,8 @@ 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/dashboards/10229) -and [clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11176) +Both Grafana dashboards for [single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics/) +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% then cache efficiency is already very high and does not need any tuning. diff --git a/guides/k8s-monitoring-via-vm-cluster.md b/guides/k8s-monitoring-via-vm-cluster.md index 5ee1149..4cbee6c 100644 --- a/guides/k8s-monitoring-via-vm-cluster.md +++ b/guides/k8s-monitoring-via-vm-cluster.md @@ -501,9 +501,9 @@ EOF By running this command we: * Install Grafana from the Helm repository. * Provision a VictoriaMetrics data source with the url from the output above which we remembered. -* Add this [https://grafana.com/grafana/dashboards/11176](https://grafana.com/grafana/dashboards/11176) dashboard for [VictoriaMetrics Cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html). -* Add this [https://grafana.com/grafana/dashboards/12683](https://grafana.com/grafana/dashboards/12683) dashboard for [VictoriaMetrics Agent](https://docs.victoriametrics.com/vmagent.html). -* Add this [https://grafana.com/grafana/dashboards/14205](https://grafana.com/grafana/dashboards/14205) dashboard to see Kubernetes cluster metrics. +* Add this [https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/) dashboard for [VictoriaMetrics Cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html). +* Add this [https://grafana.com/grafana/dashboards/12683-victoriametrics-vmagent/](https://grafana.com/grafana/dashboards/12683-victoriametrics-vmagent/) dashboard for [VictoriaMetrics Agent](https://docs.victoriametrics.com/vmagent.html). +* 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. Please see the output log in your terminal. Copy, paste and run these commands. diff --git a/guides/k8s-monitoring-via-vm-single.md b/guides/k8s-monitoring-via-vm-single.md index eaab671..166c670 100644 --- a/guides/k8s-monitoring-via-vm-single.md +++ b/guides/k8s-monitoring-via-vm-single.md @@ -296,8 +296,8 @@ 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](https://grafana.com/grafana/dashboards/10229) dashboard for VictoriaMetrics. -* Add this [https://grafana.com/grafana/dashboards/14205](https://grafana.com/grafana/dashboards/14205) dashboard to see Kubernetes cluster metrics. +* 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/14205-kubernetes-cluster-monitoring-via-prometheus/](https://grafana.com/grafana/dashboards/14205-kubernetes-cluster-monitoring-via-prometheus/) dashboard to see Kubernetes cluster metrics. Check the output log in your terminal. diff --git a/vmagent.md b/vmagent.md index ef3a7f4..9b25c87 100644 --- a/vmagent.md +++ b/vmagent.md @@ -820,7 +820,7 @@ See also [cardinality explorer docs](https://docs.victoriametrics.com/#cardinali We recommend setting up regular scraping of this page either through `vmagent` itself or by Prometheus so that the exported metrics may be analyzed later. -Use official [Grafana dashboard](https://grafana.com/grafana/dashboards/12683) for `vmagent` state overview. +Use official [Grafana dashboard](https://grafana.com/grafana/dashboards/12683-victoriametrics-vmagent/) for `vmagent` state overview. Graphs on this dashboard contain useful hints - hover the `i` icon at the top left corner of each graph in order to read it. If you have suggestions for improvements or have found a bug - please open an issue on github or add a review to the dashboard. diff --git a/vmalert.md b/vmalert.md index 30c04c6..9c037d3 100644 --- a/vmalert.md +++ b/vmalert.md @@ -682,7 +682,7 @@ The default list of alerting rules for these metric can be found [here](https:// We recommend setting up regular scraping of this page either through `vmagent` or by Prometheus so that the exported metrics may be analyzed later. -Use the official [Grafana dashboard](https://grafana.com/grafana/dashboards/14950) for `vmalert` overview. +Use the official [Grafana dashboard](https://grafana.com/grafana/dashboards/14950-victoriametrics-vmalert/) for `vmalert` overview. Graphs on this dashboard contain useful hints - hover the `i` icon in the top left corner of each graph in order to read it. If you have suggestions for improvements or have found a bug - please open an issue on github or add a review to the dashboard.