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

Update victoriametrics/vmagent Docker tag to v1.132.0 #611

Merged
AverageMarcus merged 1 commits from renovate/victoriametrics into master 2025-12-16 08:15:20 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate commented 2025-12-16 03:08:03 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
victoriametrics/vmagent minor v1.131.0 -> v1.132.0

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)

v1.132.0

Compare Source

v1.132.0

Released at 2025-12-12

  • SECURITY: upgrade Go builder from Go1.25.4 to Go1.25.5. See the list of issues addressed in Go1.25.5.

  • FEATURE: dashboards/operator: add panels for flags and configuration parameters values. See #​1341-operator.

  • FEATURE: dashboards/single, dashboards/cluster: add Memory usage breakdown panels to Drilldown section. These panels help analyze overall memory distribution and diagnose anomalies or leaks. See #​10139.

  • FEATURE: dashboards/single, dashboards/cluster: add Major page faults rate panels to Troubleshooting and Drilldown sections. See #​9974

  • FEATURE: Influx line protocol data ingestion: reduce CPU and memory usage when parsing Influx lines with escaped chars - ,, \\, = and . See #​10053.

  • FEATURE: OpenTelemetry data ingestion: reduce CPU usage when parsing metrics received via OpenTelemetry protocol. See 293d809.

  • FEATURE: vmagent: add a warning to active targets panel when -dropOriginalLabels=true is set (default), indicating that some debug information may not be available. See #​9901.

  • FEATURE: vmbackup, vmrestore, vmbackupmanager: add support for SSE KMS Key ID and ACL for use with S3-compatible storages. See #​9796. Thanks to @​sylr for the contribution.

  • FEATURE: vminsert in VictoriaMetrics cluster: improve slowness-based rerouting logic. Now rerouting occurs only for the slowest storage node, and only if the cluster as a whole has enough available capacity to handle the additional load. This prevents unnecessary rerouting when the entire cluster is under heavy load or avoid "rerouting storm". The logic is disabled by default; to enable set -disableRerouting=false. See #​9890 for details.

  • FEATURE: vmsingle, vmagent: add support of Zabbix Connector ingestion format. See #​6087. Thanks to @​SinotQ for the contribution.

  • FEATURE: vmui: improve legend auto-collapse with a higher threshold, a warning message, and a toggle option. See #​10075.

  • BUGFIX: all VictoriaMetrics components: properly validate remaining system memory limit. Previously it could have negative values. See #​10083.

  • BUGFIX: vmalert: don't increase vmalert_alerting_rules_errors_total/vmalert_recording_rules_errors_total for request context cancellation, which may occur during graceful shutdown or group configuration update. See #​10128. Thanks to @​tIGO for the contribution.

  • BUGFIX: vmauth: verify backend network reachability with a TCP dial before marking it healthy. Previously, backends were auto-restored after -failTimeout even if the network was still unreachable, causing requests to hang repeatedly. vmauth now performs a 1s TCP dial check before returning a backend to the healthy pool. See #​9997.

  • BUGFIX: vmctl: properly handle process termination during prompt confirmation. Previously, termination signal was ignored and process was still waiting for user input. See #​10104.

  • BUGFIX: vmgateway: properly recover from proxy requests errors. Previously, vmgateway may return empty response.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: report stats only for most utilized instances of indexdb/tagFiltersToMetricIDs and indexdb/date_metricID caches. This makes it clear when a cache is full and an action needs to be taken (such as adding more memory or adjusting cache limits). See #​10131.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: disable rollup result cache for instant queries that contain rate function with a lookbehind window larger than -search.minWindowForInstantRollupOptimization. Previously, utilizing the cache might yield incorrect results when time series samples are not continuous. See #​10098.

  • BUGFIX: vmstorage in VictoriaMetrics cluster: do not wait after closing the last connections from vminsert when shutting down. The bug was introduced in #​9487. See #​10136.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: dateMetricIDCache metrics were renamed to follow the naming pattern used for other caches. vm_date_metric_id_cache_resets_total becomes vm_cache_resets_total{type="indexdb/date_metricID"} and vm_date_metric_id_cache_syncs_total became vm_cache_syncs_total{type="indexdb/date_metricID"}. See #​10152.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: fix performance degradation caused by redundant indexdb lookups at the start of each hour. See #​10114. Thanks to @​fxrlv for the contribution.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: fix potential datapoint lost in response when query at the last millisecond of the day. See #​9804.

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.131.0` -> `v1.132.0` | --- ### Release Notes <details> <summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)</summary> ### [`v1.132.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.132.0) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.131.0...v1.132.0) ##### [v1.132.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.132.0) Released at 2025-12-12 - SECURITY: upgrade Go builder from Go1.25.4 to Go1.25.5. See [the list of issues addressed in Go1.25.5](https://github.com/golang/go/issues?q=milestone%3AGo1.25.5%20label%3ACherryPickApproved). - FEATURE: [dashboards/operator](https://grafana.com/grafana/dashboards/17869-victoriametrics-operator/): add panels for flags and configuration parameters values. See [#&#8203;1341-operator](https://github.com/VictoriaMetrics/operator/issues/1341). - FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229), [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add `Memory usage breakdown` panels to `Drilldown` section. These panels help analyze overall memory distribution and diagnose anomalies or leaks. See [#&#8203;10139](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10139). - FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229), [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add `Major page faults rate` panels to `Troubleshooting` and `Drilldown` sections. See [#&#8203;9974](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9974) - FEATURE: [Influx line protocol data ingestion](https://docs.victoriametrics.com/victoriametrics/integrations/influxdb/): reduce CPU and memory usage when parsing Influx lines with escaped chars - `,`, `\\`, `=` and ` `. See [#&#8203;10053](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10053). - FEATURE: [OpenTelemetry data ingestion](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#sending-data-via-opentelemetry): reduce CPU usage when parsing metrics received via OpenTelemetry protocol. See [293d809](https://github.com/VictoriaMetrics/VictoriaMetrics/commit/293d80910ce14c247e943c63cd19467df5767c3c). - FEATURE: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): add a warning to active targets panel when `-dropOriginalLabels=true` is set (default), indicating that some debug information may not be available. See [#&#8203;9901](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9901). - FEATURE: [vmbackup](https://docs.victoriametrics.com/victoriametrics/vmbackup/), [vmrestore](https://docs.victoriametrics.com/victoriametrics/vmrestore/), [vmbackupmanager](https://docs.victoriametrics.com/victoriametrics/vmbackupmanager/): add support for SSE KMS Key ID and ACL for use with S3-compatible storages. See [#&#8203;9796](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9796). Thanks to [@&#8203;sylr](https://github.com/sylr) for the contribution. - FEATURE: `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): improve slowness-based rerouting logic. Now rerouting occurs only for the slowest storage node, and only if the cluster as a whole has enough available capacity to handle the additional load. This prevents unnecessary rerouting when the entire cluster is under heavy load or avoid "rerouting storm". The logic is disabled by default; to enable set `-disableRerouting=false`. See [#&#8203;9890](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9890) for details. - FEATURE: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/), [vmagent](https://docs.victoriametrics.com/vmagent/): add support of [Zabbix Connector](https://docs.victoriametrics.com/victoriametrics/integrations/zabbixconnector/#send-data-from-zabbix-connector) ingestion format. See [#&#8203;6087](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6087). Thanks to [@&#8203;SinotQ](https://github.com/SinotQ) for the contribution. - FEATURE: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): improve legend auto-collapse with a higher threshold, a warning message, and a toggle option. See [#&#8203;10075](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10075). - BUGFIX: all VictoriaMetrics components: properly validate remaining system memory limit. Previously it could have negative values. See [#&#8203;10083](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10083). - BUGFIX: [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/): don't increase `vmalert_alerting_rules_errors_total`/`vmalert_recording_rules_errors_total` for request context cancellation, which may occur during graceful shutdown or group configuration update. See [#&#8203;10128](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10128). Thanks to [@&#8203;tIGO](https://github.com/tIGO) for the contribution. - BUGFIX: [vmauth](https://docs.victoriametrics.com/victoriametrics/vmauth/): verify backend network reachability with a TCP dial before marking it healthy. Previously, backends were auto-restored after `-failTimeout` even if the network was still unreachable, causing requests to hang repeatedly. `vmauth` now performs a 1s TCP dial check before returning a backend to the healthy pool. See [#&#8203;9997](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9997). - BUGFIX: [vmctl](https://docs.victoriametrics.com/victoriametrics/vmctl/): properly handle process termination during prompt confirmation. Previously, termination signal was ignored and process was still waiting for user input. See [#&#8203;10104](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10104). - BUGFIX: [vmgateway](https://docs.victoriametrics.com/victoriametrics/vmgateway/): properly recover from proxy requests errors. Previously, vmgateway may return empty response. - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): report stats only for most utilized instances of `indexdb/tagFiltersToMetricIDs` and `indexdb/date_metricID` caches. This makes it clear when a cache is full and an action needs to be taken (such as adding more memory or adjusting cache limits). See [#&#8203;10131](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10131). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): disable rollup result cache for [instant queries](https://docs.victoriametrics.com/keyConcepts.html#instant-query) that contain [`rate`](https://docs.victoriametrics.com/MetricsQL.html#rate) function with a lookbehind window larger than `-search.minWindowForInstantRollupOptimization`. Previously, utilizing the cache might yield incorrect results when time series samples are not continuous. See [#&#8203;10098](https://github.com/VictoriaMetrics/victoriaMetrics/issues/10098). - BUGFIX: `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): do not wait after closing the last connections from vminsert when shutting down. The bug was introduced in [#&#8203;9487](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9487). See [#&#8203;10136](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10136). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): `dateMetricIDCache` metrics were renamed to follow the naming pattern used for other caches. `vm_date_metric_id_cache_resets_total` becomes `vm_cache_resets_total{type="indexdb/date_metricID"}` and `vm_date_metric_id_cache_syncs_total` became `vm_cache_syncs_total{type="indexdb/date_metricID"}`. See [#&#8203;10152](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10152). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): fix performance degradation caused by redundant indexdb lookups at the start of each hour. See [#&#8203;10114](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10114). Thanks to [@&#8203;fxrlv](https://github.com/fxrlv) for the contribution. - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): fix potential datapoint lost in response when query at the last millisecond of the day. See [#&#8203;9804](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9804). </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:eyJjcmVhdGVkSW5WZXIiOiI0Mi41Ny4xIiwidXBkYXRlZEluVmVyIjoiNDIuNTcuMSIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6W119-->
renovate added 1 commit 2025-12-16 03:08:03 +00:00
Update victoriametrics/vmagent Docker tag to v1.132.0 e01ce9d8f8
AverageMarcus merged commit f7b9c1a4e8 into master 2025-12-16 08:15:20 +00:00
AverageMarcus deleted branch renovate/victoriametrics 2025-12-16 08:15:20 +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#611
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?