Changes
Update notes: this release introduces backwards-incompatible changes to communication protocol between vmselect
and vmstorage
nodes in cluster version of VictoriaMetrics, so vmselect
and vmstorage
nodes may log communication errors during the upgrade. These errors should stop after all the vmselect
and vmstorage
nodes are updated to new release.
-
FEATURE: vmctl: add ability to verify files obtained via native export. See these docs and this feature request.
-
FEATURE: vmui: add pre-defined dasbhoards for per-job CPU usage, memory usage and disk IO usage. See this pull request for details.
-
FEATURE: vmalert: improve compatibility with Prometheus Alert Generator specification. See this pull request.
-
FEATURE: vmalert: add
-datasource.disableKeepAlive
command-line flag, which can be used for disabling HTTP keep-alive connections to datasources. This option can be useful for distributing load among multiple datasources behind TCP proxy such as HAProxy. -
FEATURE: Cluster version of VictoriaMetrics: reduce memory usage by up to 50% for
vminsert
andvmstorage
under high ingestion rate. -
FEATURE: vmgateway: Allow to read
-ratelimit.config
file from URL. Also add-ratelimit.configCheckInterval
command-line option. See this issue. -
FEATURE: add the following command-line flags, which can be used for fine-grained limiting of CPU and memory usage during various API calls:
-search.maxFederateSeries
for limiting the number of time series, which can be returned from /federate.-search.maxExportSeries
for limiting the number of time series, which can be returned from /api/v1/export.-search.maxSeries
for limiting the number of time series, which can be returned from /api/v1/series.-search.maxTSDBStatusSeries
for limiting the number of time series, which can be scanned during the request to /api/v1/status/tsdb.-search.maxGraphiteSeries
for limiting the number of time series, which can be scanned during the request to Graphite Render API.
Previously the -search.maxUniqueTimeseries
command-line flag was used as a global limit for all these APIs. Now the -search.maxUniqueTimeseries
is used only for limiting the number of time series, which can be scanned during requests to /api/v1/query and /api/v1/query_range.
When using cluster version of VictoriaMetrics, these command-line flags (including -search.maxUniqueTimeseries
) must be passed to vmselect
instead of vmstorage
.
- BUGFIX: vmagent and vmauth: reduce the probability of
TLS handshake error from XX.XX.XX.XX: EOF
errors when-remoteWrite.url
points to HTTPS url atvmauth
. See this issue. - BUGFIX: return
Content-Type: text/html
response header when requesting/
HTTP path at VictoriaMetrics components. Previouslytext/plain
response header was returned, which could lead to broken page formatting. See this issue. - BUGFIX: Graphite Render API: accept floating-point values for maxDataPoints query arg, since some clients send floating-point values instead of integer values for this arg.
See full changelog.
How to run VictoriaMetrics
Unpack the victoria-metrics-*.tar.gz
archive and read these docs.
vmutils-*.tag.gz
archive contains the following tools:
vmutils-*-enterprise.tar.gz
archive contains the following additional enterprise tools:
The corresponding docker images are available here.
Cluster version is available here.