Skip to content
Release Radar

VictoriaMetrics

Monitoring & Observability

Fast, cost-effective monitoring solution and time series database

VictoriaMetrics/VictoriaMetricsWebsiteDocumentation
v1.152.0same day as v1.148.4
View on GitHub

Part of VictoriaMetrics

Release history

v1.152.0

CompareGitHub

v1.152.0

Released at 2026-09-11

  • SECURITY: upgrade Go builder from Go1.26.6 to Go1.27.1. See Go 1.27 release notes.

  • SECURITY: vmauth: fix authorization bypass in JWT-based routing when match_claims values are used. See GHSA-f99m-22fh-qw96.

  • SECURITY: vmsingle and vmselect in VictoriaMetrics cluster: properly escape server-side errors returned by /metric-relabel-debug since they could contain parts of user input. This prevents XSS attacks on the /vmui/#/relabeling page. See GHSA-vw10j-rqhg-qff9.

  • FEATURE: vmauth: add the deny_paths option to url_map to reject a subset of paths matched by src_paths or other src_* options with 403 Forbidden (401 Unauthorized for anonymous requests) instead of enumerating every allowed path. See #11452. Thanks to @andriibeee for contribution.

  • FEATURE: alerts-health: split TooManyLogs alert into TooManyErrorLogs and TooManyLogs. TooManyLogs now covers only warn-level logs and aggregates them per job and instance. TooManyErrorLogs fires on error, fatal, and panic logs with per-location granularity, making it easier to identify the exact source of critical log messages. See #11417.

  • FEATURE: vmui: show the range between the minimum and maximum values for each graph line in the legend. See #11425. Thanks to @umer901 for contribution.

  • BUGFIX: all VictoriaMetrics components: hide values passed to -pushmetrics.header in startup logs, /metrics, and /flags, since they can contain sensitive HTTP headers such as Authorization and API keys. See #11545.

  • BUGFIX: vmsingle, vmagent and vminsert in VictoriaMetrics cluster: fix insert requests getting stuck after another insert request times out, causing clients to time out while waiting for a response. See VictoriaLogs#1743.

  • BUGFIX: vmselect in VictoriaMetrics cluster: apply the le filter at /api/v1/status/metric_names_stats after merging request counters from all vmstorage nodes. Previously, the endpoint could report actively queried metrics as unused when the local request counter was zero on one of the nodes. See #11473. Thanks to @missusk for contribution.

  • BUGFIX: vmagent: now MDX discards cardinality_estimate and cardinality_churn_ratio metrics exposed by vmestimator service. #11501.

  • BUGFIX: vmselect in VictoriaMetrics cluster: allow access to /prometheus/api/v1/admin/tsdb/delete_series and graphite/tags/delSeries using only the corresponding -deleteAuthKey, even when -httpAuth.* is also configured, without additionally requiring -httpAuth.* credentials. See #11512.

v1.148.4

Released at 2026-09-11

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

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

  • SECURITY: vmauth: fix authorization bypass in JWT-based routing when match_claims values are used. See GHSA-f99m-22fh-qw96.

  • SECURITY: vmsingle and vmselect in VictoriaMetrics cluster: properly escape server-side errors returned by /metric-relabel-debug since they could contain parts of user input. This prevents XSS attacks on the /vmui/#/relabeling page. See GHSA-vw10j-rqhg-qff9.

  • BUGFIX: all VictoriaMetrics components: hide values passed to -pushmetrics.header in startup logs, /metrics, and /flags, since they can contain sensitive HTTP headers such as Authorization and API keys. See #11545.

  • BUGFIX: vmsingle, vmagent and vminsert in VictoriaMetrics cluster: fix insert requests getting stuck after another insert request times out, causing clients to time out while waiting for a response. See VictoriaLogs#1743.

  • BUGFIX: vmselect in VictoriaMetrics cluster: apply the le filter at /api/v1/status/metric_names_stats after merging request counters from all vmstorage nodes. Previously, the endpoint could report actively queried metrics as unused when the local request counter was zero on one of the nodes. See #11473. Thanks to @missusk for contribution.

  • BUGFIX: vmagent: now MDX discards cardinality_estimate and cardinality_churn_ratio metrics exposed by vmestimator service. #11501.

  • BUGFIX: vmselect in VictoriaMetrics cluster: allow access to /prometheus/api/v1/admin/tsdb/delete_series and graphite/tags/delSeries using only the corresponding -deleteAuthKey, even when -httpAuth.* is also configured, without additionally requiring -httpAuth.* credentials. See #11512.

v1.151.0

