From 4860cbd00cf5956c0ce82d1d8ea7162dec820f10 Mon Sep 17 00:00:00 2001 From: Vika Date: Thu, 6 Jan 2022 23:19:59 +0000 Subject: [PATCH] update wiki pages --- CHANGELOG.md | 1 + vmagent.md | 1 - vmctl.md | 9 +++++++++ 3 files changed, 10 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index edf3995..e7edf72 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -14,6 +14,7 @@ sort: 15 * BUGFIX: return the proper response stub from `/api/v1/query_exemplars` handler, which is needed for Grafana v8+. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1999). * BUGFIX: [vmctl](https://docs.victoriametrics.com/vmctl.html): fix a few edge cases and improve migration speed for OpenTSDB importer. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/2019). * BUGFIX: fix possible data race when searching for time series matching `{key=~"value|"}` filter over time range covering multipe days. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/2032). Thanks to @waldoweng for the provided fix. +* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): do not send staleness markers on graceful shutdown. This follows Prometheus behavior. See [this comment](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2013#issuecomment-1006994079). ## [v1.71.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.71.0) diff --git a/vmagent.md b/vmagent.md index cdd3cd7..d70b027 100644 --- a/vmagent.md +++ b/vmagent.md @@ -305,7 +305,6 @@ You can read more about relabeling in the following articles: * If the metric disappears from the list of scraped metrics, then stale marker is sent to this particular metric. * If the scrape target becomes temporarily unavailable, then stale markers are sent for all the metrics scraped from this target. * If the scrape target is removed from the list of targets, then stale markers are sent for all the metrics scraped from this target. -* Stale markers are sent for all the scraped metrics on graceful shutdown of `vmagent`. Prometheus staleness markers' tracking needs additional memory, since it must store the previous response body per each scrape target in order to compare it to the current response body. The memory usage may be reduced by passing `-promscrape.noStaleMarkers` command-line flag to `vmagent`. This disables staleness tracking. This also disables tracking the number of new time series per each scrape with the auto-generated `scrape_series_added` metric. See [these docs](https://prometheus.io/docs/concepts/jobs_instances/#automatically-generated-labels-and-time-series) for details. diff --git a/vmctl.md b/vmctl.md index fd332ad..b1df62e 100644 --- a/vmctl.md +++ b/vmctl.md @@ -564,6 +564,15 @@ results such as `average`, `rate`, etc. If multiple labels needs to be added, set flag for each label, for example, `--vm-extra-label label1=value1 --vm-extra-label label2=value2`. If timeseries already have label, that must be added with `--vm-extra-label` flag, flag has priority and will override label value from timeseries. +### Rate limiting + +Limiting the rate of data transfer could help to reduce pressure on disk or on destination database. +The rate limit may be set in bytes-per-second via `--vm-rate-limit` flag. + +Please note, you can also use [vmagent](https://docs.victoriametrics.com/vmagent.html) +as a proxy between `vmctl` and destination with `-remoteWrite.rateLimit` flag enabled. + + ## How to build It is recommended using [binary releases](https://github.com/VictoriaMetrics/VictoriaMetrics/releases) - `vmctl` is located in `vmutils-*` archives there.