github VictoriaMetrics/VictoriaMetrics v1.90.0
on GitHub

latest releases: v0.40.0-victorialogs, v0.39.0-victorialogs, v0.38.0-victorialogs...
19 months ago

Released at 2023-04-06

Update note: this release contains backwards-incompatible change in storage data format,
so the previous versions of VictoriaMetrics will exit with the unexpected number of substrings in the part name error when trying to run them on the data
created by v1.90.0 or newer versions. The solution is to upgrade to v1.90.0 or newer releases

  • SECURITY: upgrade base docker image (alpine) from 3.17.2 to 3.17.3. See alpine 3.17.3 release notes.

  • SECURITY: upgrade Go builder from Go1.20.2 to Go1.20.3. See the list of issues addressed in Go1.20.3.

  • FEATURE: release Windows binaries for single-node VictoriaMetrics, VictoriaMetrics cluster, vmbackup and vmrestore. See this, this and this issues. This release of VictoriaMetrics for Windows cannot delete snapshots due to Windows constraints. See this comment for details. This issue should be resolved in future releases.

  • FEATURE: log metrics with truncated labels if the length of label value in the ingested metric exceeds -maxLabelValueLen. This should simplify debugging for this case.

  • FEATURE: vmagent: show target URL when debugging target relabeling. This should simplify target relabel debugging a bit. See this pull request.

  • FEATURE: vmagent: add support for VictoriaMetrics remote write protocol when sending / receiving data to / from Kafka. This protocol allows saving egress network bandwidth costs when sending data from vmagent to Kafka located in another datacenter or availability zone. See this feature request.

  • FEATURE: vmagent: add -kafka.consumer.topic.concurrency command-line flag. It controls the number of Kafka consumer workers to use by vmagent. It should eliminate the need to start multiple vmagent instances to improve data transfer rate. See this feature request.

  • FEATURE: vmagent: add support for Kafka producer and consumer on arm64 machines. See this issue.

  • FEATURE: vmagent: delete unused buffered data at -remoteWrite.tmpDataPath directory when there is no matching -remoteWrite.url to send this data to. See this feature request.

  • FEATURE: vmagent: add the ability for hot reloading of stream aggregation configs. See these docs and this feature request.

  • FEATURE: check the contents of -relabelConfig and -streamAggr.config files additionally to -promscrape.config when single-node VictoriaMetrics runs with -dryRun command-line flag. This aligns the behaviour of single-node VictoriaMetrics with vmagent behaviour for -dryRun command-line flag.

  • FEATURE: vmui: automatically draw a heatmap graph when the query selects a single histogram. This simplifies analyzing histograms. See this feature request.

  • FEATURE: vmui: add support for drag'n'drop and paste from clipboard in the "Trace analyzer" page. See this pull request.

  • FEATURE: vmui: hide messages longer than 3 lines in the trace. You can view the full message by clicking on the show more button. See this pull request.

  • FEATURE: vmui: add the ability to manually input date and time when selecting a time range. See this pull request.

  • FEATURE: vmui: updated usability and the search process in cardinality explorer. Made this process straightforward for user. See this pull request.

  • FEATURE: vmui: add the ability to collapse/expand the legend. See this pull request.

  • FEATURE: vmui: add tips for working with the graph and legend. See this pull request.

  • FEATURE: vmui: add apply and cancel buttons to settings popup. See this issue.

  • FEATURE: vmctl: automatically disable progress bar when TTY isn't available. See this issue.

  • FEATURE: vmauth: add -configCheckInterval command-line flag, which can be used for automatic re-reading the -auth.config file. See this feature request.

  • BUGFIX: prevent from slow snapshot creating under high data ingestion rate. See this issue.

  • BUGFIX: vmauth: suppress proxy protocol parsing errors in case of EOF. Usually, the error is caused by health checks and is not a sign of an actual error.

  • BUGFIX: vmui: fix displaying errors for each query. See this issue.

  • BUGFIX: vmbackup: fix snapshot not being deleted in case of error during backup. See this issue.

  • BUGFIX: stream aggregation: suppress series after dedup error message in logs when -remoteWrite.streamAggr.dedupInterval command-line flag is set at vmagent or when -streamAggr.dedupInterval command-line flag is set at single-node VictoriaMetrics.

  • BUGFIX: allow using dashes and dots in environment variables names referred in config files via %{ENV-VAR.SYNTAX}. See these docs and this issue.

  • BUGFIX: return back query performance scalability on hosts with big number of CPU cores. The scalability has been reduced in v1.86.0. See this issue.

  • BUGFIX: MetricsQL: properly convert VictoriaMetrics historgram buckets to Prometheus histogram buckets when VictoriaMetrics histogram contain zero buckets. Previously these buckets were ignored, and this could lead to missing Prometheus histogram buckets after the conversion. Thanks to @zklapow for the fix.

  • BUGFIX: vmagent: fix CPU and memory usage spikes when files pointed by file_sd_config cannot be re-read. See this_issue.

  • BUGFIX: prevent unexpected merges on start-up when -storage.minFreeDiskSpaceBytes is set. See the issue.

  • BUGFIX: properly support comma-separated filters inside retention filters. See this issue.

  • BUGFIX: verify response code when fetching configuration files via HTTP. See this issue.

  • BUGFIX: vmalert: replace empty labels with "" instead of "<no value>" during templating, as Prometheus does. See this issue.

  • BUGFIX: vmctl: properly pass multiple filters from --vm-native-filter-match command-line flag to the data source. Previously filters from --vm-native-filter-match were only used to discover the metric names, and the metric names like __name__="metric_name" has been taken into account, while the remaining filters were ignored. For example --vm-native-src-addr={foo="bar",baz="abc"} may found metric_name{foo="bar",baz="abc"} and filter was treated as --vm-native-src-addr={__name__="metrics_name"}, e.g. foo="bar",baz="abc" filter was ignored. See this issue.

See full changelog.

How to run VictoriaMetrics

Unpack the victoria-metrics-*.tar.gz archive and read these docs.

vmutils-*.tar.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.

Check out latest releases or
releases around VictoriaMetrics/VictoriaMetrics v1.90.0

Don't miss a new VictoriaMetrics release

NewReleases is sending notifications on new releases.

Get notifications