Released at 2026-08-28

  • SECURITY: vmsingle, vmagent, vminsert and vmselect in VictoriaMetrics cluster: check HTTP Basic Auth credentials from the -httpAuth.* command-line flags for cases that do not verify the corresponding *AuthKey command-line flag on its own. Previously, HTTP Basic Auth could be skipped for request paths ending with suffixes such as /config, /reload. For example, /api/v1/import/prometheus/config was routed to the data ingestion handler /api/v1/import/prometheus without checking -httpAuth.* credentials.

  • FEATURE: all VictoriaMetrics components: add support for accepting HTTP requests over Unix domain socket at -httpListenAddr. For example, -httpListenAddr=unix:/run/victoria-metrics.sock. See VictoriaLogs#1618.

  • FEATURE: vmagent, vmsingle, vmstorage and vmselect in VictoriaMetrics cluster: expose the vm_app_prev_shutdown_unclean gauge. It is set to 1 when the previous process run didn't shut down cleanly. Added the UncleanShutdown alerting rule, which fires for 10 minutes after an unclean shutdown is detected. See #8443.

  • FEATURE: vmui: show the selected time zone UTC offset next to the date/time controls and allow opening time zone settings from it. See #11332.

  • FEATURE: vmsingle, vmagent, vmalert, and vmselect in VictoriaMetrics cluster: show how the default value is calculated for command-line flags which derive it from the number of available CPU cores. For example, -maxConcurrentInserts now prints (default 16 = 2*cgroup.AvailableCPUs()) in -help output instead of (default 16). Updated flags: -search.maxConcurrentRequests, -search.maxWorkersPerQuery, -fs.maxConcurrency, -remoteWrite.concurrency, -remoteWrite.queues. See #9680. Thanks to @Vandit1604 for contribution.

  • FEATURE: vmagent: introduce vmagent_kafka_consumer_broker_rtt_seconds and vmagent_kafka_consumer_fetch_queue_size metrics for Kafka consumer integration. These metrics help troubleshoot slow Kafka consumption. See #11342.

  • BUGFIX: alerts: fix AlertingRuleResultsApproachingLimit and RecordingRuleResultsApproachingLimit alerting rules in vmalert alerting rules. The alerts could produce incorrect results or fail to fire when vmalert_group_rule_results_limit returned multiple samples per (group, file) label combination, causing the on(group,file) group_left() vector matching to fail. See #11449.

  • BUGFIX: vmagent and vminsert in VictoriaMetrics cluster: fix infinite loop in the OpenTelemetry Firehose ingestion endpoint (/opentelemetry/api/v1/push) when receiving a malformed record with an incomplete varint in the data field. Previously this caused the goroutine to spin forever, permanently consuming CPU until the process was restarted. See #11424.

  • BUGFIX: vmalert-tool: reuse connections to -remoteWrite.url when writing the results of recording rules and alerts. Previously every series was sent over a new connection, which left a lot of sockets in TIME_WAIT state and could exhaust the ephemeral port range. The number of idle connections can be tuned via the new -remoteWrite.maxIdleConnections command-line flag. See #11387. Thanks @evkuzin for contribution.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: prevent process crash in sort_by_label_numeric() and sort_by_label_numeric_desc() when a label value contains a number with 309 or more digits. See #11423.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: fixes rare metrics metadata partial search response. See #11384.

  • BUGFIX: vmctl: reuse connections in vm-native mode when --vm-concurrency exceeds 2. Previously the number of idle connections was limited to 2 per host, which was insufficient when --vm-concurrency was bigger than 2. See #11451.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: properly re-use memory if query aggregation returns error. See #11426.

  • BUGFIX: vmselect in VictoriaMetrics cluster: fail the query request directly when there is not enough disk space to store temporary search results. Previously, such queries could lead to vmselect crash. See #4688.

  • BUGFIX: vmselect in VictoriaMetrics cluster: consistently re-use memory during storage blocks unpacking on parsing storage block error. See #11421.

  • BUGFIX: vmalert: fix parsing of instant query sample timestamps from Prometheus-compatible data sources. Previously, decimal (e.g. 1786458420.123) or scientific-notation (e.g. 1.78645842E9) values were silently truncated to 0. See #11396. Thanks to @missusk for the contribution.

  • BUGFIX: vmctl: properly release the export and import requests during migration requests fails in vm-native mode. Previously, failed export/import requests could have left hanging at the source or the destination. The fix is supposed to improve the resiliency of vmctl during long-running migrations.

  • BUGFIX: vmagent: include vm_account_id and vm_project_id labels in the instance identity used by monitoring data exchange filtering. Previously, when multitenant handlers were enabled, series from different tenants sharing the same job and instance labels could be misidentified as coming from a discovered VictoriaMetrics instance and leak into the -remoteWrite.mdx.enable destination. See #11381.

  • BUGFIX: vmsingle, vminsert in VictoriaMetrics cluster and vmagent: fix process crash at /api/v1/import/native endpoint when receiving a specially crafted ~45-byte request. #11471.

  • BUGFIX: vmsingle, vmagent and vmstorage in

…(truncated)

v1.148.3

Released at 2026-08-28

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

  • SECURITY: vmsingle, vmagent, vminsert and vmselect in VictoriaMetrics cluster: check HTTP Basic Auth credentials from the -httpAuth.* command-line flags for cases that do not verify the corresponding *AuthKey command-line flag on its own. Previously, HTTP Basic Auth could be skipped for request paths ending with suffixes such as /config, /reload. For example, /api/v1/import/prometheus/config was routed to the data ingestion handler /api/v1/import/prometheus without checking -httpAuth.* credentials.

  • BUGFIX: vmagent and vminsert in VictoriaMetrics cluster: fix infinite loop in the OpenTelemetry Firehose ingestion endpoint (/opentelemetry/api/v1/push) when receiving a malformed record with an incomplete varint in the data field. Previously this caused the goroutine to spin forever, permanently consuming CPU until the process was restarted. See #11424.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: prevent process crash in sort_by_label_numeric() and sort_by_label_numeric_desc() when a label value contains a number with 309 or more digits. See #11423.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: fixes rare metrics metadata partial search response. See #11384.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: properly re-use memory if query aggregation returns error. See #11426.

  • BUGFIX: vmselect in VictoriaMetrics cluster: fail the query request directly when there is not enough disk space to store temporary search results. Previously, such queries could lead to vmselect crash. See #4688.

  • BUGFIX: vmselect in VictoriaMetrics cluster: consistently re-use memory during storage blocks unpacking on parsing storage block error. See #11421.

  • BUGFIX: vmalert: fix parsing of instant query sample timestamps from Prometheus-compatible data sources. Previously, decimal (e.g. 1786458420.123) or scientific-notation (e.g. 1.78645842E9) values were silently truncated to 0. See #11396. Thanks to @missusk for the contribution.

  • BUGFIX: vmctl: properly release the export and import requests during migration requests fails in vm-native mode. Previously, failed export/import requests could have left hanging at the source or the destination. The fix is supposed to improve the resiliency of vmctl during long-running migrations.

  • BUGFIX: vmctl: reuse connections in vm-native mode when --vm-concurrency exceeds 2. Previously the number of idle connections was limited to 2 per host, which was insufficient when --vm-concurrency was bigger than 2. See #11451.

  • BUGFIX: vmagent: include vm_account_id and vm_project_id labels in the instance identity used by monitoring data exchange filtering. Previously, when multitenant handlers were enabled, series from different tenants sharing the same job and instance labels could be misidentified as coming from a discovered VictoriaMetrics instance and leak into the -remoteWrite.mdx.enable destination. See #11381.

  • BUGFIX: vmsingle, vminsert in VictoriaMetrics cluster and vmagent: fix process crash at /api/v1/import/native endpoint when receiving a specially crafted ~45-byte request. #11471.

  • BUGFIX: vmsingle, vmagent and vmstorage in VictoriaMetrics cluster: allow access to /remotewrite-relabel-config, /api/v1/status/remotewrite-relabel-config, /remotewrite-url-relabel-config, /api/v1/status/remotewrite-url-relabel-config and /internal/log_new_series with only the corresponding -configAuthKey or -logNewSeriesAuthKey, even when -httpAuth.* is also configured, without additionally requiring -httpAuth.* credentials. See bedc69014.

v1.150.0

Released at 2026-08-14

