diff --git a/README.md b/README.md index a151bc252..9cd1f6360 100644 --- a/README.md +++ b/README.md @@ -132,7 +132,8 @@ By default the following TCP ports are used: - `vmstorage` - 8482 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 diff --git a/docs/Cluster-VictoriaMetrics.md b/docs/Cluster-VictoriaMetrics.md index 461b6138e..ace3ca854 100644 --- a/docs/Cluster-VictoriaMetrics.md +++ b/docs/Cluster-VictoriaMetrics.md @@ -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. +#### 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 ` will translate to `insert_maxQueueDuration=`) +- For repeating flags, an alternative syntax can be used by joining the different values into one using `,` as separator (for example `-storageNode -storageNode ` will translate to `storageNode=,`) ### Monitoring @@ -123,7 +130,8 @@ By default the following TCP ports are used: - `vmstorage` - 8482 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 diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index 11d4a9066..cdc4f7dce 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -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 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 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. 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: