feat(container): update image victoriametrics/victoria-metrics to v1.142.0

[trap-renovate]

This PR contains the following updates:

Package	Update	Change
victoriametrics/victoria-metrics	minor	v1.139.0 → v1.142.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/victoria-metrics)

v1.142.0

Compare Source

v1.142.0

Released at 2026-04-28

• BUGFIX: vmagent, vmsingle and vminsert in VictoriaMetrics cluster: properly add 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.

v1.141.0

Compare 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 query link on the Alerting Rules page correctly propagates the alert’s interval and evaluation time. See #​10366.

• FEATURE: alerts: add new MetricNameStatsCacheUtilizationIsTooHigh alerting rule to track overutilization of Metric names usage stats tracker (used in Cardinality Explorer). See #​10840.

• 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.

• FEATURE: dashboards/vmagent, dashboards/cluster: add metadata row ingestion rate queries to related panels. See #​10868.

• 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: keep tenant ingested into vmagent via prometheus remotewrite endpoint. 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.

v1.140.0

Compare Source

v1.140.0

Released at 2026-04-10

Update Note 1: vmsingle and vmselect in VictoriaMetrics cluster: CSV export (/api/v1/export/csv) now adds a header row as the first line of the response, so existing CSV-processing scripts may need to skip this header. See #​10666.

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

• FEATURE: vmagent: add per-URL -remoteWrite.disableMetadata flag to disable metadata sending for specific remote storage URLs. See #​10711. Thanks to @​evkuzin for the contribution.

• FEATURE: vmagent: add profile option to ec2_sd_configs for loading credentials from named AWS profiles in ~/.aws/credentials and ~/.aws/config, including source_profile chaining and role_arn resolution. See ec2_sd_configs docs. Issue #​1685. Thanks to @​andriibeee for the contribution.

• FEATURE: introduce vm_filestream_fsync_duration_seconds_total and vm_filestream_fsync_calls_total metrics, which can be used for detecting slow storage if it cannot keep up with the current data ingestion rate. See #​10432. Thanks to @​mehrdadbn9 for the contribution.

• FEATURE: vmctl: add dedicated thanos mode for migrating data from Thanos. This mode supports both raw and downsampled Thanos blocks, including all aggregate types (count, sum, min, max, counter). Each aggregate is imported as a separate metric with resolution and aggregate type suffixes (e.g., metric_name:5m:count). The new mode uses --thanos-* prefixed flags: --thanos-snapshot, --thanos-concurrency, --thanos-filter-time-start, --thanos-filter-time-end, --thanos-filter-label, --thanos-filter-label-value, and --thanos-aggr-types. See #​9262.

• FEATURE: dashboards/alert-statistics: add pending and firing alerts stats; fix query in FIRING over time by group panel. See #​10571. Thanks to @​sias32 for the contribution.

• FEATURE: vmalert: add random jitter to concurrent periodical flushers targeting the remote write destination. This helps spread remote write flushes across the flush interval, avoiding congestion at the remote write destination and enhancing queue data consumption. See #​10729.

• FEATURE: vmalert: expose vmalert_remotewrite_sent_rows and vmalert_remotewrite_sent_bytes histograms to provide better visibility into remote write request sizes. See #​10727.

• FEATURE: vmagent: allow setting -1 value for -remoteWrite.maxHourlySeries and -remoteWrite.maxDailySeries command-line flags. This automatically sets limits to the highest possible value in order to enable tracking without enforcing any limits. This is helpful for estimating current usage before applying real limits. See #​9614.

• FEATURE: vminsert in VictoriaMetrics cluster: optimize vminsert buffer size per vmstorage node based on available CPU, memory and storage node count to reduce OOM risk. See #​10725.

• FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: allow setting -1 value for -storage.maxHourlySeries and -storage.maxDailySeries command-line flags. This automatically sets limits to the highest possible value in order to enable tracking without enforcing any limits. This is helpful for estimating current usage before applying real limits. See #​9614.

• FEATURE: vmalert: expose vmalert_remotewrite_queue_size and vmalert_remotewrite_queue_capacity to facilitate monitoring of remote write queue usage. See #​10765.

• FEATURE: vmui: CSV export on the Raw Query tab now includes all labels from the executed query. VMUI no longer prepends a header row, as it is now provided by the backend. See #​10667 and #​10666. Thanks to @​lawrence3699 for the contribution.

• FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: add header row to /api/v1/export/csv output and auto-detect header rows during import via /api/v1/import/csv. See #​10666. Thanks to @​andriibeee for the contribution.

• FEATURE: all VictoriaMetrics components: expose operating system name and release version as metric vm_os_info. See #​10481.

• FEATURE: vmalert: align group evaluation time with the eval_offset option to help manage group execution more effectively. See #​10772.

• BUGFIX: vmbackup, vmbackupmanager: retry the requests that failed with unexpected EOF due to unstable network to S3 service. See #​10699.

• BUGFIX: All VictoriaMetrics components: Fix an issue where unsupported metric metadata type was exposed for summaries and quantiles if a summary wasn't updated within a certain time window. See metrics#120 and metrics#121.

• BUGFIX: vmagent: fix scrape_series_added metric to update only on successful scrapes, aligning its behavior with Prometheus. See #​10653.

• BUGFIX: vmselect in VictoriaMetrics cluster: prevent partial responses from second-level vmselect nodes in multi-level cluster setups. Ensures response completeness and correctness, and avoids cache pollution in top-level vmselect. See #​10678.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: Fix storage connection saturation spikes at 00:00 UTC and improve data ingestion when the storage is restarted during the first hour of the day. See 10698.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: prevent rare panic during storage start-up at 100% disk usage. See #​10747 Thanks to @​nmn3m for the contribution.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: prevent data ingestion from getting completely stuck when storage is under heavy load. See #​10784. Thanks to @​fxrlv for the contribution.

---

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 becomes conflicted, 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 Mend Renovate.

[github-actions]

Diff

@@ spec.template.spec.containers.victoria-metrics.image @@
# apps/v1/StatefulSet/monitor/victoria-metrics
! ± value change
- victoriametrics/victoria-metrics:v1.139.0
+ victoriametrics/victoria-metrics:v1.142.0

@@ spec.template.spec.containers.victoria-metrics.image @@
# apps/v1/StatefulSet/monitor/victoria-metrics
! ± value change
- victoriametrics/victoria-metrics:v1.139.0
+ victoriametrics/victoria-metrics:v1.142.0