v1.82.0
版本发布时间: 2022-10-07 09:20:29
VictoriaMetrics/VictoriaMetrics最新发布版本:v1.101.0(2024-04-26 17:06:08)
Changes
v1.82.0
Released at 07-10-2022
It isn't recommended to use VictoriaMetrics and vmagent v1.82.0 because of the bug, which may result in incorrect query results and relabeling results. Upgrade to v1.82.1 instead.
Update note 1: this release changes data format for /api/v1/export/native in incompatible way, so it cannot be imported into older version of VictoriaMetrics via /api/v1/import/native.
Update note 2: vmalert changes default value for command-line flag -datasource.queryStep
from 0s
to 5m
. The change supposed to improve reliability of the rules evaluation when evaluation interval is lower than scraping interval.
Update note 3: vm_account_id
and vm_project_id
labels must be passed to tcp-based Graphite
, InfluxDB
and OpenTSDB
endpoints
at VictoriaMetrics cluster instead of undocumented
VictoriaMetrics_AccountID
and VictoriaMetrics_ProjectID
labels when writing samples to the needed tenant.
See these docs for details.
-
FEATURE: VictoriaMetrics cluster: support specifying tenant ids via
vm_account_id
andvm_project_id
labels. See these docs and this feature request. -
FEATURE: vmagent: improve relabeling performance by up to 3x for non-trivial
regex
values such as([^:]+):.+
, which can be used for extracting ahost
part fromhost:port
label value. -
FEATURE: MetricsQL: improve performance by up to 4x for queries containing non-trivial
regex
filters such as{path=~"/foo/.+|/bar"}
. -
FEATURE: improve performance scalability on systems with many CPU cores for /federate and /api/v1/export/... endpoints.
-
FEATURE: sanitize metric names for data ingested via DataDog protocol according to DataDog metric naming. The behaviour can be disabled by passing
-datadog.sanitizeMetricName=false
command-line flag. Thanks to @PerGon for the pull request. -
FEATURE: add
-usePromCompatibleNaming
command-line flag to vmagent, to single-node VictoriaMetrics and tovminsert
component of VictoriaMetrics cluster. This flag can be used for normalizing the ingested metric names and label names to Prometheus-compatible form. If this flag is set, then all the chars unsupported by Prometheus are replaced with_
chars in metric names and labels of the ingested samples. See this feature request. -
FEATURE: accept whitespace in metric names and tags ingested via Graphite plaintext protocol according to the specs. See this issue.
-
FEATURE: check the correctess of raw sample timestamps stored on disk when reading them. This reduces the probability of possible silent corruption of the data stored on disk. This should help this and this issue.
-
FEATURE: atomically delete directories with snapshots, parts and partitions at storage level. Previously such directories can be left in partially deleted state when the deletion operation was interrupted by unclean shutdown. This may result in
cannot open file ...: no such file or directory
error on the next start. The probability of this error was quite high when NFS or EFS was used as persistent storage for VictoriaMetrics data. See this issue. -
FEATURE: set the
start
arg toend - 5 minutes
if isn't passed explicitly to /api/v1/labels and /api/v1/label/.../values. See this pull request. -
FEATURE: allow to define the minimum TLS version to use when accepting https requests to VictoriaMetrics components if
-tls
command-line flag is set. The minimum TLS version can be set via-tlsMinVersion
command-line flag. See this feature request. -
FEATURE: vmctl: add
vm-native-step-interval
command line flag forvm-native
mode. New option allows splitting the import process into chunks by time interval. This helps migrating data sets with high churn rate and provides better control over the process. See feature request. -
FEATURE: vmui: add
top queries
tab, which shows various stats for recently executed queries. See these docs and this feature request. -
FEATURE: vmui: move the "Execute Query" and "Add Query" buttons below the query fields, change icon for remove query. See this issue.
-
FEATURE: vmui: set the maximum number of queries to 4, remove multi Y-axes, left one for all queries and dotted lines to indicate queries in the graph. See this issue.
-
FEATURE: vmalert: add
debug
mode to the alerting rule settings for printing additional information into logs during evaluation. Seedebug
param in alerting rule config. -
FEATURE: vmalert: add experimental feature for displaying last 10 states of the rule (recording or alerting) evaluation. The state is available on the Rule page, which can be opened by clicking on
Details
link next to Rule's name on the/groups
page. -
FEATURE: vmalert: allow using extra labels in annotiations. See this feature request.
-
FEATURE: vmalert: allow configuring authorization params per list of targets in vmalert's notifier config for
static_configs
. See this issue. -
FEATURE: vmalert: allow using
{{$labels}}
for templating in command-line flag-external.alert.source
. The change supposed to provide additional flexibility for generating alert's source link based on labels values. -
FEATURE: vmalert: add
vm_account_id
andvm_project_id
labels to results of alerting and recording rules if-clusterMode
is enabled. This improves multitenant support in vmalert. -
FEATURE: vmagent: minimize the time needed for reading large responses from scrape targets in stream parsing mode. This should reduce scrape durations for such targets as kube-state-metrics running in a big Kubernetes cluster.
-
FEATURE: MetricsQL: add sort_by_label_numeric and sort_by_label_numeric_desc functions for numeric sort of input time series by the specified labels. See this feature request.
-
FEATURE: vmbackup and vmrestore: retry GCS operations for up to 3 minutes on temporary failures. See this issue.
-
FEATURE: vmbackup: add support for saving / restoring backups to / from Azure blob storage. See this feature request.
-
FEATURE: vmbackupmanager: expose
vm_backup_in_flight
metric, which can be used for determining which backup types - latest, hourly, daily, weekly or monthly - are currently executed. -
FEATURE: vmgateway: add ability to extract JWT authorization token from non-standard HTTP header by passing it via
-auth.httpHeader
command-line flag. See this feature request. -
FEATURE: vmagent: expose
__meta_ec2_region
label for ec2_sd_config in the same way as Prometheus 2.39 does. -
FEATURE: vmagent: accept data ingestion requests via paths starting from
/prometheus
prefix in the same way as VictoriaMetrics does. For example,vmagent
now accepts Prometheusremote_write
data via both/api/v1/write
and/prometheus/api/v1/write
. This simplifies switching between single-node VictoriaMetrics andvmagent
. -
FEATURE: vmagent: add
external_labels
fromglobal
section at-promscrape.config
after the relabeling is applied to scraped metrics. This aligns with Prometheus behaviour. Previously theexternal_labels
were added to scrape targets, so they could be modified during relabeling. See this issue. -
FEATURE: vmagent: allow specifying per-
-remoteWrite.url
limits for on-disk size for pending data via-remoteWrite.maxDiskUsagePerURL
command-line flag. Thanks to @rbizos for the pull request. -
FEATURE: VictoriaMetrics cluster: log clear error when multiple identical
-storageNode
command-line flags are passed tovmselect
or tovminsert
. Previously these components were crashed with cryptic panicmetric ... is already registered
in this case. See this issue. -
BUGFIX: do not export stale metrics via /federate api after the staleness markers. Previously such metrics were exported with
NaN
values. this could break some setups. See this issue. -
BUGFIX: export ininity numbers as
"Infinity"
strings at /api/v1/export, so they can be parsed by standard JSON parsers. Previously infinity numbers were exported asInf
values, which couldn't be parsed by standard JSON parsers. See this issue. -
BUGFIX: vmauth: properly handle request paths ending with
/
such as/vmui/
. Previouslyvmui
was dropping the traling/
, which could prevent from usingvmui
viavmauth
. See this issue. -
BUGFIX: vmagent: properly encode query params for aws signed requests, use
%20
instead of+
as api requires. See this issue. -
BUGFIX: vmagent: properly parse relabel config when regex ending with escaped
$
. See this issue. -
BUGFIX: MetricsQL: properly calculate
rate_over_sum(m[d])
assum_over_time(m[d])/d
. Previously thesum_over_time(m[d])
could be improperly divided by smaller thand
time range. See rate_over_sum() docs and this issue. -
BUGFIX: MetricsQL: properly calculate
increase(m[d])
over slow-changing counters with values smaller than 100. Previously increase could return unexpectedly big results in this case. See the related issue and this pull request. -
BUGFIX: MetricsQL: ignore empty series when applying limit_offset. It should improve queries with additional filters by value in expressions like
limit_offset(1,1, foo > 1)
. -
BUGFIX: MetricsQL: properly calculate quantiles_over_time when the lookbehind window contains only a single sample. Previously an empty result was incorrectly returned in this case.
-
BUGFIX: vmui: fix
RangeError: Maximum call stack size exceeded
error when the query returns too many data points atTable
view. See this pull request. -
BUGFIX: vmui: fix workaround for adding more queries via URL. See this issue.
-
BUGFIX: vmalert: re-evaluate annotations per each alert evaluation. Previously, annotations were evaluated only on alert's value change. This could result in stale annotations in some cases described in this pull request.
-
BUGFIX: prevent from excessive CPU usage when the storage enters read-only mode. The previous fix in v1.81.0 wasn't complete.
-
BUGFIX: vmalert: change default value for command-line flag
-datasource.queryStep
from0s
to5m
. Paramstep
is added by vmalert to every rule evaluation request sent to datasource. Before this change,step
was equal to group's evaluation interval by default. Paramstep
for instant queries defines how far VM can look back for the last written data point. The change supposed to improve reliability of the rules evaluation when evaluation interval is lower than scraping interval. -
BUGFIX: properly calculate
vm_rows_scanned_per_query
histogram exported at/metrics
page ofvmselect
and single-node VictoriaMetrics. Previously it could return misleadingly high numbers for rollup functions, which scan only a few samples on the provided lookbehind window in square brackets. For example,increase(m[1d])
always scans only 2 rows (akaraw samples
) per each returned time series.
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.
1、 victoria-metrics-darwin-amd64-v1.82.0-enterprise.tar.gz 9.46MB
2、 victoria-metrics-darwin-amd64-v1.82.0-enterprise_checksums.txt 210B
3、 victoria-metrics-darwin-amd64-v1.82.0.tar.gz 9.12MB
4、 victoria-metrics-darwin-amd64-v1.82.0_checksums.txt 199B
5、 victoria-metrics-darwin-arm64-v1.82.0-enterprise.tar.gz 9.09MB
6、 victoria-metrics-darwin-arm64-v1.82.0-enterprise_checksums.txt 210B
7、 victoria-metrics-darwin-arm64-v1.82.0.tar.gz 8.76MB
8、 victoria-metrics-darwin-arm64-v1.82.0_checksums.txt 199B
9、 victoria-metrics-freebsd-amd64-v1.82.0-cluster.tar.gz 19MB
10、 victoria-metrics-freebsd-amd64-v1.82.0-cluster_checksums.txt 361B
11、 victoria-metrics-freebsd-amd64-v1.82.0-enterprise-cluster.tar.gz 19.56MB
12、 victoria-metrics-freebsd-amd64-v1.82.0-enterprise-cluster_checksums.txt 372B
13、 victoria-metrics-freebsd-amd64-v1.82.0-enterprise.tar.gz 9.61MB
14、 victoria-metrics-freebsd-amd64-v1.82.0-enterprise_checksums.txt 211B
15、 victoria-metrics-freebsd-amd64-v1.82.0.tar.gz 9.26MB
16、 victoria-metrics-freebsd-amd64-v1.82.0_checksums.txt 200B
17、 victoria-metrics-linux-amd64-v1.82.0-cluster.tar.gz 18.98MB
18、 victoria-metrics-linux-amd64-v1.82.0-cluster_checksums.txt 359B
19、 victoria-metrics-linux-amd64-v1.82.0-enterprise-cluster.tar.gz 19.52MB
20、 victoria-metrics-linux-amd64-v1.82.0-enterprise-cluster_checksums.txt 370B
21、 victoria-metrics-linux-amd64-v1.82.0-enterprise.tar.gz 9.43MB
22、 victoria-metrics-linux-amd64-v1.82.0-enterprise_checksums.txt 209B
23、 victoria-metrics-linux-amd64-v1.82.0.tar.gz 9.1MB
24、 victoria-metrics-linux-amd64-v1.82.0_checksums.txt 198B
25、 victoria-metrics-linux-arm-v1.82.0-enterprise.tar.gz 9.5MB
26、 victoria-metrics-linux-arm-v1.82.0-enterprise_checksums.txt 207B
27、 victoria-metrics-linux-arm-v1.82.0.tar.gz 9.15MB
28、 victoria-metrics-linux-arm-v1.82.0_checksums.txt 196B
29、 victoria-metrics-linux-arm64-v1.82.0-cluster.tar.gz 17.23MB
30、 victoria-metrics-linux-arm64-v1.82.0-cluster_checksums.txt 359B
31、 victoria-metrics-linux-arm64-v1.82.0-enterprise-cluster.tar.gz 17.72MB
32、 victoria-metrics-linux-arm64-v1.82.0-enterprise-cluster_checksums.txt 370B
33、 victoria-metrics-linux-arm64-v1.82.0-enterprise.tar.gz 8.6MB
34、 victoria-metrics-linux-arm64-v1.82.0-enterprise_checksums.txt 209B
35、 victoria-metrics-linux-arm64-v1.82.0.tar.gz 8.3MB
36、 victoria-metrics-linux-arm64-v1.82.0_checksums.txt 198B
37、 victoria-metrics-openbsd-amd64-v1.82.0-cluster.tar.gz 18.95MB
38、 victoria-metrics-openbsd-amd64-v1.82.0-cluster_checksums.txt 361B
39、 victoria-metrics-openbsd-amd64-v1.82.0-enterprise-cluster.tar.gz 19.5MB
40、 victoria-metrics-openbsd-amd64-v1.82.0-enterprise-cluster_checksums.txt 372B
41、 victoria-metrics-openbsd-amd64-v1.82.0-enterprise.tar.gz 9.59MB
42、 victoria-metrics-openbsd-amd64-v1.82.0-enterprise_checksums.txt 211B
43、 victoria-metrics-openbsd-amd64-v1.82.0.tar.gz 9.23MB
44、 victoria-metrics-openbsd-amd64-v1.82.0_checksums.txt 200B
45、 vmutils-darwin-amd64-v1.82.0-enterprise.tar.gz 71.95MB
46、 vmutils-darwin-amd64-v1.82.0-enterprise_checksums.txt 755B
47、 vmutils-darwin-amd64-v1.82.0.tar.gz 53.39MB
48、 vmutils-darwin-amd64-v1.82.0_checksums.txt 576B
49、 vmutils-darwin-arm64-v1.82.0-enterprise.tar.gz 69.29MB
50、 vmutils-darwin-arm64-v1.82.0-enterprise_checksums.txt 755B
51、 vmutils-darwin-arm64-v1.82.0.tar.gz 51.4MB
52、 vmutils-darwin-arm64-v1.82.0_checksums.txt 576B
53、 vmutils-freebsd-amd64-v1.82.0-enterprise.tar.gz 72.58MB
54、 vmutils-freebsd-amd64-v1.82.0-enterprise_checksums.txt 756B
55、 vmutils-freebsd-amd64-v1.82.0.tar.gz 53.88MB
56、 vmutils-freebsd-amd64-v1.82.0_checksums.txt 577B
57、 vmutils-linux-amd64-v1.82.0-enterprise.tar.gz 75.69MB
58、 vmutils-linux-amd64-v1.82.0-enterprise_checksums.txt 754B
59、 vmutils-linux-amd64-v1.82.0.tar.gz 54.02MB
60、 vmutils-linux-amd64-v1.82.0_checksums.txt 575B
61、 vmutils-linux-arm-v1.82.0-enterprise.tar.gz 69.73MB
62、 vmutils-linux-arm-v1.82.0-enterprise_checksums.txt 752B
63、 vmutils-linux-arm-v1.82.0.tar.gz 51.82MB
64、 vmutils-linux-arm-v1.82.0_checksums.txt 573B
65、 vmutils-linux-arm64-v1.82.0-enterprise.tar.gz 68.07MB
66、 vmutils-linux-arm64-v1.82.0-enterprise_checksums.txt 754B
67、 vmutils-linux-arm64-v1.82.0.tar.gz 50.41MB
68、 vmutils-linux-arm64-v1.82.0_checksums.txt 575B
69、 vmutils-openbsd-amd64-v1.82.0-enterprise.tar.gz 72.43MB
70、 vmutils-openbsd-amd64-v1.82.0-enterprise_checksums.txt 756B
71、 vmutils-openbsd-amd64-v1.82.0.tar.gz 53.78MB
72、 vmutils-openbsd-amd64-v1.82.0_checksums.txt 577B
73、 vmutils-windows-amd64-v1.82.0-enterprise.zip 17.58MB
74、 vmutils-windows-amd64-v1.82.0-enterprise_checksums.txt 595B
75、 vmutils-windows-amd64-v1.82.0.zip 14.76MB