Update Note 1: vmselect and vminsert in VictoriaMetrics cluster, and vmagent: default value of -enableMultitenancyViaHeaders command-line flag has changed from false to true. This change enables support of multitenancy via headers for cluster and for vmagent by default. With this change, mentioned components will start supporting URLs with omitted tenant ID in the path: https://<vmselect>:8481/select/prometheus/api/v1/query will become a valid URL. To disable multitenancy via headers and simplified URLs set --enableMultitenancyViaHeaders=false on vmagent, vminsert and vmselect.

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

  • FEATURE: relabeling: reduce CPU usage up to 30% when matching relabeling rules with multiple if expressions containing exact metric names. Expressions for other metric names are now skipped before evaluating their remaining label filters. See #11341. Thanks to @nevgeny for contribution.

  • FEATURE: vmagent and vmsingle: add support for linode_sd_configs for discovering scrape targets from Linode instances. See #9118. Thanks to @cxdy for contribution.

  • FEATURE: vmalert: extend -replay.continueWithExecutionErr to also handle the 400 Bad Request response code, since it is used for Prometheus querying API requests when request parameters are missing or incorrect. See #11352.

  • FEATURE: vmselect and vminsert in VictoriaMetrics cluster, and vmagent: set default value of -enableMultitenancyViaHeaders to true. This change enables support of multitenancy via headers for cluster and for vmagent by default, aligning VictoriaMetrics multitenancy behavior with multitenancy in VictoriaLogs. See related ticket #11365.

  • FEATURE: vmui: add an option to customize the favicon color. This makes it easier to distinguish between different installations opened in multiple browser tabs. See #11329.

  • BUGFIX: vmagent and vmsingle: avoid suggesting the unrelated -enableTCP6 command-line flag when scraping a target over a Unix domain socket fails. See #11320. Thanks to @lwmacct for contribution.

  • BUGFIX: vmsingle and vminsert in VictoriaMetrics cluster: skip labels with empty name at /api/v1/import. Previously such a label replaced the metric name, so a series sent with "metric":{"__name__":"foo","":"bar"} was stored under the name bar. Other ingestion protocols already skip such labels. See #4962. Thanks to @Vandit1604 for contribution.

  • BUGFIX: vmsingle, vmselect in VictoriaMetrics cluster and vmctl: properly parse small fractional Unix timestamps in 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, fractional Unix timestamps with the integer part below 9223372 were interpreted with the wrong unit, for example 12.0 was parsed as 12000 seconds instead of 12 seconds. See #11324.

  • BUGFIX: vmsingle, vmstorage and vmselect in VictoriaMetrics cluster: persist the previous working set cache during graceful shutdown when it is likely to contain the active working set. This prevents saving an empty or cold current cache right after split-mode cache rotation, which could otherwise slow down ingestion or queries after restart until the cache warms up again. See #11299.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: change the HTTP response code for Prometheus querying API requests from 422 Unprocessable Entity to 400 Bad Request when request parameters are missing or incorrect. See #11330.

  • BUGFIX: vmui: respect the custom query step specified via g0.step_input when opening a URL. Previously, it could be reset to the automatically calculated step and potentially cause dashboards to freeze. See #11137.

  • BUGFIX: vmagent and vmsingle: properly assign scrape target IP address at IPv6-only networks for docker_sd_configs. See #10965.

  • BUGFIX: vmalert: rename vmalert_rule_group_results_limit back to vmalert_group_rule_results_limit. The metric was introduced in v1.147.0 but was accidentally given the wrong name. See #11179.

  • BUGFIX: vmalert: properly update group-level eval_delay and eval_alignment for existing groups during runtime when config reload is triggered periodically or manually via /-/reload. Previously, these settings weren't updated after config reload during runtime. See #11374.

  • BUGFIX: vmselect in VictoriaMetrics cluster: scale the default -search.maxConcurrentRequests with the number of available CPU cores instead of capping it at 16. See #11191. Thanks to @Dhru1Tanna for contribution.

v1.148.2

Released at 2026-08-14

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

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

  • BUGFIX: vmsingle, vmselect in VictoriaMetrics cluster and vmctl: properly parse small fractional Unix timestamps in 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, fractional Unix timestamps with the integer part below 9223372 were interpreted with the wrong unit, for example 12.0 was parsed as 12000 seconds instead of 12 seconds. See #11324.

  • BUGFIX: vmsingle, vmstorage and vmselect in VictoriaMetrics cluster: persist the previous working set cache during graceful shutdown when it is likely to contain the active working set. This prevents saving an empty or cold current cache right after split-mode cache rotation, which could otherwise slow down ingestion or queries after restart until the cache warms up again. See #11299.

  • BUGFIX: vmagent and vmsingle: properly assign scrape target IP address at IPv6-only networks for docker_sd_configs. See #10965.

  • BUGFIX: vmagent and vmsingle: avoid suggesting the unrelated -enableTCP6 command-line flag when scraping a target over a Unix domain socket fails.

  • BUGFIX: vmui: respect the custom query step specified via g0.step_input when opening a URL. Previously, it could be reset to the automatically calculated step and potentially cause dashboards to freeze. See #11137.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: change the HTTP response code for Prometheus querying API requests from 422 Unprocessable Entity to 400 Bad Request when request parameters are missing or incorrect. See #11330.

  • BUGFIX: vmsingle and vminsert in VictoriaMetrics cluster: skip labels with empty name at /api/v1/import. Previously such a label replaced the metric name, so a series sent with "metric":{"__name__":"foo","":"bar"} was stored under the name bar. Other ingestion protocols already skip such labels. See #4962.

  • BUGFIX: vmalert: rename vmalert_rule_group_results_limit back to vmalert_group_rule_results_limit. The metric was introduced in v1.147.0 but was accidentally given the wrong name. See #11179.

  • BUGFIX: vmalert: properly update group-level eval_delay and eval_alignment for existing groups during runtime when config reload is triggered periodically or manually via /-/reload. Previously, these settings weren't updated after config reload during runtime. See #11374.

  • BUGFIX: vmselect in VictoriaMetrics cluster: scale the default -search.maxConcurrentRequests with the number of available CPU cores instead of capping it at 16. See #11191. Thanks to @Dhru1Tanna for contribution.

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-20

