mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-21 14:44:00 +00:00
fix link for grafana dashbaord for single node after its renaming
Signed-off-by: Artem Navoiev <tenmozes@gmail.com>
This commit is contained in:
parent
dab160cd74
commit
ff33e60a3d
5 changed files with 11 additions and 11 deletions
2
.github/ISSUE_TEMPLATE/bug_report.yml
vendored
2
.github/ISSUE_TEMPLATE/bug_report.yml
vendored
|
@ -60,7 +60,7 @@ body:
|
||||||
|
|
||||||
For VictoriaMetrics health-state issues please provide full-length screenshots
|
For VictoriaMetrics health-state issues please provide full-length screenshots
|
||||||
of Grafana dashboards if possible:
|
of Grafana dashboards if possible:
|
||||||
* [Grafana dashboard for single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics/)
|
* [Grafana dashboard for single-node VictoriaMetrics](https://grafana.com/grafana/dashboards/10229-victoriametrics-single-node/)
|
||||||
* [Grafana dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/)
|
* [Grafana dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/)
|
||||||
|
|
||||||
See how to setup monitoring here:
|
See how to setup monitoring here:
|
||||||
|
|
|
@ -1855,7 +1855,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%
|
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.
|
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/).
|
and [the dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/).
|
||||||
See more details in [monitoring docs](#monitoring).
|
See more details in [monitoring docs](#monitoring).
|
||||||
|
|
||||||
|
@ -2058,7 +2058,7 @@ with 10 seconds interval.
|
||||||
|
|
||||||
_Please note, never use loadbalancer address for scraping metrics. All monitored components should be scraped directly by their address._
|
_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.
|
and [clustered](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/) VictoriaMetrics.
|
||||||
See an [alternative dashboard for clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11831)
|
See an [alternative dashboard for clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11831)
|
||||||
created by community.
|
created by community.
|
||||||
|
@ -2329,7 +2329,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_misses_total` - the number of cache misses
|
||||||
* `vm_cache_entries` - the number of entries in the cache
|
* `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/)
|
and [clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/)
|
||||||
contain `Caches` section with cache metrics visualized. The panels show the current
|
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%
|
memory usage by each type of cache, and also a cache hit rate. If hit rate is close to 100%
|
||||||
|
|
|
@ -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%
|
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.
|
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/).
|
and [the dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/).
|
||||||
See more details in [monitoring docs](#monitoring).
|
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._
|
_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.
|
and [clustered](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/) VictoriaMetrics.
|
||||||
See an [alternative dashboard for clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11831)
|
See an [alternative dashboard for clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11831)
|
||||||
created by community.
|
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_misses_total` - the number of cache misses
|
||||||
* `vm_cache_entries` - the number of entries in the cache
|
* `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/)
|
and [clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/)
|
||||||
contain `Caches` section with cache metrics visualized. The panels show the current
|
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%
|
memory usage by each type of cache, and also a cache hit rate. If hit rate is close to 100%
|
||||||
|
|
|
@ -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%
|
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.
|
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/).
|
and [the dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/).
|
||||||
See more details in [monitoring docs](#monitoring).
|
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._
|
_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.
|
and [clustered](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/) VictoriaMetrics.
|
||||||
See an [alternative dashboard for clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11831)
|
See an [alternative dashboard for clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11831)
|
||||||
created by community.
|
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_misses_total` - the number of cache misses
|
||||||
* `vm_cache_entries` - the number of entries in the cache
|
* `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/)
|
and [clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/)
|
||||||
contain `Caches` section with cache metrics visualized. The panels show the current
|
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%
|
memory usage by each type of cache, and also a cache hit rate. If hit rate is close to 100%
|
||||||
|
|
|
@ -306,7 +306,7 @@ EOF
|
||||||
By running this command we:
|
By running this command we:
|
||||||
* Install Grafana from Helm repository.
|
* Install Grafana from Helm repository.
|
||||||
* Provision VictoriaMetrics datasource with the url from the output above which we copied before.
|
* 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.
|
* 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.
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue