BUGFIX: vmagent, vmsingle and vminsert in VictoriaMetrics cluster: properly add OpenTelemetryUnit suffix to the metric name and metadata Help when -opentelemetry.usePrometheusNaming flag is enabled. Previously, if http_requests has Unit: seconds and the next metric cpu_usage has no Unit, cpu_usage would be ingested as cpu_usage_seconds. See #10889.
FEATURE: all VictoriaMetrics components: add support for reading cpu/memory limits configured via systemd slices. Previously, only limits set directly on the process's own cgroup were detected. See #10635. Thanks to @andriibeee for the contribution.
FEATURE: vmctl: improve error handling at opentsdb migration. See #10797
FEATURE: vmui: now Run query link on the Alerting Rules page correctly propagates the alert’s interval and evaluation time. See #10366.
FEATURE: stream aggregation: add vm_streamaggr_counter_resets_total metric for total*, increase* and rate* outputs that is useful for aggregation behaviour tracking. These metrics help to identify issues described in Troubleshooting: counter resets. See #10807.
FEATURE: vmsingle and vmstorage and vmselect in VictoriaMetrics cluster: add the support of ingestion and retrieval of samples with timestamps in the future. The new -futureRetention flag controls how far in the future the timestamps are allowed to be. See #827 and #10718.
BUGFIX: vminsert in VictoriaMetrics cluster: fix increased memory usage after upgrade to v1.140.0 by properly accounting for internal buffer count when calculating per-storage buffer size. See #10725. Thanks to @fxrlv for the contribution.
BUGFIX: all VictoriaMetrics components: properly parse IPv6 source address when accepting connections with proxy protocol v2 enabled. See #10839. Thanks to @andriibeee for the contribution.
BUGFIX: vmagent: properly attach tenant from __tenant_id__ label to the scraped metadata. See #10828.
BUGFIX: vmagent and vmsingle: -maxScrapeSize is now correctly applied when reading response bodies, including non-OK scrape error responses. See #10804.
BUGFIX: vmagent: fix ec2_sd_configs returning 401 AuthFailure from AWS when credentials are obtained via IRSA, instance role or AWS_CONTAINER_CREDENTIALS_* env vars. The regression was introduced in v1.140.0. See #10815. Thanks to @andriibeee for the contribution.
BUGFIX: vmauth: fix leak of backend TCP connections, file descriptors and goroutines when the client cancels the request after the backend response has been received. See #10833. Thanks to @andriibeee for the contribution.
BUGFIX: vmauth: fix a rare panic during config reload when a backend is marked as broken. See #10806.
BUGFIX: vmselect in VictoriaMetrics cluster: stop logging warnings about failed handshakes when the clusternative port receives TCP healthchecks from load balancers. See #10786. Thanks to @andriibeee for the contribution.
BUGFIX: vmrestore: fix an issue where vmrestore could hang indefinitely when interrupted during backup download. See #10794.
BUGFIX: vmsingle: properly execute graceful shutdown for vmsingle if -maxIngestionRate is configured. See #10795.
BUGFIX: vmui: fix time display on Alerting Rules page to use selected timezone. See #10827.
BUGFIX: vmui: use contrasting colors when displaying time series to improve visibility on light and dark themes. See #10869.
BUGFIX: vmalert: delete labels from rule results if they are specified with an empty string value in rule or group labels. See #10766.
BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: fix incorrect evaluation of binary operations caused by an ordering bug (e.g. 10 - (3 + 3 + 4) being evaluated as 10 - 3 + 3 + 4). The issue was introduced in v1.140.0, v1.136.4, and v1.122.19. See #10856.
Configuration
📅Schedule: (UTC)
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 contains the following updates:
| Package | Update | Change |
|---|---|---|
| [victoriametrics/vmagent](https://github.com/VictoriaMetrics/VictoriaMetrics) | minor | `v1.140.0` → `v1.142.0` |
---
### Release Notes
<details>
<summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)</summary>
### [`v1.142.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.142.0)
[Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.141.0...v1.142.0)
##### [v1.142.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.142.0)
Released at 2026-04-28
- BUGFIX: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/), [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): properly add [OpenTelemetry](https://docs.victoriametrics.com/victoriametrics/integrations/opentelemetry/) `Unit` suffix to the metric name and metadata `Help` when `-opentelemetry.usePrometheusNaming` flag is enabled. Previously, if `http_requests` has `Unit: seconds` and the next metric `cpu_usage` has no `Unit`, `cpu_usage` would be ingested as `cpu_usage_seconds`. See [#​10889](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10889).
### [`v1.141.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.141.0)
[Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.140.0...v1.141.0)
##### [v1.141.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.141.0)
Released at 2026-04-24
- SECURITY: upgrade base docker image (Alpine) from 3.23.3 to 3.23.4. See [Alpine 3.23.4 release notes](https://www.alpinelinux.org/posts/Alpine-3.20.10-3.21.7-3.22.4-3.23.4-released.html).
- FEATURE: all VictoriaMetrics components: add support for reading cpu/memory limits configured via [systemd slices](https://www.freedesktop.org/software/systemd/man/latest/systemd.slice.html). Previously, only limits set directly on the process's own cgroup were detected. See [#​10635](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10635). Thanks to [@​andriibeee](https://github.com/andriibeee) for the contribution.
- FEATURE: [vmctl](https://docs.victoriametrics.com/victoriametrics/vmctl/): improve error handling at opentsdb migration. See [#​10797](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10797)
- FEATURE: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): now `Run query` link on the Alerting Rules page correctly propagates the alert’s interval and evaluation time. See [#​10366](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10366).
- FEATURE: [alerts](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/rules): add new `MetricNameStatsCacheUtilizationIsTooHigh` alerting rule to track overutilization of [Metric names usage stats tracker](https://docs.victoriametrics.com/victoriametrics/#track-ingested-metrics-usage) (used in [Cardinality Explorer](https://docs.victoriametrics.com/victoriametrics/#cardinality-explorer)). See [#​10840](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10840).
- FEATURE: [stream aggregation](https://docs.victoriametrics.com/victoriametrics/stream-aggregation/): add `vm_streamaggr_counter_resets_total` metric for `total*`, `increase*` and `rate*` outputs that is useful for aggregation behaviour tracking. These metrics help to identify issues described in [Troubleshooting: counter resets](https://docs.victoriametrics.com/victoriametrics/stream-aggregation/#counter-resets). See [#​10807](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10807).
- FEATURE: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): add the support of ingestion and retrieval of samples with timestamps in the future. The new `-futureRetention` flag controls how far in the future the timestamps are allowed to be. See [#​827](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/827) and [#​10718](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10718).
- FEATURE: [dashboards/vmagent](https://grafana.com/grafana/dashboards/12683), [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add metadata row ingestion rate queries to related panels. See [#​10868](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10868).
- BUGFIX: `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): fix increased memory usage after upgrade to [v1.140.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.140.0) by properly accounting for internal buffer count when calculating per-storage buffer size. See [#​10725](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10725#issuecomment-4282256709). Thanks to [@​fxrlv](https://github.com/fxrlv) for the contribution.
- BUGFIX: all VictoriaMetrics components: properly parse IPv6 source address when accepting connections with proxy protocol v2 enabled. See [#​10839](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10839). Thanks to [@​andriibeee](https://github.com/andriibeee) for the contribution.
- BUGFIX: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): properly attach [tenant](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#multitenancy) from `__tenant_id__` label to the scraped metadata. See [#​10828](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10828).
- BUGFIX: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): keep [tenant](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#multitenancy) ingested into vmagent via [prometheus remotewrite](https://docs.victoriametrics.com/victoriametrics/integrations/prometheus/) endpoint. See [#​10828](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10828).
- BUGFIX: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/) and [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/): `-maxScrapeSize` is now correctly applied when reading response bodies, including non-OK scrape error responses. See [#​10804](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10804).
- BUGFIX: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): fix `ec2_sd_configs` returning 401 `AuthFailure` from AWS when credentials are obtained via IRSA, instance role or `AWS_CONTAINER_CREDENTIALS_*` env vars. The regression was introduced in [v1.140.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.140.0). See [#​10815](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10815). Thanks to [@​andriibeee](https://github.com/andriibeee) for the contribution.
- BUGFIX: [vmauth](https://docs.victoriametrics.com/victoriametrics/vmauth/): fix leak of backend TCP connections, file descriptors and goroutines when the client cancels the request after the backend response has been received. See [#​10833](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10833). Thanks to [@​andriibeee](https://github.com/andriibeee) for the contribution.
- BUGFIX: [vmauth](https://docs.victoriametrics.com/victoriametrics/vmauth/): fix a rare panic during config reload when a backend is marked as broken. See [#​10806](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10806).
- BUGFIX: `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): stop logging warnings about failed handshakes when the `clusternative` port receives TCP healthchecks from load balancers. See [#​10786](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10786). Thanks to [@​andriibeee](https://github.com/andriibeee) for the contribution.
- BUGFIX: [vmrestore](https://docs.victoriametrics.com/victoriametrics/vmrestore/): fix an issue where vmrestore could hang indefinitely when interrupted during backup download. See [#​10794](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10794).
- BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/): properly execute graceful shutdown for vmsingle if `-maxIngestionRate` is configured. See [#​10795](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10795).
- BUGFIX: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): fix time display on Alerting Rules page to use selected timezone. See [#​10827](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10827).
- BUGFIX: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): use contrasting colors when displaying time series to improve visibility on light and dark themes. See [#​10869](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10869).
- BUGFIX: [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/): delete labels from rule results if they are specified with an empty string value in rule or group labels. See [#​10766](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10766).
- BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): fix incorrect evaluation of binary operations caused by an ordering bug (e.g. `10 - (3 + 3 + 4)` being evaluated as `10 - 3 + 3 + 4`). The issue was introduced in v1.140.0, v1.136.4, and v1.122.19. See [#​10856](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10856).
</details>
---
### Configuration
📅 **Schedule**: (UTC)
- 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 [Mend Renovate](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xNDYuMCIsInVwZGF0ZWRJblZlciI6IjQzLjE1MC4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=-->
renovate
changed title from Update victoriametrics/vmagent Docker tag to v1.141.0 to Update victoriametrics/vmagent Docker tag to v1.142.02026-04-29 03:05:14 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR contains the following updates:
v1.140.0→v1.142.0Release Notes
VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)
v1.142.0Compare Source
v1.142.0
Released at 2026-04-28
vminsertin VictoriaMetrics cluster: properly add OpenTelemetryUnitsuffix to the metric name and metadataHelpwhen-opentelemetry.usePrometheusNamingflag is enabled. Previously, ifhttp_requestshasUnit: secondsand the next metriccpu_usagehas noUnit,cpu_usagewould be ingested ascpu_usage_seconds. See #10889.v1.141.0Compare Source
v1.141.0
Released at 2026-04-24
SECURITY: upgrade base docker image (Alpine) from 3.23.3 to 3.23.4. See Alpine 3.23.4 release notes.
FEATURE: all VictoriaMetrics components: add support for reading cpu/memory limits configured via systemd slices. Previously, only limits set directly on the process's own cgroup were detected. See #10635. Thanks to @andriibeee for the contribution.
FEATURE: vmctl: improve error handling at opentsdb migration. See #10797
FEATURE: vmui: now
Run querylink on the Alerting Rules page correctly propagates the alert’s interval and evaluation time. See #10366.FEATURE: alerts: add new
MetricNameStatsCacheUtilizationIsTooHighalerting rule to track overutilization of Metric names usage stats tracker (used in Cardinality Explorer). See #10840.FEATURE: stream aggregation: add
vm_streamaggr_counter_resets_totalmetric fortotal*,increase*andrate*outputs that is useful for aggregation behaviour tracking. These metrics help to identify issues described in Troubleshooting: counter resets. See #10807.FEATURE: vmsingle and
vmstorageandvmselectin VictoriaMetrics cluster: add the support of ingestion and retrieval of samples with timestamps in the future. The new-futureRetentionflag controls how far in the future the timestamps are allowed to be. See #827 and #10718.FEATURE: dashboards/vmagent, dashboards/cluster: add metadata row ingestion rate queries to related panels. See #10868.
BUGFIX:
vminsertin VictoriaMetrics cluster: fix increased memory usage after upgrade to v1.140.0 by properly accounting for internal buffer count when calculating per-storage buffer size. See #10725. Thanks to @fxrlv for the contribution.BUGFIX: all VictoriaMetrics components: properly parse IPv6 source address when accepting connections with proxy protocol v2 enabled. See #10839. Thanks to @andriibeee for the contribution.
BUGFIX: vmagent: properly attach tenant from
__tenant_id__label to the scraped metadata. See #10828.BUGFIX: vmagent: keep tenant ingested into vmagent via prometheus remotewrite endpoint. See #10828.
BUGFIX: vmagent and vmsingle:
-maxScrapeSizeis now correctly applied when reading response bodies, including non-OK scrape error responses. See #10804.BUGFIX: vmagent: fix
ec2_sd_configsreturning 401AuthFailurefrom AWS when credentials are obtained via IRSA, instance role orAWS_CONTAINER_CREDENTIALS_*env vars. The regression was introduced in v1.140.0. See #10815. Thanks to @andriibeee for the contribution.BUGFIX: vmauth: fix leak of backend TCP connections, file descriptors and goroutines when the client cancels the request after the backend response has been received. See #10833. Thanks to @andriibeee for the contribution.
BUGFIX: vmauth: fix a rare panic during config reload when a backend is marked as broken. See #10806.
BUGFIX:
vmselectin VictoriaMetrics cluster: stop logging warnings about failed handshakes when theclusternativeport receives TCP healthchecks from load balancers. See #10786. Thanks to @andriibeee for the contribution.BUGFIX: vmrestore: fix an issue where vmrestore could hang indefinitely when interrupted during backup download. See #10794.
BUGFIX: vmsingle: properly execute graceful shutdown for vmsingle if
-maxIngestionRateis configured. See #10795.BUGFIX: vmui: fix time display on Alerting Rules page to use selected timezone. See #10827.
BUGFIX: vmui: use contrasting colors when displaying time series to improve visibility on light and dark themes. See #10869.
BUGFIX: vmalert: delete labels from rule results if they are specified with an empty string value in rule or group labels. See #10766.
BUGFIX: vmsingle and
vmselectin VictoriaMetrics cluster: fix incorrect evaluation of binary operations caused by an ordering bug (e.g.10 - (3 + 3 + 4)being evaluated as10 - 3 + 3 + 4). The issue was introduced in v1.140.0, v1.136.4, and v1.122.19. See #10856.Configuration
📅 Schedule: (UTC)
🚦 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 Mend Renovate.
Update victoriametrics/vmagent Docker tag to v1.141.0to Update victoriametrics/vmagent Docker tag to v1.142.00ae72bbd1ato0b61a47008