Skip to content

chore(deps): update dependency victoriametrics/victoriametrics to v1.145.0#1716

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate-victoriametrics-victoriametrics-1-x
Open

chore(deps): update dependency victoriametrics/victoriametrics to v1.145.0#1716
renovate[bot] wants to merge 1 commit into
mainfrom
renovate-victoriametrics-victoriametrics-1-x

Conversation

@renovate

@renovate renovate Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
VictoriaMetrics/VictoriaMetrics minor 1.139.0 → 1.145.0

Release Notes

VictoriaMetrics/VictoriaMetrics (VictoriaMetrics/VictoriaMetrics)

v1.145.0

Compare Source

v1.145.0

Release candidate

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

  • FEATURE: enterprise vmsingle and vmstorage in VictoriaMetrics cluster: add the new metrics vm_downsampling_partitions_scheduled_rows and vm_retention_filters_partitions_scheduled_rows for measuring background historical data merge completion time. See #​10960

  • FEATURE: vmalert: support match[]=<label_selector> query parameters in /api/v1/rules and /api/v1/alerts APIs to return only the rules that have configured labels satisfying the provided label selectors. See 11020.

  • FEATURE: vmagent, vmsingle and vminsert in VictoriaMetrics cluster: add -opentelemetry.promoteAllResourceAttributes and -opentelemetry.promoteScopeMetadata command-line flags to allow managing label promotion for resource attributes and OTel scope metadata. See OpenTelemetry docs and #​10931.

  • FEATURE: vmagent : introduce vmagent_remotewrite_kafka_outbuf_latency_seconds and vmagent_remotewrite_kafka_rtt_seconds metrics for kafka integration. The metrics could help identify throughput bottlenecks. See #​10730.

  • FEATURE: vmauth: properly log user information when a missing route error occurs. See #​11052.

  • FEATURE: vmctl: add the ability to migrate data from Mimir object storage to VictoriaMetrics. See #​7717.

  • FEATURE: dashboards: show the full version label in the Version panel when short_version label is empty (e.g. custom builds from feature branch). Previously, the panel could appear empty. See #​11047.

  • BUGFIX: vmalert: fix the Notifiers page in web UI appearing blank despite the API returning notifier data correctly. See #​11035.

  • BUGFIX: vmalert: reset the group evaluation timestamp if it exceeds the current host time. Previously, vmalert could use future timestamps for evaluations if the system clock was shifted backward. See #​10985.

  • BUGFIX: vmagent and vmsingle: properly parse Prometheus Native Histograms, previously Protobuf parser could produce unexpected vmrange labels. See #​11041.

  • BUGFIX: vmauth: properly calculate number of loaded users to be printed in startup log. Previously, it was only accounting for static users and skipped JWT configuration entries. See #​11050.

  • BUGFIX: MetricsQL: integrate() no longer extrapolates the last sample's value past the end of the time series. Previously, querying integrate(metric[1h]) at a timestamp where the series had already ended would keep accruing area as if the last value continued indefinitely, producing values much larger than the true integral. See #​9474. Thanks to @​wtfashwin for contribution.

  • BUGFIX: vmselect in VictoriaMetrics cluster: avoid returning HTTP 503 for queries with partial results when a storage group is unavailable and -search.denyPartialResponse is disabled. See #​11009. Thanks to @​fxrlv for the contribution.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: properly escape utf-8 label names for /federate API requests. See #​10968.

  • BUGFIX: vmui: persist the Disable deduplication toggle under its own local storage key. Before this fix, the toggle state was lost after reload and could overwrite the Compact view table setting. See #​11004. Thanks to @​immanuwell for the contribution.

  • BUGFIX: vmselect in VictoriaMetrics cluster: fix intermittent write: connection timed out errors caused by silently dropped TCP connections being reused from the connection pool. See #​10735.

v1.144.0

Compare Source

v1.144.0

