chore(helm): update image docker.io/victoriametrics/victoria-metrics v1.119.0 → v1.120.0 #36633
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
393cd7b
->a1cb2f3
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Add the preset
:preserveSemverRanges
to your config if you don't want to pin your dependencies.Release Notes
VictoriaMetrics/VictoriaMetrics (docker.io/victoriametrics/victoria-metrics)
v1.120.0
Compare Source
v1.120.0
Released at 2025-06-20
SECURITY: upgrade Go builder from Go1.24.3 to Go1.24.4. See the list of issues addressed in Go1.24.4.
SECURITY: upgrade base docker image (Alpine) from 3.21.3 to 3.22.0. See Alpine 3.22.0 release notes.
FEATURE: all the VictoriaMetrics components: add
-http.disableKeepAlive
to disable HTTP keep-alives for incoming connections. The flag could improve load balancing among replicas behind HTTP load balancers. See #9125 and #2395 for details.FEATURE: dashboards/cluster: add panel
Partitions scheduled for re-processing
toTroubleshooting
row. It shows the amount of data scheduled for downsampling or retention filters. The new panel should help to correlate resource usage with background re-processing of partitions.FEATURE: MetricsQL: support rate_prometheus function, an equivalent to
increase_prometheus(series_selector[d]) / d
. See #8901 and #8891 for details.FEATURE: MetricsQL: respect staleness markers when calculating
rate
andincrease
functions. The new behavior will interrupt rate/increase calculation if last sample on the selected time window is a staleness marker, making the series to disappear immediately instead of slowly fading away. See more details in #8891-comment.FEATURE: vmalert: do not break vmalert process under replay mode when rule uses
query
template, but only logging a warning.FEATURE: vmalert: correct the rule evaluation timestamp if the system clock is changed during runtime. See #8790.
FEATURE: vmalert: respect group
concurrency
setting in replay mode when-replay.rulesDelay=0
. See this #7387 for details. Thanks to @BenNF for the PR #9214.FEATURE: vmsingle and
vmstorage
in VictoriaMetrics cluster: allow overriding default limits for in-memory cachestorage/metricName
via flag-storage.cacheSizeStorageMetricName
.BUGFIX: vmsingle and
vmstorage
in VictoriaMetrics cluster: fix incorrect sorting of tag filters, which led to suboptimal tag filter evaluation order and potentially degraded query performance in rare cases. See #9127 for details.BUGFIX: vmbackup, vmbackupmanager: fix server-side copying of objects for Azure Blob Storage when using managed identity for authentication. Previously, it wasn't possible to use smart backups strategy for
vmbackup
as server-side copy would fail. See #9131.BUGFIX: vmbackupmanager: increase startup healthcheck delay for storage reachability from 30 seconds to 3 minutes. This is required to avoid vmbackupmanager restarts when storage node startup take more than 30 seconds (e.g. when storage nodes stores more than 5Tb of data).
BUGFIX: VictoriaMetrics Enterprise cluster: properly include FIPS binaries in release artifacts for platforms other than windows. Previously, FIPS binaries were only included in windows release artifacts. See #9188.
BUGFIX: stream aggregation: properly calculate
rate_sum
andrate_avg
aggregations if aggregationinterval
is smaller than distance between samples timestamps. See #9017.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
8000
This PR has been generated by Renovate Bot.