VictoriaMetrics

v1.149.0

Released at 2026-07-31

Update Note 1: vminsert in VictoriaMetrics cluster: the default value of -disableRerouting flag has changed from true to false, enabling slowness-based re-routing by default. Slowness re-routing is automatically disabled when -replicationFactor is greater than 1. If you rely on the old behavior, pass -disableRerouting command-line flag to vminsert. See #11287.

Update Note 2: vmsingle and vmselect in VictoriaMetrics cluster: the /api/v1/admin/tsdb/delete_series, /tags/delSeries endpoints now require POST method. Previously, it also accepted GET requests. If you use GET requests for this endpoint, update your scripts or tooling to use POST instead. See #5552.

• SECURITY: vmsingle and vmselect in VictoriaMetrics cluster: restrict /api/v1/admin/tsdb/delete_series, /tags/delSeries endpoints to POST method only to prevent some SSRF-based data deletion attacks. See #5552.

• FEATURE: dashboards: add Fsync avg duration panel to the Troubleshooting section of the single-node, cluster, and vmagent dashboards. This panel surfaces degradation of IO operation for faster incident triage. See #10432.

• FEATURE: vmagent: add name label identifying the corresponding -remoteWrite.url target to the vm_persistentqueue_* metrics exposed by persistent queue. See #7944. Thanks to @tIGO for contribution.

• FEATURE: vmagent: add -remoteWrite.obfuscateLabels flag for hashing values of the specified labels before sending metrics to the corresponding -remoteWrite.url. This allows sharing metrics with external systems while keeping sensitive label values hidden. See #10599.

• FEATURE: vmalert: add -replay.continueWithExecutionErr flag to allow continuing to replay other rules when a rule execution fails with a 422 response code, which can happen due to an expression syntax error or a resource limit being hit. See 11313.

• FEATURE: vmalert: add template variable $interval to expose the alerting rule group's evaluation interval. This allows generating dashboard links with a lookback window relative to the rule's interval, for example &from={{ ($activeAt.Add (parseDurationTime (printf "-%s" .Interval))).UnixMilli }}&to={{ $activeAt.UnixMilli }}. See #11232. Thanks to @1solomonwakhungu for contribution.

• FEATURE: vmbackupmanager and alerts: introduce vm_backup_last_success_at metric to track the last successful backup by type. Add alerting rules NoLatestBackupWithinLastDay, NoHourlyBackupWithinLastDay, NoDailyBackupWithinLast3Days, NoWeeklyBackupWithinLast14Days and NoMonthlyBackupWithinLast62Days to remind users about the missing backups. See #11217.

• FEATURE: vmctl: support Prometheus native histograms migration in remote read mode. Native histograms are converted into _count, _sum and _bucket series with vmrange labels in the same way as VictoriaMetrics converts native histograms received via Prometheus remote write protocol, except that for native histograms with custom buckets the original bucket bounds are preserved instead of being estimated with the exponential formula. Previously native histograms were silently ignored in SAMPLES mode, while in stream mode the migration failed with EOF error. See #11292. Thanks to @liuxu623 for contribution.

• FEATURE: vminsert in VictoriaMetrics cluster: enable slowness-based re-routing by default. Previously, -disableRerouting defaulted to true, which limited ingestion throughput to the slowest vmstorage node. Now -disableRerouting defaults to false, so vminsert automatically routes data away from the slowest vmstorage node, improving overall ingestion performance. Slowness re-routing is automatically disabled when -replicationFactor is greater than 1. See #11287.

• FEATURE: vmui: persist the selected auto-refresh interval in the URL. See VictoriaLogs#1310.

• BUGFIX: MetricsQL: properly drop data points filtered out by an inner comparison operation when its result is used on the right side of another comparison. Previously, queries like foo != (bar > 100) could return unexpected results because filtered-out data points are represented internally as NaN, and value != NaN evaluates to true. Comparisons against explicitly present NaN values keep the previous behavior. See #10018. Thanks to @zasdaym for contribution.

• BUGFIX: vmagent and vmsingle: ignore HTTP proxy environment variables when scraping targets over Unix domain sockets. See #11318. Thanks to @lwmacct for contribution.

• BUGFIX: vmalert: fixed the display of rule state badges on the Groups page in the web UI. See #11160.