Update Note 1: vmalert-tool: the default start timestamp of tests has changed in #11219 from 1970-01-01T00:00:00 to 2000-01-01T00:00:00 to enable global index disablement. As a result, tests involving functions that depend on the current time, such as time() and day_of_*(), may produce different results. See #11437.

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

Update Note 2: vmalert: vmalert updates VictoriaLogs LogsQL query parser to v1.51.0, which contains a breaking change in LogsQL filter pipes handling. If you used vmalert with vlogs query type and query expressions contained deprecated syntax - these rules will fail the validation on vmalert restart. Please review the VictoriaLogs v1.51.0 changelog and update your alerting rules accordingly before upgrading.

  • 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](https://docs.victoriametrics

…(truncated)

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

Update Note 1: vmalert: vmalert updates VictoriaLogs LogsQL query parser to v1.51.0, which contains a breaking change in LogsQL filter pipes handling. If you used vmalert with vlogs query type and query expressions contained deprecated syntax - these rules will fail the validation on vmalert restart. Please review the VictoriaLogs v1.51.0 changelog and update your alerting rules accordingly before upgrading.

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

Released at 2026-06-22

  • FEATURE: all VictoriaMetrics components: add -http.header.disableServerHostname command-line flag for disabling the X-Server-Hostname HTTP response header. See #11067. Thanks to @zasdaym for contribution.

  • FEATURE: stream aggregation: expose vm_streamaggr_dedup_dropped_samples_total to allow tracking dropped old samples during deduplication.

  • FEATURE: stream aggregation: use the aggregation rule interval as the default staleness_interval instead of 2*interval, to reduce spikes when there are gaps between received samples. See #11102.

  • FEATURE: stream aggregation: add new aggregation output sum_samples_total for summing input delta values into a cumulative counter. See issues #11002 and #4843.

  • FEATURE: vmagent: add a new flag -remoteWrite.inmemoryQueues to prioritize recently ingested data over historical data stored at file-based persistent queue. See #8833

  • FEATURE: vmagent: add -promscrape.cluster.shardByLabels command-line flag for selecting target labels used for sharding scrape targets among vmagent instances in cluster mode. See #11044.

  • FEATURE: vmctl: add -vm-headers and -vm-bearer-token flags for authenticating requests to the VictoriaMetrics import destination. The flags are available in opentsdb, influx, remote-read, prometheus, mimir, and thanos vmctl sub-commands. See #8897.

  • FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: log calls to /api/v1/admin/tsdb/delete_series API handler. This should help to identify events of metrics deletion from the database. See #11104.

  • FEATURE: vmui: add the last value to graph legend statistics. See #10759.

  • BUGFIX: enterprise vmsingle and vmstorage in VictoriaMetrics cluster: properly expose metric vm_retention_filters_partitions_scheduled_rows. See #11138

  • BUGFIX: stream aggregation: fix issue with producing aggregated samples with identical timestamps between flushes. See #10808.

  • BUGFIX: vmagent: fix potential corruption of remote-write metadata Unit values. See #11120. Thanks for @fxrlv for the contribution.

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

  • 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: vmselect in VictoriaMetrics cluster: fix corrupted metrics metadata when a response contains multiple rows. See #11115. 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 6c3c548

  • BUGFIX: vmselect in VictoriaMetrics cluster: don't cache empty responses for tenant IDs discovery during multitenant queries. This problem was visible during integration tests when multitenant queries were executed before the first ingestion happened. See #10982

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: properly escape metricFamilyName at metrics metadata response. See #11129. Thanks for @fxrlv for the contribution.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: prevent more cases of panic during directory deletion on NFS-based mounts. See #11060.

v1.122.25

Released at 2026-06-19

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

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.

v1.136.11

Released at 2026-06-05

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.3 to Go1.26.4. See the list of issues addressed in Go1.26.4.

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