Andrii ChubatiukandGitHub
fc56d7aabc
### Describe Your Changes update victorialogs grafana plugin links, moved root plugin file to plugin repo ### Checklist The following checks are **mandatory**: - [ ] My change adheres to [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/victoriametrics/contributing/#pull-request-checklist). - [ ] My change adheres to [VictoriaMetrics development goals](https://docs.victoriametrics.com/victoriametrics/goals/).
3.0 KiB
title, weight, menu
| title | weight | menu | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Grafana | 1 |
|
VictoriaMetrics integrates with Grafana using either Prometheus datasource or VictoriaMetrics datasource plugins.
Resources:
VictoriaMetrics datasource
Create VictoriaMetrics datasource in Grafana with the following URL for single-server:
http://<victoriametrics-addr>:8428
Replace <victoriametrics-addr> with the VictoriaMetrics hostname or IP address.
For the cluster version, use vmselect address:
http://<vmselect-addr>:8481/select/<tenant>/prometheus
Replace <vmselect-addr> with the hostname or IP address of vmselect service.
If you have more than 1 vmselect, configure load-balancing.
Replace <tenant> based on your multitenancy settings.
Once connected, you can start building graphs and dashboards using PromQL or MetricsQL.
VictoriaMetrics datasource is publicly available on GitHub. See more in plugin docs.
Creating a datasource may require specific permissions. If you don't see an option to create a data source - try contacting system administrator.
Prometheus datasource
Create Prometheus datasource in Grafana. Follow the same connection instructions as for VictoriaMetrics datasource.
In the "Type and version" section set the type to "Prometheus" and the version to at least "2.24.x". This allows Grafana to use a more efficient API to get label values:
Once connected, you can build graphs and dashboards using PromQL.
Creating a datasource may require specific permissions. If you don't see an option to create a data source - try contacting system administrator.