# VictoriaMetrics v1.151.0

- Product: VictoriaMetrics (https://whatsnew.fyi/product/victoriametrics)
- Vendor: VictoriaMetrics
- Date: 2026-08-31
- Version: v1.151.0
- Original notes: https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.151.0
- Permalink: https://whatsnew.fyi/product/victoriametrics/releases/v1.151.0

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **security** — Check HTTP Basic Auth credentials from -httpAuth.* command-line flags for all request paths, including those ending with suffixes such as /config or /reload, preventing bypass of authentication
- **added** — Add support for accepting HTTP requests over Unix domain socket at -httpListenAddr
- **added** — Expose vm_app_prev_shutdown_unclean gauge which is set to 1 when the previous process run did not shut down cleanly
- **added** — Show selected time zone UTC offset next to date/time controls in vmui and allow opening time zone settings from it
- **added** — Display how default values are calculated for command-line flags derived from CPU cores in help output
- **added** — Introduce vmagent_kafka_consumer_broker_rtt_seconds and vmagent_kafka_consumer_fetch_queue_size metrics for Kafka consumer integration troubleshooting
- **fixed** — Fix AlertingRuleResultsApproachingLimit and RecordingRuleResultsApproachingLimit alerting rules to handle multiple samples per label combination correctly
- **fixed** — Fix infinite loop in OpenTelemetry Firehose ingestion endpoint when receiving malformed record with incomplete varint in data field
- **fixed** — Reuse connections to remote write URL in vmalert-tool and add -remoteWrite.maxIdleConnections flag to tune idle connections
- **fixed** — Prevent process crash in sort_by_label_numeric() and sort_by_label_numeric_desc() when label value contains number with 309 or more digits

##### [v1.151.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.151.0)

Released at 2026-08-28

* SECURITY: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/), [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/), `vminsert` and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): 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](https://github.com/VictoriaMetrics/VictoriaLogs/issues/1618).
* FEATURE: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/), [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/), `vmstorage` and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): 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](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/rules/alerts-health.yml), which fires for 10 minutes after an unclean shutdown is detected. See [#8443](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8443).
* FEATURE: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): show the selected time zone UTC offset next to the date/time controls and allow opening time zone settings from it. See [#11332](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/11332).
* FEATURE: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/), [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/), [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/), and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): 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](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9680). Thanks to @Vandit1604 for contribution.
* FEATURE: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): introduce `vmagent_kafka_consumer_broker_rtt_seconds` and `vmagent_kafka_consumer_fetch_queue_size` metrics for [Kafka consumer integration](https://docs.victoriametrics.com/victoriametrics/integrations/kafka/). These metrics help [troubleshoot slow Kafka consumption](https://docs.victoriametrics.com/victoriametrics/integrations/kafka/#slow-kafka-consumption). See [#11342](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11342).

* BUGFIX: [alerts](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/rules): fix `AlertingRuleResultsApproachingLimit` and `RecordingRuleResultsApproachingLimit` alerting rules in [vmalert alerting rules](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/rules/alerts-vmalert.yml). The alerts could produce incorrect results or fail to fire when `vmalert_group_rule_

_[Truncated at 4000 characters — full notes: https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.151.0]_