v1.77.2
Changes
v1.77.2
Released at 21-05-2022
-
FEATURE: vmalert: support reusable templates for rules annotations. The path to the template files can be specified via
-rule.templates
flag. See more about this feature here. Thanks to @AndrewChubatiuk for the pull request. See this feature request. -
FEATURE: vmalert: expose
vmalert_iteration_interval_seconds
metric athttp://vmalert:8880/metrics
. This metric shows the configured per-group evaluation interval. See this feature request. -
FEATURE: vmctl: add
influx-prometheus-mode
command-line flag, which allows to restore the original time series written from Prometheus into InfluxDB during data migration from InfluxDB to VictoriaMetrics. See this feature request. Thanks to @mback2k for the pull request. -
FEATURE: vmagent: add ability to specify AWS service name when issuing requests to AWS api. See this feature request. Thanks to @transacid for the pull request.
-
BUGFIX: vmagent: fix a bug, which could lead to incomplete discovery of scrape targets in Kubernetes (aka
kubernetes_sd_config
). the bug has been introduced in v1.77.0. -
BUGFIX: vmalert: support
scalar
result type in response. See this issue. -
BUGFIX: vmalert: support strings in
humanize.*
template function in the same way as Prometheus does. See this issue. -
BUGFIX: vmalert: proxy
/rules
requests to vmalert from Grafana's alerting UI. This removes errors in Grafana's UI for Grafana versions older than8.5.*
. See this issue -
BUGFIX: vmalert: do not add
/api/v1/query
suffix to-datasource.url
if-remoteRead.disablePathAppend
command-line flag is set. Previously this flag was applied only to-remoteRead.url
, which could confuse users. -
BUGFIX: vmalert: prevent from possible resource leak on config update, which could lead to the slowdown of
vmalert
over time. See this pull request. -
BUGFIX: MetricsQL: do not return values from label_value() function if the original time series has no values at the selected timestamps.
-
BUGFIX: VictoriaMetrics cluster: limit the number of concurrently established connections from vmselect to vmstorage. This should prevent from potentially high spikes in the number of established connections after temporary slowdown in connection handshake procedure between vmselect and vmstorage because of spikes in workload. See this issue.
-
BUGFIX: vmctl: fix build for Solaris / SmartOS. See this issue.
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.