mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2025-01-20 07:19:17 +01:00
docs/FAQ.md: actualize answer about deduplication
This commit is contained in:
parent
9d89b08cb5
commit
8d3869cd99
@ -163,14 +163,7 @@ or via [Prometheus datasource in Grafana](http://docs.grafana.org/features/datas
|
|||||||
|
|
||||||
### Does VictoriaMetrics deduplicate data from Prometheus instances scraping the same targets (aka `HA pairs`)?
|
### Does VictoriaMetrics deduplicate data from Prometheus instances scraping the same targets (aka `HA pairs`)?
|
||||||
|
|
||||||
Data from all the Prometheus instances is saved in VictoriaMetrics without deduplication.
|
Yes. See [these docs](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/README.md#deduplication) for details.
|
||||||
|
|
||||||
The deduplication for Prometheus HA pair may be easily implemented on top of VictoriaMetrics with the following steps:
|
|
||||||
|
|
||||||
1) Run multiple VictoriaMetrics instances in multiple availability zones (datacenters).
|
|
||||||
2) Configure each Prometheus from each HA pair to write data to VictoriaMetrics in distinct availability zone.
|
|
||||||
3) Put [Promxy](https://github.com/jacksontj/promxy) in front of all the VictoriaMetrics instances.
|
|
||||||
4) Send queries to Promxy - it will deduplicate data from VictoriaMetrics instances behind it.
|
|
||||||
|
|
||||||
|
|
||||||
### Where is the source code of VictoriaMetrics?
|
### Where is the source code of VictoriaMetrics?
|
||||||
|
Loading…
Reference in New Issue
Block a user