VictoriaMetrics v1.39.4 Release Notes
Release Date: 2020-08-09 // over 3 years ago-
🔄 Changes since v1.39.3
- 🔋 FEATURE: improve query performance and concurrency on systems with big number of CPU cores (16+ vCPUs).
- 🔋 FEATURE: limit the maximum memory usage and reduce CPU trashing on vmstorage when multiple heavy queries are executed. See #648 .
- 🔋 FEATURE: improve PromQL compatibility at https://promlabs.com/promql-compliance-test-results-victoriametrics/ . See #673 , #674 , #675
- FEATURE: vmagent: export
scrape_samples_added
per-target metric like Prometheus does. This metric may be useful for detecting targets with high churn rate for the exported metrics. See #683 - 🔋 FEATURE: vmalert: extend exported metrics. See #573 .
- 🔋 FEATURE: vmauth: properly trigger browser auth dialog. See #680
- 🔋 FEATURE: slow down concurrent searches when the number of concurrent inserts reaches the limit. This should improve data ingestion performance when heavy searches are executed. See #648 and #618
- FEATURE: export
vm_nfs_pending_dirs_to_remove
metric for monitoring the number of pending directories that couldn't be removed due to NFS lock - BUGFIX: rename
vm_cache_size_entries{type="storage/prefetchedMetricIDs"}
tovm_cache_entries{type="storage/prefetchedMetricIDs"}
to be consistent with othervm_cache_entries
metrics - BUGFIX: vmauth: add missing
-tls*
flags to*-cluster
release. See #677
How to run VictoriaMetrics
📄 Unpack the
victoria-metrics-*.tar.gz
archive and read these docs.vmutils-*.tag.gz
archive contains the following tools:🐳 The corresponding docker images are available here.
Cluster version is available here.