From 07c067697e8815412a2a0d685c286990105b7536 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Fri, 7 Feb 2020 00:02:25 +0200 Subject: [PATCH] docs/Single-server-VictoriaMetrics.md: sync with README.md --- docs/Single-server-VictoriaMetrics.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/docs/Single-server-VictoriaMetrics.md b/docs/Single-server-VictoriaMetrics.md index 739d31725..e142fb6c6 100644 --- a/docs/Single-server-VictoriaMetrics.md +++ b/docs/Single-server-VictoriaMetrics.md @@ -85,6 +85,7 @@ Cluster version is available [here](https://github.com/VictoriaMetrics/VictoriaM - [Federation](#federation) - [Capacity planning](#capacity-planning) - [High availability](#high-availability) + - [Deduplication](#deduplication) - [Retention](#retention) - [Multiple retentions](#multiple-retentions) - [Downsampling](#downsampling) @@ -691,6 +692,19 @@ kill -HUP `pidof prometheus` If you have Prometheus HA pairs with replicas `r1` and `r2` in each pair, then configure each `r1` to write data to `victoriametrics-addr-1`, while each `r2` should write data to `victoriametrics-addr-2`. +Another option is to write data simultaneously from Prometheus HA pair to a pair of VictoriaMetrics instances +with the enabled de-duplication. See [this section](#deduplication) for details. + + +### Deduplication + +VictoriaMetrics de-duplicates data points if `-dedup.minScrapeInterval` command-line flag +is set to positive duration. For example, `-dedup.minScrapeInterval=60s` would de-duplicate data points +on the same time series if they are located closer than 60s to each other. +The de-duplication reduces disk space usage if multiple identically configured Prometheus instances in HA pair +write data to the same VictoriaMetrics instance. Note that these Prometheus instances must have identical +`external_labels` section in their configs, so they write data to the same time series. + ### Retention @@ -784,7 +798,7 @@ mkfs.ext4 ... -O 64bit,huge_file,extent -T huge VictoriaMetrics exports internal metrics in Prometheus format at `/metrics` page. These metrics may be collected either via Prometheus by adding the corresponding scrape config to it. Alternatively they can be self-scraped by setting `-selfScrapeInterval` command-line flag to duration greater than 0. -For example, `-scrapeInterval=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).