docs/Single-server-VictoriaMetrics.md: link to cardinality limiter docs in vmagent

This commit is contained in:
Aliaksandr Valialkin 2021-09-13 21:26:59 +03:00
parent a8f1b614e5
commit d3289bf276
3 changed files with 6 additions and 0 deletions

View file

@ -280,6 +280,8 @@ with new configs.
Cluster should remain in working state if at least a single node of each type remains available during Cluster should remain in working state if at least a single node of each type remains available during
the update process. See [cluster availability](#cluster-availability) section for details. the update process. See [cluster availability](#cluster-availability) section for details.
See also more advanced [cardinality limiter in vmagent](https://docs.victoriametrics.com/vmagent.html#cardinality-limiter).
## Cluster availability ## Cluster availability

View file

@ -1231,6 +1231,8 @@ The exceeded limits can be [monitored](#monitoring) with the following metrics:
These limits are approximate, so VictoriaMetrics can underflow/overflow the limit by a small percentage (usually less than 1%). These limits are approximate, so VictoriaMetrics can underflow/overflow the limit by a small percentage (usually less than 1%).
See also more advanced [cardinality limiter in vmagent](https://docs.victoriametrics.com/vmagent.html#cardinality-limiter).
## Troubleshooting ## Troubleshooting

View file

@ -1235,6 +1235,8 @@ The exceeded limits can be [monitored](#monitoring) with the following metrics:
These limits are approximate, so VictoriaMetrics can underflow/overflow the limit by a small percentage (usually less than 1%). These limits are approximate, so VictoriaMetrics can underflow/overflow the limit by a small percentage (usually less than 1%).
See also more advanced [cardinality limiter in vmagent](https://docs.victoriametrics.com/vmagent.html#cardinality-limiter).
## Troubleshooting ## Troubleshooting