• BUGFIX: vmbackupmanager: previously, vmbackupmanager was crashing on startup when it failed to restore backup state from remote storage, causing a crash loop. Now it logs the error and continues running, retrying the state restore before each scheduled backup. Added vm_backup_errors_total{type="restoreState"} metric to track backup state restore failures. See #11217.

• BUGFIX: stream aggregation: fix incorrect sum_samples_total results when enable_windows: true is set. See #11261. Thanks to @beyond-infra for contribution.

• BUGFIX: vmsingle, vmselect in VictoriaMetrics cluster and vmctl: accept scientific notation with sub-second precision (e.g. 1.784144612388E9) for timestamp args such as start and end in /api/v1/query_range and --vm-native-filter-time-start and --vm-native-filter-time-end in vmctl. Previously, values with this pattern were rejected, which is incompatible with Prometheus. See #11268. Thanks to @STiFLeR7 for contribution.

v1.136.15

Released at 2026-07-31

v1.136.x is a line of LTS releases. It contains important up-to-date bugfixes for VictoriaMetrics enterprise. All these fixes are also included in the latest community release. The v1.136.x line will be supported for at least 12 months since v1.136.0 release

Update Note 1: vmsingle and vmselect in VictoriaMetrics cluster: the /api/v1/admin/tsdb/delete_series, /tags/delSeries endpoints now require POST method. Previously, it also accepted GET requests. If you use GET requests for this endpoint, update your scripts or tooling to use POST instead. See #5552.

• SECURITY: vmsingle and vmselect in VictoriaMetrics cluster: restrict /api/v1/admin/tsdb/delete_series, /tags/delSeries endpoints to POST method only to prevent some SSRF-based data deletion attacks. See #5552.

• BUGFIX: vmbackupmanager: previously, vmbackupmanager was crashing on startup when it failed to restore backup state from remote storage, causing a crash loop. Now it logs the error and continues running, retrying the state restore before each scheduled backup. Added vm_backup_errors_total{type="restoreState"} metric to track backup state restore failures. See #11217.

v1.148.1

Released at 2026-07-31

v1.148.x is a line of LTS releases. It contains important up-to-date bugfixes for VictoriaMetrics enterprise. All these fixes are also included in the latest community release. The v1.148.x line will be supported for at least 12 months since v1.148.0 release

Update Note 1: vmsingle and vmselect in VictoriaMetrics cluster: the /api/v1/admin/tsdb/delete_series, /tags/delSeries endpoints now require POST method. Previously, it also accepted GET requests. If you use GET requests for this endpoint, update your scripts or tooling to use POST instead. See #5552.

• SECURITY: vmsingle and vmselect in VictoriaMetrics cluster: restrict /api/v1/admin/tsdb/delete_series, /tags/delSeries endpoints to POST method only to prevent some SSRF-based data deletion attacks. See #5552.

• BUGFIX: MetricsQL: properly drop data points filtered out by an inner comparison operation when its result is used on the right side of another comparison. Previously, queries like foo != (bar > 100) could return unexpected results because filtered-out data points are represented internally as NaN, and value != NaN evaluates to true. Comparisons against explicitly present NaN values keep the previous behavior. See #10018. Thanks to @zasdaym for contribution.

• BUGFIX: vmagent and vmsingle: ignore HTTP proxy environment variables when scraping targets over Unix domain sockets. See #11318. Thanks to @lwmacct for contribution.

• BUGFIX: vmalert: fixed the display of rule state badges on the Groups page in the web UI. See #11160.

• BUGFIX: vmbackupmanager: previously, vmbackupmanager was crashing on startup when it failed to restore backup state from remote storage, causing a crash loop. Now it logs the error and continues running, retrying the state restore before each scheduled backup. Added vm_backup_errors_total{type="restoreState"} metric to track backup state restore failures. See #11217.

• BUGFIX: stream aggregation: fix incorrect sum_samples_total results when enable_windows: true is set. See #11261. Thanks to @beyond-infra for contribution.

• BUGFIX: vmsingle, vmselect in VictoriaMetrics cluster and vmctl: accept scientific notation with sub-second precision (e.g. 1.784144612388E9) for timestamp args such as start and end in /api/v1/query_range and --vm-native-filter-time-start and --vm-native-filter-time-end in vmctl. Previously, values with this pattern were rejected, which is incompatible with Prometheus. See #11268. Thanks to @STiFLeR7 for contribution.

v1.148.0

Released at 2026-07-17

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

• FEATURE: MetricsQL: support fill modifiers to allow missing series on either side of a binary operation to be filled with a provided default value. See #10598.

• FEATURE: vmagent and vmsingle: support scraping metrics over Unix domain sockets. The socket path can be configured via the __unix_socket__ target label. See #11156. Thanks to @vinyas-bharadwaj for contribution.

• FEATURE: vmagent and vmsingle: Improve background discovery performance for http_sd discovery. See #8838.

• FEATURE: vmagent and vmsingle: allow overriding max_scrape_size on a per-target basis via the __max_scrape_size__ label during target relabeling. See #11188.

• FEATURE: vmstorage and vmsingle: add -maxBackfillAge command-line flag for limiting ingestion of samples with historical timestamps, for example, when older data has been moved between storage tiers (nvme/hdd, hot/cold). See #11199. Thanks to @AshwinRamaniPsg for contribution.

• FEATURE: vmagent: automatically preload relabeling rules configured via -remoteWrite.relabelConfig and -remoteWrite.urlRelabelConfig in the metrics relabel debug UI. See #9918.

• BUGFIX: vminsert in VictoriaMetrics cluster: Now drops metadata blocks when communicating with vmstorage nodes over the legacy RPC protocol. To avoid this limitation, upgrade vmstorage to a version that supports the new RPC protocol (>= v1.137.0). See #11146.

• BUGFIX: vmbackup and vmbackupmanager: retry S3 requests failing with HTTP 429 status code or TooManyRequests error code. Previously such requests were not retried, so a short burst of rate limiting would fail the whole backup. See #11218. Thanks to @gautamrizwani for contribution.

• BUGFIX: vmselect in VictoriaMetrics cluster: properly apply limit to metrics metadata response. See #11139.

• BUGFIX: vmagent: fix a possible data race when processing OpenTelemetry metadata. See #11238. Thanks to @nevgeny for contribution.

• BUGFIX: vmagent: flush pending persistent queue data to chunk file before updating the metadata. This prevents the metadata writer offset from getting ahead of the chunk file size and avoids losing the persistent queue after an unclean shutdown. See #11192.

• BUGFIX: vmagent: atomically write persistent queue metainfo to prevent possible file corruption on ungraceful shutdown. See #11192.

• BUGFIX: vmagent: fix increased CPU and memory usage when -remoteWrite.urlRelabelConfig or -remoteWrite.streamAggr.config flags are used. The bug was introduced in #10854 and existed since v1.147.0. See #11250.

• BUGFIX: vmui: preserve newline formatting in alert and rule annotations on the Alerting page. See #11171.

• BUGFIX: vmui: hide Total metric names stats on Cardinality Explorer page when user selects a specific metric or label to focus. See #11154 for details. Thanks to @lghuy05 for the contribution.

• BUGFIX: vmui: keep only one header navigation dropdown (Explore, Tools) open at a time. Previously, hovering across two dropdowns could briefly leave both open due to the close delay. See #11224. Thanks to @antedotee for contribution.

• BUGFIX: vmauth: return 408 Request Timeout instead of 400 Bad Request when the request body isn't received within -maxQueueDuration. This prevents vmagent from incorrectly downgrading the remote write protocol and dropping data when vmauth is used as a proxy for a remote write endpoint. See #11272.

v1.122.27

Released at 2026-07-17

v1.122.x is a line of LTS releases. It contains important up-to-date bugfixes for VictoriaMetrics enterprise. All these fixes are also included in the latest community release. The v1.122.x line will be supported for at least 12 months since v1.122.0 release

• BUGFIX: vmagent: flush pending persistent queue data to chunk file before updating the metadata. This prevents the metadata writer offset from getting ahead of the chunk file size and avoids losing the persistent queue after an unclean shutdown. See #11192.
• BUGFIX: vmbackup and vmbackupmanager: retry S3 requests failing with HTTP 429 status code or TooManyRequests error code. Previously such requests were not retried, so a short burst of rate limiting would fail the whole backup. See #11218. Thanks to @gautamrizwani for contribution.
• BUGFIX: vmui: hide Total metric names stats on Cardinality Explorer page when user selects a specific metric or label to focus. See #11154 for details. Thanks to @lghuy05 for the contribution.

v1.136.14

Released at 2026-07-17

v1.136.x is a line of LTS releases. It contains important up-to-date bugfixes for VictoriaMetrics enterprise. All these fixes are also included in the latest community release. The v1.136.x line will be supported for at least 12 months since v1.136.0 release

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

• BUGFIX: vmagent: flush pending persistent queue data to chunk file before updating the metadata. This prevents the metadata writer offset from getting ahead of the chunk file size and avoids losing the persistent queue after an unclean shutdown. See #11192.

• BUGFIX: vmagent: fix a possible data race when processing OpenTelemetry metadata. See #11238. Thanks to @nevgeny for contribution.

• BUGFIX: vmagent: atomically write persistent queue metainfo to prevent possible file corruption on ungraceful shutdown. See #11192.

• BUGFIX: vmbackup and vmbackupmanager: retry S3 requests failing with HTTP 429 status code or TooManyRequests error code. Previously such requests were not retried, so a short burst of rate limiting would fail the whole backup. See #11218. Thanks to @gautamrizwani for contribution.

• BUGFIX: vmselect in VictoriaMetrics cluster: properly apply limit to metrics metadata response. See #11139.

• BUGFIX: vminsert in VictoriaMetrics cluster: Now drops metadata blocks when communicating with vmstorage nodes over the legacy RPC protocol. To avoid this limitation, upgrade vmstorage to a version that supports the new RPC protocol (>= v1.137.0). See #11146.

• BUGFIX: vmui: keep only one header navigation dropdown (Explore, Tools) open at a time. Previously, hovering across two dropdowns could briefly leave both open due to the close delay. See #11224. Thanks to @antedotee for contribution.

• BUGFIX: vmui: preserve newline formatting in alert and rule annotations on the Alerting page. See #11171.

• BUGFIX: vmui: hide Total metric names stats on Cardinality Explorer page when user selects a specific metric or label to focus. See #11154 for details. Thanks to @lghuy05 for the contribution.

• BUGFIX: vmauth: return 408 Request Timeout instead of 400 Bad Request when the request body isn't received within -maxQueueDuration. This prevents vmagent from incorrectly downgrading the remote write protocol and dropping data when vmauth is used as a proxy for a remote write endpoint. See #11272.

v1.147.0

Released at 2026-07-06

Update Note 1: vmagent: contains a bug that causes increased CPU and memory usage when -remoteWrite.urlRelabelConfig or -remoteWrite.streamAggr.config flags are used. The bug was introduced in #10854. Upgrade to v1.148.0 or rollback to v1.146.0. See #11250.

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

• FEATURE: vmauth: add default_vm_access_claim field into jwt section of auth config. It could be used at JWT claim placeholders, if JWT token doesn't have vm_access claim. See #11054.

• FEATURE: vmagent: reduces CPU usage by 10% at sharding among remote storages. See #11113. Thanks to @bennf for contribution.

• FEATURE: vmagent, vminsert in VictoriaMetrics cluster and vmsingle: introduce 64KiB size limit for metric metadata fields - Unit, Help and MetricFamilyName. See #11128.

• FEATURE: vmagent and vmsingle: reduce CPU usage for storing scrape target labels. See #10919.

• FEATURE: vmagent: add support for Monitoring Data eXchange (MDX): the ability to route only metrics from VictoriaMetrics services to a specific -remoteWrite.url. MDX is useful for building monitoring-of-monitoring where one remote storage should receive the full metric stream and another should receive only VictoriaMetrics metrics. Enable per destination with -remoteWrite.mdx.enable=true. See #10600.

• FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: expose vm_data_size_bytes{type="storage/metaindex"} and vm_data_size_bytes{type="indexdb/metaindex"} metrics for tracking memory occupied by metaindex data. See #11204. Thanks to @SamarthBagga for contribution.

• FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: add optimize_repeated_binary_op_subexprs=1 query arg to /api/v1/query_range for executing binary operator sides sequentially when they share the same optimized aggregate rollup result expression. This allows the second side to reuse rollup result cache populated by the first side. See #10575. Thanks to @xhebox for the contribution.

