mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-15 16:30:55 +01:00
2152d3eb61
* Multi retention standardization of docs While reading through the docs the implementation details had different formatting for storageNode. This standardizes them and adds a link to the retention docs. * Update docs/guides/guide-vmcluster-multiple-retention-setup.md Co-authored-by: Aliaksandr Valialkin <valyala@gmail.com>
41 lines
2.4 KiB
Markdown
41 lines
2.4 KiB
Markdown
# Multi Retention Setup within VictoriaMetrics Cluster
|
|
|
|
|
|
**Objective**
|
|
|
|
Setup Victoria Metrics TSDB with support of multiple retention periods within one installation.
|
|
|
|
**Challenge**
|
|
|
|
VictoriaMetrics instance (single node or vmstorage node) supports only one retention period.
|
|
|
|
|
|
**Solution**
|
|
|
|
A multi-retention setup can be implemented by dividing a [victoriametrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html) into logical groups with different retentions.
|
|
|
|
Example:
|
|
Setup should handle 3 different retention groups 3months, 1year and 3 years.
|
|
Solution contains 3 groups of vmstorages + vminserst and one group of vmselects. Routing is done by [vmagent](https://docs.victoriametrics.com/vmagent.html) and [relabeling configuration](https://docs.victoriametrics.com/vmagent.html#relabeling). The [-retentionPeriod](https://docs.victoriametrics.com/#retention) sets how long to keep the metrics.
|
|
|
|
The diagram below shows a proposed solution
|
|
|
|
<p align="center">
|
|
<img src="guide-vmcluster-multiple-retention-scheme.png" width="800">
|
|
</p>
|
|
|
|
**Implementation Details**
|
|
1. Groups of vminserts A know about only vmstorages A and this is explicitly specified via `-storageNode` [configuration](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#cluster-setup).
|
|
2. Groups of vminserts B know about only vmstorages B and this is explicitly specified via `-storageNode` [configuration](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#cluster-setup).
|
|
3. Groups of vminserts C know about only vmstorages A and this is explicitly specified via `-storageNode` [configuration](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#cluster-setup).
|
|
4. Vmselect reads data from all vmstorage nodes via `-storageNode` [configuration](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#cluster-setup).
|
|
5. Vmagent routes incoming metrics to the given set of `vminsert` nodes using relabeling rules specified at `-remoteWrite.urlRelabelConfig` [configuration](https://docs.victoriametrics.com/vmagent.html#relabeling).
|
|
|
|
**Multi-Tenant Setup**
|
|
|
|
Every group of vmstorages can handle one tenant or multiple one. Different groups can have overlapping tenants. As vmselect reads from all vmstorage nodes, the data is aggregated on its level.
|
|
|
|
**Additional Enhancements**
|
|
|
|
You can set up [vmauth](https://docs.victoriametrics.com/vmauth.html) for routing data to the given vminsert group depending on the needed retention.
|