mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-21 14:44:00 +00:00
README.md: mention about alternative dashboard for cluster version - https://grafana.com/grafana/dashboards/11831
This commit is contained in:
parent
50555d89d3
commit
41b532046f
3 changed files with 15 additions and 2 deletions
|
@ -132,7 +132,8 @@ By default the following TCP ports are used:
|
||||||
- `vmstorage` - 8482
|
- `vmstorage` - 8482
|
||||||
|
|
||||||
It is recommended setting up Prometheus to scrape `/metrics` pages from all the cluster components, so they can be monitored and analyzed
|
It is recommended setting up 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)
|
||||||
|
or [an alternative dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11831).
|
||||||
|
|
||||||
|
|
||||||
### URL format
|
### URL format
|
||||||
|
|
|
@ -113,6 +113,13 @@ Ports may be altered by setting `-httpListenAddr` on the corresponding nodes.
|
||||||
|
|
||||||
It is recommended setting up [monitoring](#monitoring) for the cluster.
|
It is recommended setting up [monitoring](#monitoring) for the cluster.
|
||||||
|
|
||||||
|
#### Environment variables
|
||||||
|
|
||||||
|
Each flag values can be set thru environment variables by following these rules:
|
||||||
|
|
||||||
|
- The `-envflag.enable` flag must be set
|
||||||
|
- Each `.` in flag names must be substituted by `_` (for example `-insert.maxQueueDuration <duration>` will translate to `insert_maxQueueDuration=<duration>`)
|
||||||
|
- For repeating flags, an alternative syntax can be used by joining the different values into one using `,` as separator (for example `-storageNode <nodeA> -storageNode <nodeB>` will translate to `storageNode=<nodeA>,<nodeB>`)
|
||||||
|
|
||||||
### Monitoring
|
### Monitoring
|
||||||
|
|
||||||
|
@ -123,7 +130,8 @@ By default the following TCP ports are used:
|
||||||
- `vmstorage` - 8482
|
- `vmstorage` - 8482
|
||||||
|
|
||||||
It is recommended setting up Prometheus to scrape `/metrics` pages from all the cluster components, so they can be monitored and analyzed
|
It is recommended setting up 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)
|
||||||
|
or [an alternative dashboard for VictoriaMetrics cluster](https://grafana.com/grafana/dashboards/11831).
|
||||||
|
|
||||||
|
|
||||||
### URL format
|
### URL format
|
||||||
|
|
|
@ -619,6 +619,9 @@ Each JSON line would contain data for a single time series. An example output:
|
||||||
Optional `start` and `end` args may be added to the request in order to limit the time frame for the exported data. These args may contain either
|
Optional `start` and `end` args may be added to the request in order to limit the time frame for the exported data. These args may contain either
|
||||||
unix timestamp in seconds or [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) values.
|
unix timestamp in seconds or [RFC3339](https://www.ietf.org/rfc/rfc3339.txt) values.
|
||||||
|
|
||||||
|
Optional `max_rows_per_line` arg may be added to the request in order to limit the maximum number of rows exported per each JSON line.
|
||||||
|
By default each JSON line contains all the rows for a single time series.
|
||||||
|
|
||||||
Pass `Accept-Encoding: gzip` HTTP header in the request to `/api/v1/export` in order to reduce network bandwidth during exporing big amounts
|
Pass `Accept-Encoding: gzip` HTTP header in the request to `/api/v1/export` in order to reduce network bandwidth during exporing big amounts
|
||||||
of time series data. This enables gzip compression for the exported data. Example for exporting gzipped data:
|
of time series data. This enables gzip compression for the exported data. Example for exporting gzipped data:
|
||||||
|
|
||||||
|
@ -844,6 +847,7 @@ Alternatively they can be self-scraped by setting `-selfScrapeInterval` command-
|
||||||
For example, `-selfScrapeInterval=10s` would enable self-scraping of `/metrics` page with 10 seconds interval.
|
For example, `-selfScrapeInterval=10s` would enable self-scraping of `/metrics` page with 10 seconds interval.
|
||||||
|
|
||||||
There are officials Grafana dashboards for [single-node VictoriaMetrics](https://grafana.com/dashboards/10229) and [clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11176).
|
There are officials Grafana dashboards for [single-node VictoriaMetrics](https://grafana.com/dashboards/10229) and [clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11176).
|
||||||
|
There is also an [alternative dashboard for clustered VictoriaMetrics](https://grafana.com/grafana/dashboards/11831).
|
||||||
|
|
||||||
The most interesting metrics are:
|
The most interesting metrics are:
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue