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

Update victoriametrics/vmagent Docker tag to v1.133.0 #625

Merged
AverageMarcus merged 1 commits from renovate/victoriametrics into master 2026-01-06 09:59:02 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate commented 2026-01-06 03:07:41 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
victoriametrics/vmagent minor v1.132.0 → v1.133.0

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)

v1.133.0

Compare Source

v1.133.0

Released at 2026-01-02

Update Note 1: vmsingle and vmstorage in VictoriaMetrics cluster: Upgrading to per-partition index requires registering all active time series. Expect slow down of data ingestion and queries during upgrade roll-out. This is a one-time operation. Additionally, for users with retention periods shorter than 1 month the disk usage may increase.

  • SECURITY: upgrade base docker image (Alpine) from 3.22.2 to 3.23.2. See Alpine 3.23.2 release notes.

  • FEATURE: vmagent and vmsingle: add support for global sampleLimit setting. This allows users to efficiently limit the number of samples accepted per scrape target. This also ensures target-level sample_limit can correctly override the global setting. See #​10145. Thanks to @​kobylyanskiy for the contribution.

  • FEATURE: vmauth: expose vmauth_user_request_backend_requests_total and vmauth_unauthorized_user_request_backend_requests_total metrics, which track the number of requests sent to backends. These counts may exceed vmauth_user_requests_total and vmauth_unauthorized_user_requests_total when requests are retried across multiple backends. See #​10171.

  • FEATURE: vmauth: expose vmauth_user_request_errors_total and vmauth_unauthorized_user_request_errors_total metrics, which track the number of user request errors. See #​10188.

  • FEATURE: vmauth: add -maxQueueDuration command-line flag for waiting until the incoming request could be executed if -maxConcurrentRequests are already exceeded. This should help with graceful handling of a short spike in the number of concurrent requests without leading to a retry storm. See #​10078.

  • FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: introduce per-partition index. This should reduce disk space occupied by indexDBs as they get deleted along with the corresponding partitions once those partitions become outside the retention window. Read more about the motivation behind this feature at #​7599 and what to expect at #​8134.

  • BUGFIX: vmagent and vmsingle: properly add exported_ prefix to scraped metrics that have the same names as auto-generated metrics. Previously, some auto-generated metrics were not recognized, so scraped metrics with the same names could overwrite them. See #​10197. Thanks to @​fxrlv for the contribution.

  • BUGFIX: vmagent: fix vmagent_rows_inserted_total{type="newrelic"} metric to correctly count samples. See #​10191. Thanks to @​fxrlv for the contribution.

  • BUGFIX: vmauth: fix vmauth_user_request_backend_errors_total and vmauth_unauthorized_user_request_backend_errors_total to only reflect backend request errors. Previously, these counters could be overcounted with user request error. See #​10177.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: rotate dateMetricIDCache instead of resetting it. This should make the eviction less aggressive. Since the cache does not have fixed max size anymore the -storage.cacheSizeIndexDBDateMetricID flag has been removed. See #​10064 and PR #​10169.

  • BUGFIX: vmsingle: properly add metrics metadata scraped with promscrape.config and selfScrapeInterval. See #​10175.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: fix stats collection for indexdb/tagFiltersToMetricIDs, indexdb/metricID, and indexdb/date_metricID caches. As per PR #​10131, the stats is collected for most utilized instance only, but if the size of all instances is 0 then the stats won't be collected at all. This may result in max cache size alternating between the actual value and 0. See #​10204 and #​10230.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: properly proxy requests to vmalert when -vmalert.proxyURL flag is set. See #​10178.

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.132.0` → `v1.133.0` | --- ### Release Notes <details> <summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)</summary> ### [`v1.133.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.133.0) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.132.0...v1.133.0) ##### [v1.133.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.133.0) Released at 2026-01-02 **Update Note 1:** [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): Upgrading to per-partition index requires registering all active time series. Expect slow down of data ingestion and queries during upgrade roll-out. This is a one-time operation. Additionally, for users with retention periods shorter than 1 month the disk usage may increase. - SECURITY: upgrade base docker image (Alpine) from 3.22.2 to 3.23.2. See [Alpine 3.23.2 release notes](https://www.alpinelinux.org/posts/Alpine-3.23.2-released.html). - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent/) and [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/): add support for global `sampleLimit` setting. This allows users to efficiently limit the number of samples accepted per scrape target. This also ensures target-level `sample_limit` can correctly override the global setting. See [#&#8203;10145](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10145). Thanks to [@&#8203;kobylyanskiy](https://github.com/kobylyanskiy) for the contribution. - FEATURE: [vmauth](https://docs.victoriametrics.com/victoriametrics/vmauth/): expose `vmauth_user_request_backend_requests_total` and `vmauth_unauthorized_user_request_backend_requests_total` [metrics](https://docs.victoriametrics.com/victoriametrics/vmauth/#monitoring), which track the number of requests sent to backends. These counts may exceed `vmauth_user_requests_total` and `vmauth_unauthorized_user_requests_total` when requests are retried across multiple backends. See [#&#8203;10171](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10171). - FEATURE: [vmauth](https://docs.victoriametrics.com/victoriametrics/vmauth/): expose `vmauth_user_request_errors_total` and `vmauth_unauthorized_user_request_errors_total` [metrics](https://docs.victoriametrics.com/victoriametrics/vmauth/#monitoring), which track the number of user request errors. See [#&#8203;10188](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10188). - FEATURE: [vmauth](https://docs.victoriametrics.com/victoriametrics/vmauth/): add `-maxQueueDuration` command-line flag for waiting until the incoming request could be executed if `-maxConcurrentRequests` are already exceeded. This should help with graceful handling of a short spike in the number of concurrent requests without leading to a retry storm. See [#&#8203;10078](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10078). - FEATURE: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): introduce per-partition index. This should reduce disk space occupied by indexDBs as they get deleted along with the corresponding partitions once those partitions become outside the retention window. Read more about the motivation behind this feature at [#&#8203;7599](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7599) and what to expect at [#&#8203;8134](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8134). - BUGFIX: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/) and [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/): properly add `exported_` prefix to scraped metrics that have the same names as [auto-generated metrics](https://docs.victoriametrics.com/victoriametrics/vmagent/#automatically-generated-metrics). Previously, some auto-generated metrics were not recognized, so scraped metrics with the same names could overwrite them. See [#&#8203;10197](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10197). Thanks to [@&#8203;fxrlv](https://github.com/fxrlv) for the contribution. - BUGFIX: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): fix `vmagent_rows_inserted_total{type="newrelic"}` metric to correctly count samples. See [#&#8203;10191](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10191). Thanks to [@&#8203;fxrlv](https://github.com/fxrlv) for the contribution. - BUGFIX: [vmauth](https://docs.victoriametrics.com/victoriametrics/vmauth/): fix `vmauth_user_request_backend_errors_total` and `vmauth_unauthorized_user_request_backend_errors_total` to only reflect backend request errors. Previously, these counters could be overcounted with user request error. See [#&#8203;10177](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10177). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): rotate `dateMetricIDCache` instead of resetting it. This should make the eviction less aggressive. Since the cache does not have fixed max size anymore the `-storage.cacheSizeIndexDBDateMetricID` flag has been removed. See [#&#8203;10064](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10053) and PR [#&#8203;10169](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10169). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/): properly add metrics metadata scraped with `promscrape.config` and `selfScrapeInterval`. See [#&#8203;10175](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10175). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): fix stats collection for `indexdb/tagFiltersToMetricIDs`, `indexdb/metricID`, and `indexdb/date_metricID` caches. As per PR [#&#8203;10131](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10131), the stats is collected for most utilized instance only, but if the size of all instances is 0 then the stats won't be collected at all. This may result in max cache size alternating between the actual value and 0. See [#&#8203;10204](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10204) and [#&#8203;10230](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10230). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): properly proxy requests to [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/) when `-vmalert.proxyURL` flag is set. See [#&#8203;10178](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10178). </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:eyJjcmVhdGVkSW5WZXIiOiI0Mi43MS4yIiwidXBkYXRlZEluVmVyIjoiNDIuNzEuMiIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6W119-->
renovate added 1 commit 2026-01-06 03:07:42 +00:00
Update victoriametrics/vmagent Docker tag to v1.133.0 ef147d7226
AverageMarcus merged commit ed1f4506d4 into master 2026-01-06 09:59:02 +00:00
AverageMarcus deleted branch renovate/victoriametrics 2026-01-06 09:59:03 +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#625
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?