Update victoriametrics/vmagent Docker tag to v1.102.0 #288
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/victoriametrics"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v1.101.0
->v1.102.0
Release Notes
VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)
v1.102.0
Compare Source
Released at 2024-07-17
Update note 1: support for snap packages was removed due to lack of interest from community. See this pull request for details. Please read about supported package types here.
Update note 2: stream aggregation config now prevents setting multiple identical outputs. For example,
outputs: [total, total]
will fail the validation phase. In addition,outputs: ["quantiles(0.5)", "quantiles(0.9)"]
will fail the validation as well - useoutputs: ["quantiles(0.5, 0.9)"]
instead.SECURITY: upgrade Go builder from Go1.22.4 to Go1.22.5. See the list of issues addressed in Go1.22.5.
SECURITY: upgrade base docker image (Alpine) from 3.20.0 to 3.20.1. See alpine 3.20.1 release notes.
FEATURE: streaming aggregation: expose the following metrics at
/metrics
page of vmagent and single-node VictoriaMetrics:vm_streamaggr_matched_samples_total
- the number of input samples matched by the corresponding aggregation rulevm_streamaggr_output_samples_total
- the number of output samples produced by the corresponding aggregation rulevm_streamaggr_samples_lag_seconds
- histogram with the lag between the current time and the timestamp seen in the aggregated input samplesFEATURE: steaming aggregation: add new labels to
vm_streamaggr_*
metrics:name
- the name of the streaming aggregation rule, which can be configured vianame
option - see these docs.url
--remoteWrite.url
for the corresponding-remoteWrite.streamAggr.config
path
- path to the corresponding streaming aggregation config fileposition
- the position of the aggregation rule in the corresponding streaming aggregation config fileFEATURE: streaming aggregation: prevent having duplicated aggregation function as
outputs
in one aggregation config. It also prevents usingoutputs: ["quantiles(0.5)", "quantiles(0.9)"]
instead ofoutputs: ["quantiles(0.5, 0.9)"]
, as the former has higher computation cost for producing the same result.FEATURE: vmagent and Single-node VictoriaMetrics: add
-graphite.sanitizeMetricName
command-line flag for sanitizing metrics ingested via Graphite protocol. See this issue.FEATURE: vmagent:
yandexcloud_sd_configs
: add support for obtaining IAM token in GCE format additionally to the deprecated Amazon EC2 IMDSv1 format. See this issue.FEATURE: vmalert: make
-replay.timeTo
optional in replay mode. When omitted, the current timestamp will be used. See this issue.FEATURE: vmauth: reduce CPU usage when proxying data ingestion requests.
FEATURE: vmauth: allow disabling request body caching with
-maxRequestBodySizeToRetry=0
. See this issue. Thanks to @shichanglin5 for the pull request.FEATURE: vmauth: allow overriding
Host
header with backend host before sending the request to the configured backend. See these docs and this issue.FEATURE: VictoriaMetrics cluster: do not retry RPC calls to vmstorage nodes if complexity limits were exceeded.
FEATURE: vmbackup and vmrestore: add support for Azure Managed Identity and default credentials lookup. See these docs and this issue for the details. Thanks to @justinrush for the pull request.
FEATURE: vmbackup and vmrestore: allow overriding Azure storage domain when performing backups via
AZURE_STORAGE_DOMAIN
environment variable. See these docs and this issue. Thanks to @justinrush for the pull request.FEATURE: vmui: show compacted result in the JSON tab for query results. See this issue.
FEATURE: dashboards: add Grafana dashboard and alerting rules for vmauth dashboard. See this issue for details.
FEATURE: vmagent dashboard:
stream aggregation
section: add graphs based on newly exposed streaming aggregation metrics.BUGFIX: MetricsQL: properly calculate histogram_quantile over Prometheus buckets with inconsistent values. See this comment and this pull request. Updates this issue.
BUGFIX: vmagent: fix panic when using multiple topics with the same name when ingesting metrics from Kafka. See this issue for the details.
BUGFIX: vmalert: fix incorrect redirection in WebUI of vmalert. See this issue and this pull request.
BUGFIX: vmgateway: properly apply read and write based rate limits. See this issue for details.
BUGFIX: vmbackupmanager: fix
vm_backup_last_run_failed
metric not being properly initialized during startup. Previously, it could imply an error even if the backup have been completed successfully. See this issue for the details.BUGFIX: vmui: fix input cursor position reset in modal settings. See this pull request.
BUGFIX: docker-compose: fix incorrect link to vmui from VictoriaMetrics plugin in Grafana.
This release also includes changes from v1.102.0-rc1 and v1.102.0-rc2 releases.
See all the changes at the 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.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
���� Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.