Changelog History
Page 3
-
v1.40.1-cluster
September 03, 2020 -
v1.40.0 Changes
August 15, 2020๐ Changes since v1.39.4
- ๐ FEATURE: release Kubernetes operator for VictoriaMetrics - see https://github.com/VictoriaMetrics/operator .
- ๐ FEATURE: respect CPU limits set via
cgroups
. This should reduce CPU trashing and reduce memory usage for cases when VictoriaMetrics components run in containers (Docker, Kubernetes) with CPU limits. See #685 . - FEATURE: support
%{ENV_VAR}
placeholders in yaml configs in all the vm* components. Such placeholders are substituted by the corresponding environment variable values. See #583 . - ๐ FEATURE: vmagent: reduce memory usage when scraping big number of targets. Thanks to @dxtrzhang for the original idea at #688 . See #689 .
- FEATURE: reduce memory usage when exporting time series with big number of samples via
/api/v1/export
ifmax_rows_per_line
is set to non-zero value. See #685 . - ๐ FEATURE: add
-memory.allowedBytes
command-line flag for setting absolute memory limit for VictoriaMetrics caches. - ๐ FEATURE: allow passing multiple args to aggregate functions such as
avg(q1, q2, q3)
. See MetricsQL docs for details. - ๐ FEATURE: update Go builder from Go1.14.7 to Go1.15.0.
- ๐ BUGFIX: vmagent, vminsert: prevent from busy loop on repeated timeout errors when reading streams of ingested data. See #696 .
- ๐ BUGFIX: vmagent, vminsert: accept
precision=us
andprecision=ยต
query args according to https://docs.influxdata.com/influxdb/v1.8/tools/api/#write-http-endpoint . - ๐ BUGFIX: vmagent: show real timestamp and real scrape duration on
/targets
page. Previously the scrape duration could be negative when calculated scrape timestamp drifts away from the real scrape timestamp. - ๐ BUGFIX: vmagent: properly retry requests on
the server closed connection before returning the first response byte
error during service discovery API calls and target scrapes.
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. -
v1.40.0-cluster
August 15, 2020 -
v1.39.4 Changes
August 09, 2020๐ 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. -
v1.39.4-cluster
August 09, 2020 -
v1.39.3 Changes
August 05, 2020๐ Changes since v1.39.2
- FEATURE: add MetricsQL functions for calculating z-score over time range and over a group of time series. The following functions are added:
zscore_over_time(m[d])
andzscore(q) by (group)
. They may be used for anomaly detection and alerting. See more details at MetricsQL docs. - ๐ FEATURE: show
X-Forwarded-For
contents on/api/v1/status/active_queries
page. See #659 . - ๐ FEATURE: vmbackup, vmrestore: allow using
~/.aws/config
without region. Determining bucket region viaus-west-2
. See vmbackup docs for details. - ๐ FEATURE: use warning level instead of info level for logging slow queries that take longer than
-search.logSlowQueryDuration
. - ๐ BUGFIX: vmagent: prevent from closing keep-alive connections to remote storage in case
-remoteWrite.queues
is set to value bigger than 1. See #663 . - ๐ BUGFIX: reduce the maximum number of concurrent merge workers to
GOMAXPROCS/2
. The limit has been raised to GOMAXPROCS inv1.39.2
, but it has been appeared that this may increase query latency, because more CPU cores are busy with merges. - ๐ BUGFIX: do not adjust
start
andend
query args passed to/api/v1/query_range
when-search.disableCache
command-line flag is set. See #563 .
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. - FEATURE: add MetricsQL functions for calculating z-score over time range and over a group of time series. The following functions are added:
-
v1.39.3-cluster
August 05, 2020 -
v1.39.2 Changes
July 30, 2020๐ Changes since v1.39.1
- ๐ FEATURE: vmalert: add
-external.label
command-line flag to specify global labelset for all rules. This flag supposed to help to distinguish the source of alert or recording rules when more than onevmalert
runs for the same datasource or AlertManager. See #622 - โ FEATURE: show query origin (aka remote_addr or client address) on the
/api/v1/status/active_queries
page for every query. - ๐ FEATURE: add
X-Forwarded-For
header value to remoteAddr in error logs. See #659 - ๐ BUGFIX: do not prioritize merging of small parts over merging of big parts, since this doesn't work as expected. The prioritizing could lead to starvation for big part merges, which could end up in too big number of parts that must be merged into big parts.
Note : multiple big merges may be initiated after the migration from v1.39.0 or v1.39.1 to v1.39.2 or newer releases. It is OK - these merges should be finished soon. After that CPU load and disk IO usage should return to normal levels. See #648 and #618 - ๐ BUGFIX: vmagent: add missing
resp.Body.Close()
call after pushing data to remote storage. Missing body close could disable HTTP keep-alive connections, which could lead to higher load on re-establishing connections to remote storage after each request to it. See #653 - ๐ BUGFIX: vmalert,vminsert: properly preserve
db
tag from query string passed to Influx line protocol query. Previouslydb
tag from the query string wasn't added to metrics after encounteringdb
tag in the Influx line. See #653 - ๐ BUGFIX: return empty values instead of 1 from
group()
if all the time series in the group have no values at the given timestamp. This alignsgroup()
behaviour to Prometheus. - BUGFIX: improve
rate_over_sum(m[d])
handling for cases whenm
contains zero or one data point on the time ranged
. - BUGFIX: properly update
vm_slow_row_inserts_total
metric when importing multiple data points per time series at once. Previously thevm_slow_row_inserts_total
metric could be incremented multiple times for different data points per a single time series, while only a single increment is needed when inserting the first data point for this time series.
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. - ๐ FEATURE: vmalert: add
-
v1.39.2-cluster
July 30, 2020 -
v1.34.3 Changes
March 11, 2020๐ Changes since v1.34.2
- ๐ BUGFIX: properly add labels set via
-remoteWrite.label
to metrics before sending them to-remoteWrite.url
. This has been broken in v1.34.2 - ๐ BUGFIX: do not retry idempotent requests when scraping targets. See #357
- ๐ BUGFIX: properly apply
-remoteWrite.sendTimeout
to fasthttp.HostClient - ๐ BUGFIX: return 500 status code instead of 200 status code on internal errors inside
/snapshot/*
handlers - โจ ENHANCEMENT: vmagent,vminsert: add support for importing csv data via
/api/v1/import/csv
. See https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/README.md#how-to-import-csv-data - ENHANCEMENT: add optional
max_rows_per_line
query arg to/api/v1/export
for limiting the number of data points that may be exported on a single line - ENHANCEMENT: do not allow non-supported fields in
-remoteWrite.relabelConfig
andfile_sd_configs
. See #363 - โจ ENHANCEMENT: vmagent: consistently update
/targets
page after SIGHUP - โจ ENHANCEMENT: Makefile: add build and test rules with enabled race detector. These rules have
-race
suffix.
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. - ๐ BUGFIX: properly add labels set via