• FEATURE: vmsingle: Add the support of vmselect RPC to vmsingle so that single node can be queried by a vmselect from a vmcluster deployment. See #4328, #10926, and the documentation.

• FEATURE: alerts: add InvalidAuthTokenRequestErrors alerting rule to vmauth alerts. The new rule notifies when vmauth receives requests with invalid or missing auth tokens, which may indicate a client misconfiguration, expired token use, or brute-force attack. See #11180.

• FEATURE: alerts: add AlertingRuleResultsApproachingLimit and RecordingRuleResultsApproachingLimit alerting rules to vmalert alerts. These alerts notify when a rule's last evaluation samples exceed 90% of the configured group results limit. See #11179. Thanks to @vinyas-bharadwaj for the contribution.

• FEATURE: vmauth: prevent possible password brute-force attacks with an artificial 2-3 second delay as recommended by OWASP. See #11180.

• FEATURE: vmauth: allow log requests with missing or invalid auth tokens to access log. This is useful for identifying remote_addr IPs performing brute-force attacks. See #11180.

• FEATURE: vmauth: fall through to unauthorized_user when a JWT token has no vm_access claim and no default_vm_access_claim is configured. Previously, vmauth returned 401 Unauthorized immediately in this case, which prevented unauthorized_user from handling such requests. See #5740.

• FEATURE: MetricsQL: improve the selection algorithm of buckets_limit to remove consecutive empty buckets at the beginning and end to obtain more accurate min and max values. See #10417.

• FEATURE: vmalert: expose vmalert_group_rule_results_limit metric to indicate the number of alerts or recording results that a single rule within the group can produce. See #11179. Thanks to @vinyas-bharadwaj for the contribution.

• BUGFIX: all VictoriaMetrics components: cancel in-flight HTTP requests shortly before -http.maxGracefulShutdownDuration elapses during graceful shutdown, so they can drain and the shutdown completes cleanly within that window instead of timing out and exiting via logger.Fatalf -> os.Exit. This prevents skipping the storage flush and losing in-memory data when long-lived requests are in flight (such as VictoriaLogs live tailing). See #1502.

• BUGFIX: vminsert in VictoriaMetrics cluster and vmsingle: properly check values range for the limits configured with flags -maxLabelsPerTimeseries, -maxLabelNameLen and -maxLabelValueLen. It must be in range 1..65535. See #11128.

• BUGFIX: vminsert in VictoriaMetrics cluster: fixes unexpected rare rerouting. See #11162.

• BUGFIX: vmselect in VictoriaMetrics cluster: propagate cache reset operation to selectNode when /internal/resetRollupResultCache is called. Previously, the propagation only happened when the delete_series API was called. See #11112.

• BUGFIX: stream aggregation: fix possible unexpected increases in rate_avg and rate_sum if an out-of-order sample is ingested after the previous flush. See #11140.

• BUGFIX: vmctl: properly URL-encode -vm-extra-label values when building import requests, so special characters such as & don't get split into broken query parameters. See #11144. Thanks to @immanuwell for contribution.

• BUGFIX: enterprise vmagent: ignore enable.auto.offset.store option in kafka.consumer.topic.options, since vmagent manages offset storage internally. Previously, setting this option could cause vmagent to stop committing Kafka messages. See #11208.

v1.122.26

Released at 2026-07-03

v1.122.x is a line of LTS releases. It contains important up-to-date bugfixes for VictoriaMetrics enterprise. All these fixes are also included in the latest community release. The v1.122.x line will be supported for at least 12 months since v1.122.0 release

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

• BUGFIX: vminsert in VictoriaMetrics cluster and vmsingle: properly check values range for the limits configured with flags -maxLabelsPerTimeseries, -maxLabelNameLen and -maxLabelValueLen. It must be in range 1..65535. See #11128.

• BUGFIX: stream aggregation: fix possible unexpected increases in rate_avg and rate_sum if an out-of-order sample is ingested after the previous flush. See #11140.

• BUGFIX: vmselect in VictoriaMetrics cluster: propagate cache reset operation to selectNode when /internal/resetRollupResultCache is called. Previously, the propagation only happened when the delete_series API was called. See #11112.