Released at 2026-05-22

  • FEATURE: all VictoriaMetrics components: improve logging for the -memory.allowedBytes flag to warn about excessively low value (less than 1MB). See issue #​10935.

  • FEATURE: vmagent and vmalert: add basicAuth.usernameFile command-line flags for reading basic auth username from a file, similar to the existing basicAuth.passwordFile. The file is re-read every second. See #​9436. Thanks to @​kimjune01 for the contribution.

  • FEATURE: vminsert in VictoriaMetrics cluster: add clusternative.tls vminsert configuration flags for multi-level cluster setups. See #​10958.

  • FEATURE: vmsingle, vminsert in VictoriaMetrics cluster and vmagent: add -opentelemetry.labelNameUnderscoreSanitization command-line flag to control whether to enable prepending of key to labels starting with _ when -opentelemetry.usePrometheusNaming is enabled. See OpenTelemetry docs and #​9663. Thanks to @​andriibeee for the contribution.

  • FEATURE: vmui: improve the Top Queries table UI. Duration columns now display human-readable values (e.g. 1.23s) instead of raw seconds, memory column shows human-readable sizes (e.g. 1.23 MB), instant queries are labeled as instant instead of empty string, and column headers now show tooltips with descriptions. See #​10790.

  • FEATURE: vmagent: drain in-memory remote write queue on shutdown within the 5-second grace period before falling back to persisting blocks to disk. See #​9996

  • FEATURE: vminsert in VictoriaMetrics cluster: Improve slowness-based rerouting to prevent rerouting storms under high cluster load. Previously, rerouting could cascade across storage nodes when the whole cluster was saturated, making the situation worse. Now rerouting only activates when the cluster p90 saturation is below 60%, and the slowest node is more than 20% slower than p90. See #​10876.

  • FEATURE: vmauth: add {{.MetricsAccountID}} and {{.MetricsProjectID}} JWT claim placeholders for use in headers and url_prefix config fields. Previously, only the combined {{.MetricsTenant}} (accountID:projectID) JWT placeholder was supported, making it impossible to configure multitenancy via headers. See #​10927. Thanks to @​Vinayak9769 for the contribution.

  • FEATURE: vmui: display null values on Raw Query chart. null values can be actual NaN or null values exposed by the exporter, or stale markers. Before, vmui Raw Query was silently dropping non-numeric values. Displaying such values on the chart could improve the debugging experience. See #​10986.

  • BUGFIX: stream aggregation: stop emitting stale values for quantiles(...) outputs when a time series has no samples during the current aggregation interval. See #​10918. Thanks to @​alexei38 for the contribution.

  • BUGFIX: stream aggregation: extend delay on aggregation windows flush by the biggest lag among pushed samples. Before, the delay was calculated as 95th percentile across samples, which could underrepresent outliers and reject them from aggregation as "too old". See #​10402.

  • BUGFIX: vmagent: fix a bug in cardinality limiters where series with different labels, like {a="bc"} and {ab="c"}, could be incorrectly treated as identical and dropped. See #​10937.

  • BUGFIX: vmagent: hide values passed to -remoteWrite.headers in startup logs, /metrics, and /flags, since they can contain sensitive HTTP headers such as Authorization and API keys.

  • BUGFIX: vmagent: hide values passed to -remoteWrite.proxyURL in startup logs, /metrics, and /flags, since they can contain sensitive credentials.

  • BUGFIX: vmalert: hide values passed to -remoteWrite.headers,remoteRead.headers, datasource.headers and notifier.headers in startup logs, /metrics, and /flags, since they can contain sensitive HTTP headers such as Authorization and API keys.

  • BUGFIX: vminsert in VictoriaMetrics cluster: properly establish mtls connection between vmstorage and vminsert. Regression was introduced in v1.130.0 release for the enterprise version of vmstorage. See #​10972.

  • BUGFIX: vmrestore: fix a bug where specifying -storageDataPath with a trailing slash could cause vmrestore to panic. See #​10823. Thanks to @​utafrali for the contribution.

  • BUGFIX: vmagent: prevent unintentional rerouting of samples to other sharding targets when one of the -remoteWrite.url targets with -remoteWrite.disableOnDiskQueue becomes blocked. Previously this could break the sharding guarantee by sending samples to wrong targets instead of dropping or retrying them. See #​10507.

  • BUGFIX: vmagent: return error on startup if -remoteWrite.disableOnDiskQueue is not configured uniformly across all -remoteWrite.url targets when -remoteWrite.shardByURL is enabled. Either all targets must have it enabled or all must have it disabled. See #​10507.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: hide values passed to vmalert.proxyURL in startup logs, /metrics, and /flags, since they can contain sensitive HTTP headers such as Authorization and API keys.

  • BUGFIX: vmui: preserve exact series values in graph tooltips instead of rounding them by significant digits. See #​10952.

  • BUGFIX: all VictoriaMetrics components: fix int64 overflow when parsing timestamp parameters with relative durations. See #​10880.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: -denyQueriesOutsideRetention now also rejects queries whose end time is beyond -futureRetention. See #​10879.

  • BUGFIX: vmui: add missing __timestamp__ and __value__ columns to CSV exported from the table view on the Query tab. See #​10975.

v1.143.0

Compare Source

v1.143.0

Released at 2026-05-08

v1.142.0

Compare Source

v1.142.0

Update Note 1: vminsert in VictoriaMetrics cluster: contain a bug that can block ingestion when enterprise automatic-vmstorage-discovery feature is used. Bug was introduced in v1.141.0, v1.136.6.

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

Update Note 1: vmagent, vmsingle and vminsert in VictoriaMetrics cluster: a bug in OpenTelemetry parsing caused the Unit suffix of the previously parsed metric to be incorrectly applied to subsequent metrics that have no Unit field, when -opentelemetry.usePrometheusNaming is enabled. For example, if http_requests has Unit: seconds and the next metric cpu_usage has no Unit, cpu_usage would be ingested as cpu_usage_seconds. The bug was introduced in v1.132.0. See #​10889.

Update Note 2: vminsert in VictoriaMetrics cluster: contain a bug that can block ingestion when enterprise automatic-vmstorage-discovery feature is used. Bug was introduced in v1.141.0, v1.136.6.

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.

Update Note 2: MetricsQL: Due to an ordering bug in binary operations, some queries may produce incorrect results. For example, 10 - (3 + 3 + 4) is evaluated as 10 - 3 + 3 + 4. The issue was introduced in versions v1.140.0, v1.136.4, v1.122.19, and is addressed in upcoming releases. It is strongly recommended to avoid these versions entirely. See #​10856.

Update Note 3: vmagent, vmsingle and vminsert in VictoriaMetrics cluster: a bug in OpenTelemetry parsing caused the Unit suffix of the previously parsed metric to be incorrectly applied to subsequent metrics that have no Unit field, when -opentelemetry.usePrometheusNaming is enabled. For example, if http_requests has Unit: seconds and the next metric cpu_usage has no Unit, cpu_usage would be ingested as cpu_usage_seconds. The bug was introduced in v1.132.0. See #​10889.

  • 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: Never, 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 was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants