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 rulesNoLatestBackupWithinLastDay, 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: 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.
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.148.0` → `v1.149.0` |
---
### Release Notes
<details>
<summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)</summary>
### [`v1.149.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.149.0)
[Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.148.0...v1.149.0)
##### [v1.149.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.149.0)
Released at 2026-07-31
**Update Note 1:** `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): the default value of `-disableRerouting` flag has changed from `true` to `false`, enabling [slowness-based re-routing](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#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](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/11287).
**Update Note 2:** [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): 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](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5552).
- SECURITY: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): restrict `/api/v1/admin/tsdb/delete_series`, `/tags/delSeries` endpoints to `POST` method only to prevent some [SSRF](https://en.wikipedia.org/wiki/Server-side_request_forgery)-based data deletion attacks. See [#​5552](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5552).
- FEATURE: [dashboards](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/master/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](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10432).
- FEATURE: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): add `name` label identifying the corresponding `-remoteWrite.url` target to the `vm_persistentqueue_*` metrics exposed by persistent queue. See [#​7944](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7944). Thanks to [@​tIGO](https://github.com/tIGO) for contribution.
- FEATURE: [vmagent](https://docs.victoriametrics.com/victoriametrics/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](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10599).
- FEATURE: [vmalert](https://docs.victoriametrics.com/victoriametrics/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](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11313).
- FEATURE: [vmalert](https://docs.victoriametrics.com/victoriametrics/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](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11232). Thanks to [@​1solomonwakhungu](https://github.com/1solomonwakhungu) for contribution.
- FEATURE: [vmbackupmanager](https://docs.victoriametrics.com/victoriametrics/vmbackupmanager/) and [alerts](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/rules): introduce `vm_backup_last_success_at` metric to track the last successful backup by type. Add [alerting rules](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/rules/alerts-vmbackupmanager.yml) `NoLatestBackupWithinLastDay`, `NoHourlyBackupWithinLastDay`, `NoDailyBackupWithinLast3Days`, `NoWeeklyBackupWithinLast14Days` and `NoMonthlyBackupWithinLast62Days` to remind users about the missing backups. See [#​11217](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11217).
- FEATURE: [vmctl](https://docs.victoriametrics.com/victoriametrics/vmctl/): support [Prometheus native histograms](https://prometheus.io/docs/specs/native_histograms/) migration in [remote read mode](https://docs.victoriametrics.com/victoriametrics/vmctl/remoteread/). 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](https://docs.victoriametrics.com/victoriametrics/integrations/prometheus/#native-histograms), 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](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11292). Thanks to [@​liuxu623](https://github.com/liuxu623) for contribution.
- FEATURE: `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): enable [slowness-based re-routing](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#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](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/11287).
- FEATURE: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): persist the selected auto-refresh interval in the URL. See [VictoriaLogs#1310](https://github.com/VictoriaMetrics/VictoriaLogs/issues/1310).
- BUGFIX: [MetricsQL](https://docs.victoriametrics.com/victoriametrics/metricsql/): properly drop data points filtered out by an inner [comparison operation](https://prometheus.io/docs/prometheus/latest/querying/operators/#comparison-binary-operators) 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](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10018). Thanks to [@​zasdaym](https://github.com/zasdaym) for contribution.
- BUGFIX: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/) and [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/): ignore HTTP proxy environment variables when scraping targets over Unix domain sockets. See [#​11318](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/11318). Thanks to [@​lwmacct](https://github.com/lwmacct) for contribution.
- BUGFIX: [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/): fixed the display of rule state badges on the `Groups` page in the web UI. See [#​11160](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11160).
- BUGFIX: [vmbackupmanager](https://docs.victoriametrics.com/victoriametrics/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](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11217).
- BUGFIX: [stream aggregation](https://docs.victoriametrics.com/victoriametrics/stream-aggregation/): fix incorrect [sum\_samples\_total](https://docs.victoriametrics.com/victoriametrics/stream-aggregation/configuration/#sum_samples_total) results when `enable_windows: true` is set. See [#​11261](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11261). Thanks to [@​beyond-infra](https://github.com/beyond-infra) for contribution.
- BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/), `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/) and [vmctl](https://docs.victoriametrics.com/victoriametrics/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](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11268). Thanks to [@​STiFLeR7](https://github.com/STiFLeR7) for contribution.
</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 CLI](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMy4zIiwidXBkYXRlZEluVmVyIjoiNDQuMTMuMyIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6W119-->
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.148.0→v1.149.0Release Notes
VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)
v1.149.0Compare Source
v1.149.0
Released at 2026-07-31
Update Note 1:
vminsertin VictoriaMetrics cluster: the default value of-disableReroutingflag has changed fromtruetofalse, enabling slowness-based re-routing by default. Slowness re-routing is automatically disabled when-replicationFactoris greater than 1. If you rely on the old behavior, pass-disableReroutingcommand-line flag tovminsert. See #11287.Update Note 2: vmsingle and
vmselectin VictoriaMetrics cluster: the/api/v1/admin/tsdb/delete_series,/tags/delSeriesendpoints now requirePOSTmethod. Previously, it also acceptedGETrequests. If you useGETrequests for this endpoint, update your scripts or tooling to usePOSTinstead. See #5552.SECURITY: vmsingle and
vmselectin VictoriaMetrics cluster: restrict/api/v1/admin/tsdb/delete_series,/tags/delSeriesendpoints toPOSTmethod only to prevent some SSRF-based data deletion attacks. See #5552.FEATURE: dashboards: add
Fsync avg durationpanel 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
namelabel identifying the corresponding-remoteWrite.urltarget to thevm_persistentqueue_*metrics exposed by persistent queue. See #7944. Thanks to @tIGO for contribution.FEATURE: vmagent: add
-remoteWrite.obfuscateLabelsflag 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.continueWithExecutionErrflag 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
$intervalto 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_atmetric to track the last successful backup by type. Add alerting rulesNoLatestBackupWithinLastDay,NoHourlyBackupWithinLastDay,NoDailyBackupWithinLast3Days,NoWeeklyBackupWithinLast14DaysandNoMonthlyBackupWithinLast62Daysto 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,_sumand_bucketseries withvmrangelabels 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 inSAMPLESmode, while in stream mode the migration failed withEOFerror. See #11292. Thanks to @liuxu623 for contribution.FEATURE:
vminsertin VictoriaMetrics cluster: enable slowness-based re-routing by default. Previously,-disableReroutingdefaulted totrue, which limited ingestion throughput to the slowestvmstoragenode. Now-disableReroutingdefaults tofalse, sovminsertautomatically routes data away from the slowestvmstoragenode, improving overall ingestion performance. Slowness re-routing is automatically disabled when-replicationFactoris 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 asNaN, andvalue != NaNevaluates totrue. Comparisons against explicitly presentNaNvalues 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
Groupspage in the web UI. See #11160.BUGFIX: vmbackupmanager: previously,
vmbackupmanagerwas 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. Addedvm_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: trueis set. See #11261. Thanks to @beyond-infra for contribution.BUGFIX: vmsingle,
vmselectin VictoriaMetrics cluster and vmctl: accept scientific notation with sub-second precision (e.g.1.784144612388E9) for timestamp args such asstartandendin/api/v1/query_rangeand--vm-native-filter-time-startand--vm-native-filter-time-endinvmctl. Previously, values with this pattern were rejected, which is incompatible with Prometheus. See #11268. Thanks to @STiFLeR7 for contribution.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 CLI.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.