Update victoriametrics/vmagent Docker tag to v1.122.0 #521
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.121.0
->v1.122.0
Release Notes
VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)
v1.122.0
Compare Source
v1.122.0
Released at 2025-07-18
Update Note 1: vmsingle and
vmstorage
in VictoriaMetrics cluster: The-snapshotsMaxAge
flag default have been changed to3d
. This enables automatic deletion of snapshots older than 3 days. If you want to keep the previous behavior (never automatically deleting snapshots), please set-snapshotsMaxAge=0
. See #9344 for the details.Update Note 2: all the VictoriaMetrics Enterprise components:
-eula
command-line flag is skipped when validating VictoriaMetrics enterprise license. Instead, the-license
or-licenseFile
command-line flags must be used to provide a valid license key. See these docs for configuration examples.SECURITY: upgrade Go builder from Go1.24.4 to Go1.24.5. See the list of issues addressed in Go1.24.5.
SECURITY: upgrade base docker image (Alpine) from 3.22.0 to 3.22.1. See Alpine 3.22.1 release notes.
FEATURE: vmsingle and
vmstorage
in VictoriaMetrics cluster: enable automatic deletion of snapshots older than 3 days by default. This helps to avoid wasting disk space due to snapshots not being removed in case of backup failure. See #9344.FEATURE: vmsingle and
vmstorage
in VictoriaMetrics cluster: enable metric names stats tracker by default.FEATURE: MetricsQL: revert change on respecting staleness markers when calculating
rate
andincrease
functions described in #8891-comment. This change was introduced in v1.120.0.FEATURE: vmselect in VictoriaMetrics cluster: Increase idle timeout from
30s
to2m
and ensure at least two connections remain open betweenvmselect
andvmstorage
. The change smooth out connection usage during traffic spikes. See #9464.BUGFIX: all VictoriaMetrics components: properly set
process_cpu_cores_available
metric to respect both logical CPU cores and cgroup CPU quota. Previously, it could report incorrect values in containerized environments with no cgroup limits. See #9449. Thanks to the @fxrlv.BUGFIX: vmagent and vmsingle: properly release memory for
/target_response
API requests. Previously it could used after return and it may lead to data races and potential data loss during scraping. See #9466. Thanks to the @fxrlv.BUGFIX: vmagent: Prevent panic when re-packing a corrupted block during protocol downgrade. See #9417.
BUGFIX:
vmselect
in VictoriaMetrics cluster: fix handling of/api/v1/notifiers
and/api/v1/metadata
endpoints; previously, requests to these endpoints returned 400 Bad Request.vmsingle
was not affected.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.