• BUGFIX: vmctl: properly URL-encode -vm-extra-label values when building import requests, so special characters such as & don't get split into broken query parameters. See #11144. Thanks to @immanuwell for contribution.

• BUGFIX: all VictoriaMetrics components: cancel in-flight HTTP requests shortly before -http.maxGracefulShutdownDuration elapses during graceful shutdown, so they can drain and the shutdown completes cleanly within that window instead of timing out and exiting via logger.Fatalf -> os.Exit. This prevents skipping the storage flush and losing in-memory data when long-lived requests are in flight (such as VictoriaLogs live tailing). See #1502.

v1.136.13

Released at 2026-07-03

v1.136.x is a line of LTS releases. It contains important up-to-date bugfixes for VictoriaMetrics enterprise. All these fixes are also included in the latest community release. The v1.136.x line will be supported for at least 12 months since v1.136.0 release

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

• BUGFIX: vminsert in VictoriaMetrics cluster and vmsingle: properly check values range for the limits configured with flags -maxLabelsPerTimeseries, -maxLabelNameLen and -maxLabelValueLen. It must be in range 1..65535. See #11128.

• BUGFIX: vminsert in VictoriaMetrics cluster: fixes unexpected rare rerouting. See #11162.

• BUGFIX: vmselect in VictoriaMetrics cluster: propagate cache reset operation to selectNode when /internal/resetRollupResultCache is called. Previously, the propagation only happened when the delete_series API was called. See #11112.

• BUGFIX: stream aggregation: fix possible unexpected increases in rate_avg and rate_sum if an out-of-order sample is ingested after the previous flush. See #11140.

• BUGFIX: vmctl: properly URL-encode -vm-extra-label values when building import requests, so special characters such as & don't get split into broken query parameters. See #11144. Thanks to @immanuwell for contribution.

• BUGFIX: enterprise vmagent: ignore enable.auto.offset.store option in kafka.consumer.topic.options, since vmagent manages offset storage internally. Previously, setting this option could cause vmagent to stop committing Kafka messages. See #11208.

• BUGFIX: all VictoriaMetrics components: cancel in-flight HTTP requests shortly before -http.maxGracefulShutdownDuration elapses during graceful shutdown, so they can drain and the shutdown completes cleanly within that window instead of timing out and exiting via logger.Fatalf -> os.Exit. This prevents skipping the storage flush and losing in-memory data when long-lived requests are in flight (such as VictoriaLogs live tailing). See #1502.

v1.136.12

Released at 2026-06-19

v1.136.x is a line of LTS releases. It contains important up-to-date bugfixes for VictoriaMetrics enterprise. All these fixes are also included in the latest community release. The v1.136.x line will be supported for at least 12 months since v1.136.0 release

• BUGFIX: stream aggregation: fix issue with producing aggregated samples with identical timestamps between flushes. See #10808.
• BUGFIX: vmalert,vmauth,vmagent and vmsingle: fix rare unbounded shutdown delay when config reload takes longer than -configCheckInterval. See #11107. Thanks to @PleasingFungus for contribution.
• BUGFIX: vmselect in VictoriaMetrics cluster: fix corrupted metrics metadata when a response contains multiple rows. See #11115. Thanks for @fxrlv for the contribution.
• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: properly escape metricFamilyName at metrics metadata response. See #11129. Thanks for @fxrlv for the contribution.
• BUGFIX: vmagent: fix potential corruption of remote-write metadata Unit values. See #11120. Thanks for @fxrlv for the contribution.
• BUGFIX: vmselect in VictoriaMetrics cluster: correctly apply long tenant filters. Previously, such filters could be truncated, causing tenants to be matched incorrectly. See #11096. Thanks for @fxrlv for the contribution.
• BUGFIX: vmbackup, vmbackupmanager: do not fail backup list if directory is absent while using fs:// destination to align with other protocols. See 6c3c548d
• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: prevent more cases of panic during directory deletion on NFS-based mounts. See #11060.
• BUGFIX: vmctl: push metrics to configured -pushmetrics.url on shutdown when migration fails. Previously, metrics were not pushed if vmctl exited with an error. See #11081. Thanks to @zasdaym for contribution.
• BUGFIX: vmrestore: disallow restoring parts outside the configured -storageDataPath directory. See 710c920d.