AverageMarcus/cluster.fun
1
0
Fork 0
Code Issues 1 Pull Requests 2 Releases Activity

Update victoriametrics/vmagent Docker tag to v1.120.0 #503

Merged
AverageMarcus merged 1 commits from renovate/victoriametrics into master 2025-06-24 05:42:29 +00:00
Conversation 0 Commits 1 Files Changed 2 +2 -2
renovate commented 2025-06-24 03:19:39 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
victoriametrics/vmagent minor v1.119.0 -> v1.120.0

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)

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 to Troubleshooting 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 and increase 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 cache storage/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 and rate_avg aggregations if aggregation interval 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: 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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [victoriametrics/vmagent](https://github.com/VictoriaMetrics/VictoriaMetrics) | minor | `v1.119.0` -> `v1.120.0` | --- ### Release Notes <details> <summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)</summary> ### [`v1.120.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.120.0) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.119.0...v1.120.0) ##### [v1.120.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/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](https://github.com/golang/go/issues?q=milestone%3AGo1.24.4+label%3ACherryPickApproved). - SECURITY: upgrade base docker image (Alpine) from 3.21.3 to 3.22.0. See [Alpine 3.22.0 release notes](https://alpinelinux.org/posts/Alpine-3.22.0-released.html). - 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 [#&#8203;9125](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9125) and [#&#8203;2395](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/2395) for details. - FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panel `Partitions scheduled for re-processing` to `Troubleshooting` row. It shows the amount of data scheduled for [downsampling](https://docs.victoriametrics.com/#downsampling) or [retention filters](https://docs.victoriametrics.com/#retention-filters). The new panel should help to correlate resource usage with background re-processing of partitions. - FEATURE: [MetricsQL](https://docs.victoriametrics.com/victoriametrics/metricsql/): support [rate\_prometheus](https://docs.victoriametrics.com/victoriametrics/metricsql/#rate_prometheus) function, an equivalent to `increase_prometheus(series_selector[d]) / d`. See [#&#8203;8901](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8901) and [#&#8203;8891](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8891) for details. - FEATURE: [MetricsQL](https://docs.victoriametrics.com/victoriametrics/metricsql/): respect staleness markers when calculating `rate` and `increase` functions. The new behavior will interrupt rate/increase calculation if last sample on the selected time window is a [staleness marker](https://docs.victoriametrics.com/victoriametrics/vmagent/#prometheus-staleness-markers), making the series to disappear immediately instead of slowly fading away. See more details in [#&#8203;8891-comment](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8891#issuecomment-2875542721). - FEATURE: [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/): do not break vmalert process under replay mode when rule uses `query` template, but only logging a warning. - FEATURE: [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/): correct the rule evaluation timestamp if the system clock is changed during runtime. See [#&#8203;8790](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8790). - FEATURE: [vmalert](https://docs.victoriametrics.com/vmalert/): respect [group](https://docs.victoriametrics.com/victoriametrics/vmalert/#groups) `concurrency` setting in [replay mode](https://docs.victoriametrics.com/victoriametrics/vmalert/#rules-backfilling) when `-replay.rulesDelay=0`. See this [#&#8203;7387](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7387) for details. Thanks to [@&#8203;BenNF](https://github.com/BenNF) for the [PR #&#8203;9214](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9214). - FEATURE: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): allow overriding default limits for in-memory cache `storage/metricName` via flag `-storage.cacheSizeStorageMetricName`. - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): fix incorrect sorting of tag filters, which led to suboptimal tag filter evaluation order and potentially degraded query performance in rare cases. See [#&#8203;9127](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9127) for details. - BUGFIX: [vmbackup](https://docs.victoriametrics.com/vmbackup/), [vmbackupmanager](https://docs.victoriametrics.com/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](https://docs.victoriametrics.com/victoriametrics/vmbackup/#smart-backups) strategy for `vmbackup` as server-side copy would fail. See [#&#8203;9131](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9131). - BUGFIX: [vmbackupmanager](https://docs.victoriametrics.com/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](https://docs.victoriametrics.com/enterprise.html) cluster: properly include FIPS binaries in release artifacts for platforms other than windows. Previously, FIPS binaries were only included in windows release artifacts. See [#&#8203;9188](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9188). - BUGFIX: [stream aggregation](https://docs.victoriametrics.com/victoriametrics/stream-aggregation/): properly calculate `rate_sum` and `rate_avg` aggregations if aggregation `interval` is smaller than distance between samples timestamps. See [#&#8203;9017](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9017). </details> --- ### 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS42LjQiLCJ1cGRhdGVkSW5WZXIiOiI0MS42LjQiLCJ0YXJnZXRCcmFuY2giOiJtYXN0ZXIiLCJsYWJlbHMiOltdfQ==-->
renovate added 1 commit 2025-06-24 03:19:39 +00:00
Update victoriametrics/vmagent Docker tag to v1.120.0 642b90d7b5
AverageMarcus merged commit 1cd38b1ff2 into master 2025-06-24 05:42:29 +00:00
AverageMarcus deleted branch renovate/victoriametrics 2025-06-24 05:42:29 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
renovate AverageMarcus
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: AverageMarcus/cluster.fun#503
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?