v1.136.1

v1.136.1

Released at 2026-03-02

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: all VictoriaMetrics components: return gzip-compressed response instead of zstd-compressed response to the client if Accept-Encoding request header contains both gzip and zstd. This is needed because some clients and proxies improperly handle zstd-compressed responses. See #10535.
• BUGFIX: vmagent and vmsingle: properly check expired client certificate during mTLS requests. See #10393.
• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: prevent panic error parsing regexp: expression nests too deeply triggered by large repetition ranges in regex. See VictoriaLogs#1112.
• BUGFIX: vmstorage in VictoriaMetrics cluster: properly search tenants for multitenant query request. See #10422.
• BUGFIX: vmstorage in VictoriaMetrics cluster: properly apply extra_filters[] filter when querying vm_account_id or vm_project_id labels via multitenant request for /api/v1/label/…/values API. Before, extra_filters was ignored.
• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: revert the use of rollup result cache for instant queries that contain rate function with a lookbehind window larger than -search.minWindowForInstantRollupOptimization. The cache usage was removed since v1.132.0. See #10098 for more details.
• BUGFIX: vmui: fix escaping for label names with special characters. See #10485.

v1.122.16

v1.122.16

Released at 2026-02-27

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: vmsingle and vmstorage in VictoriaMetrics cluster: prevent panic error parsing regexp: expression nests too deeply triggered by large repetition ranges in regex, for example {"__name__"=~"a{0,1000}"}. See VictoriaLogs#1112.
• BUGFIX: vmstorage in VictoriaMetrics cluster: properly search tenants for multitenant query request. See #10422.
• BUGFIX: vmstorage in VictoriaMetrics cluster: properly apply extra_filters[] filter when querying vm_account_id or vm_project_id labels via multitenant request for /api/v1/label/…/values API. Before, extra_filters was ignored. See #10503.
• BUGFIX: vmui: fix escaping for label names with special characters. See #10485.

v1.110.31

v1.110.31

Released at 2026-02-27

v1.110.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.110.x line will be supported for at least 12 months since v1.110.0 release

• BUGFIX: vmstorage in VictoriaMetrics cluster: properly search tenants for multitenant query request. See #10422.

v1.137.0

v1.137.0

Released at 2026-02-27

Update Note 1: vmsingle and vmagent: default value of the flag -promscrape.dropOriginalLabels changed from true to false.
It enables back Discovered targets debug UI by default.

• FEATURE: vmbackup: can now copy backups between different storage backends, such as from s3 to local disk or gcs to s3. See #10401. Thanks to @BenNF for the contribution.

• FEATURE: vmauth: add JWT token authentication support with signature verification based on provided public_keys. Read more about configuration in JWT Token auth proxy documentation. See #10445.

• FEATURE: vmauth: support dynamic rewriting of upstream URLs and request headers using placeholders populated from JWT vm_access claim fields. This allows routing requests to the correct tenant backend without maintaining a separate user config entry per tenant. Read more in JWT claim-based request templating documentation. See #10492.

• FEATURE: all VictoriaMetrics components: expose process_cpu_seconds_total, process_resident_memory_bytes, and other process-level metrics when running on macOS. See metrics#75.

• FEATURE: dashboards/vmauth: add Request body buffering duration panel to the Troubleshooting section. This panel shows the time spent buffering incoming client request bodies, helping identify slow client uploads and potential concurrency issues. The panel is only available when -requestBufferSize is non-zero. See #10309.

• FEATURE: vmagent and vmsingle: reduce CPU and memory usage when -promscrape.dropOriginalLabels command-line flag is set. See #9952.

• FEATURE: vmagent, vmsingle, vminsert and vmstorage in VictoriaMetrics cluster: enable ingestion and in-memory storage of metrics metadata by default. Metadata ingestion can be disabled with -enableMetadata=false. See #2974.

• FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: decode UTF-8 label names in the label/<name>/values API according to the Prometheus API specifications. See #10446. Thanks to @utrack for the contribution.

• FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: increase default value for -storage.minFreeDiskSpaceBytes flag from 10M to 100M to reduce risk of panics under high ingestion on small disks. See #9561.

• FEATURE: vmagent and vmsingle: improve InfluxDB ingestion parsing error message when a closing quote is missing for a quoted field value, by adding a hint that this may be caused by a raw newline (\n) inside the quoted field value. See #10067. Thanks to @hklhai for the contribution.

• FEATURE: MetricsQL: add histogram_fraction function to calculate the fraction of buckets falling between lowerLe and upperLe. See #5346.

• FEATURE: dashboards/alert-statistics: add job and instance filters to the VictoriaMetrics - Alert statistics dashboard. This allows users running multiple independent vmalert instances to filter and analyze alerts statistics per specific instance, making it easier to identify issues in a particular vmalert deployment. See #10549.

• FEATURE: dashboards/alert-statistics: add a link to a specific alerting rule on the table of firing alerts. See #10508. Thanks to @sias32 for the contribution.

• FEATURE: alerts: use $externalURL instead of localhost in the alerting rules. This should improve usability of the rules if $externalURL is correctly configured, without need to update rules annotations. See #10508. Thanks to @sias32 for the contribution.

• FEATURE: all VictoriaMetrics components: publish SPDX SBOM attestations for container images on docker.io and quay.io. See SECURITY.md and #10474. Thanks to @smuda for the contribution.

• BUGFIX: all VictoriaMetrics components: return gzip-compressed response instead of zstd-compressed response to the client if Accept-Encoding request header contains both gzip and zstd. This is needed because some clients and proxies improperly handle zstd-compressed responses. See #10535.

• BUGFIX: vmagent and vmsingle: properly check expired client certificate during mTLS requests. See #10393.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: prevent panic error parsing regexp: expression nests too deeply triggered by large repetition ranges in regex, for example {"__name__"=~"a{0,1000}"}. See VictoriaLogs#1112.

• BUGFIX: vmui: fix escaping for label names with special characters. See #10485.

• BUGFIX: vmstorage in VictoriaMetrics cluster: properly search tenants for multitenant query request. See #10422.

• BUGFIX: vmstorage in VictoriaMetrics cluster: properly apply extra_filters[] filter when querying vm_account_id or vm_project_id labels via multitenant request for /api/v1/label/…/values API. Before, extra_filters was ignored. See #10503.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: revert the use of rollup result cache for instant queries that contain rate function with a lookbehind window larger than -search.minWindowForInstantRollupOptimization. The cache usage was removed since v1.132.0. See #10098 for more details.

v1.122.15

v1.122.15

Released at 2026-02-13

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.2 to 3.23.3. See Alpine 3.23.3 release notes.

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

• BUGFIX: all VictoriaMetrics components: respect default http client proxy env variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY). See #10385. Thanks to @zane-deg for the contribution.

• BUGFIX: vmagent and vmsingle: properly expose kubernetes_sd discovery network dialer metrics vm_promscrape_discovery_kubernetes_conn_*. See #10382.

• BUGFIX: VictoriaMetrics enterprise vmagent and vmsingle: introduce time‑based manual offset commit for kafka consumer to fix performance degradation with enabled manual commit. After this change, the consumer will commit partition offsets in batch per second to avoid high commit QPS on the Kafka broker. It's no longer recommended to set enable.auto.commit=true in -kafka.consumer.topic.options, as vmagent will automatically manage it. See #10395.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: fix vm_deduplicated_samples_total{type="select"} to correctly count deduplicated identical samples with the same timestamp and value. See #10400.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: previously the Graphite render API used a fixed process timeout that could expire before long queries completed; now the timeout follows the query deadline, so users can extend it via -search.maxQueryDuration or the timeout argument in the query. See #8484.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: avoid slow-path deduplication for time series with staleness markers. See #10384.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: properly prettify metricsql queries with regex. See metricsql#60. Thanks to @freeseacher for the contribution.

v1.110.30

v1.110.30

Released at 2026-02-13

v1.110.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.110.x line will be supported for at least 12 months since v1.110.0 release

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

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

• BUGFIX: VictoriaMetrics enterprise vmagent and vmsingle: introduce time‑based manual offset commit for kafka consumer to fix performance degradation with enabled manual commit. After this change, the consumer will commit partition offsets in batch per second to avoid high commit QPS on the Kafka broker. It's no longer recommended to set enable.auto.commit=true in -kafka.consumer.topic.options, as vmagent will automatically manage it. See #10395.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: previously the Graphite render API used a fixed process timeout that could expire before long queries completed; now the timeout follows the query deadline, so users can extend it via -search.maxQueryDuration or the timeout argument in the query. See #8484.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: avoid slow-path deduplication for time series with staleness markers. See #10384. Thanks to @fxrlv for the contribution.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: fix vm_deduplicated_samples_total{type="select"} to correctly count deduplicated identical samples with the same timestamp and value. See #10400.
  #10400.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: properly prettify metricsql queries with regex. See metricsql#60. Thanks to @freeseacher for the contribution.

v1.136.0

v1.136.0

Released at 2026-02-13

• SECURITY: upgrade Go builder from Go1.25.6 to Go1.26.0. See Go 1.26 release notes.

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

• FEATURE: dashboards/single, dashboards/cluster, dashboards/vmagent: add clickable source code links to the Logging rate panel in Drilldown. Users can use it to navigate directly to the source code location that generated those logs, making debugging and code exploration easier. See #10406.

• FEATURE: vmui: add Queries with most memory to execute section in Top Queries page of vmui. It can help users to find queries that consume most memory and potentially cause OOM. See #9330.

• FEATURE: vmui: make label value autocomplete context-aware by suggesting values only from series matching already selected label filters. See #9269.

• BUGFIX: all VictoriaMetrics components: respect default http client proxy env variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY). See #10385. Thanks to @zane-deg for the contribution.

• BUGFIX: vmagent and vmsingle: properly expose kubernetes_sd discovery network dialer metrics vm_promscrape_discovery_kubernetes_conn_*. See #10382.

• BUGFIX: vmsingle: slightly reduce memory usage for metrics-metadata ingestion. See #10392.

• BUGFIX: VictoriaMetrics enterprise vmagent and vmsingle: introduce time‑based manual offset commit for kafka consumer to fix performance degradation with enabled manual commit. After this change, the consumer will commit partition offsets in batch per second to avoid high commit QPS on the Kafka broker. It's no longer recommended to set enable.auto.commit=true in -kafka.consumer.topic.options, as vmagent will automatically manage it. See #10395.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: fix vm_deduplicated_samples_total{type="select"} to correctly count deduplicated identical samples with the same timestamp and value. See #10400.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: properly prettify metricsql queries with regex. See metricsql#60. Thanks to @freeseacher for the contribution.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: previously the Graphite render API used a fixed process timeout that could expire before long queries completed; now the timeout follows the query deadline, so users can extend it via -search.maxQueryDuration or the timeout argument in the query. See #8484.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: properly report last partition metrics at the end of current month. See #10387.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: avoid slow-path deduplication for time series with staleness markers. See #10384. Thanks to @fxrlv for the contribution.

• BUGFIX: vmsingle, vminsert in VictoriaMetrics cluster and vmagent: ensure proper reset of buf size for OpenTelemetry ingestion, and allow flushing when buf size exceeds 4MiB. Previously, when a small number of requests carried a large volume of time series or labels, buf was over-expanded and recycled to the pool, resulting in excessive memory usage. See #10378.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: correctly display hierarchy of actions in query trace during index searches. Before, search within the specific index was placed out of scope in the trace. See #10459.

v1.122.14

v1.122.14

Released at 2026-01-30

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: vmauth: stop backend health checks for URL prefixes defined in url_map during configuration reloads. Previously, stale backends kept being health-checked and produced repeated warning logs after reloads. See #10334.
• BUGFIX: vmstorage in VictoriaMetrics cluster: correctly return tenants results for /admin/tenants when start or end are specified. See #10312
• BUGFIX: vmui: fix "Percentage from total" calculation on the Cardinality Explorer page when multiple metrics match the filter. See #10323. Thanks to @PleasingFungus for the contribution.
• BUGFIX: vmagent: apply -promscrape.maxScrapeSize check to decompressed data instead of compressed data. See #9481.
• BUGFIX: vmalert: fix alert restore when a group contains many rules and is slow to complete evaluation. Previously, the restore process might not retrieve the correct previous alert state. See #10335.
• BUGFIX: MetricsQL: fix changes() function when gaps between samples exceed the lookbehind window. Previously, it could yield a non-zero value even when the sample value remained unchanged. See #10280.
• BUGFIX: vmauth: fix an issue where canceling a client request (closing a browser tab or timeout) incorrectly marked all backends as unavailable for -failTimeout duration (3s by default), even though backends were healthy. See #10318.

v1.110.29

v1.110.29

Released at 2026-01-30

v1.110.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.110.x line will be supported for at least 12 months since v1.110.0 release

• BUGFIX: MetricsQL: fix changes() function when gaps between samples exceed the lookbehind window. Previously, it could yield a non-zero value even when the sample value remained unchanged. See #10280.
• BUGFIX: vmalert: fix alert restore when a group contains many rules and is slow to complete evaluation. Previously, the restore process might not retrieve the correct previous alert state. See #10335.
• BUGFIX: vmauth: fix an issue where canceling a client request (closing a browser tab or timeout) incorrectly marked all backends as unavailable for -failTimeout duration (3s by default), even though backends were healthy. See #10318.
• BUGFIX: vmauth: stop backend health checks for URL prefixes defined in url_map during configuration reloads. Previously, stale backends kept being health-checked and produced repeated warning logs after reloads. See #10334.
• BUGFIX: vmstorage in VictoriaMetrics cluster: correctly return tenants results for /admin/tenants when start or end are specified. See #10312
• BUGFIX: vmui: fix "Percentage from total" calculation on the Cardinality Explorer page when multiple metrics match the filter. See #10323. Thanks to @PleasingFungus for the contribution.

v1.135.0

v1.135.0

Released at 2026-01-30

• FEATURE: vmagent and vmsingle: improved scrape size display. Sizes below 1024 bytes are now shown in B, and larger sizes are shown as whole KiB (rounded up). This prevents confusion where values like 123.456 KiB were interpreted as 123456 KiB, while the actual size was only 123 KiB. See #10307.

• FEATURE: vmauth: allow buffering request bodies before proxying them to backends. This reduces load on backends when processing requests from slow clients such as IoT devices connected to vmauth via slow networks. See #10309 and request body buffering docs.

• FEATURE: vmbackupmanager: allow completely disabling scheduled backups by using -disableScheduledBackups command-line flag. This is useful to run vmbackupmanager only for on-demand backups and restores triggered via API. See #10364.

• FEATURE: monitoring: take into account all the generated log messages at vm_log_messages_total metric, including suppressed logs if the -loggerLevel command-line flag is set to values other than INFO. Add is_printed label to the vm_log_messages_total metric in order to understand whether the log at the given code location was suppressed or not. This simplifies troubleshooting of VictoriaMetrics components when logs aren't available. See #10304.

• FEATURE: vmagent: support configuring different -remoteWrite.queues per remoteWrite url. This allows setting -remoteWrite.queues=1 for backends that do not support out-of-order ingestion (e.g. Mimir), while keeping higher queue counts for other backends such as VictoriaMetrics. Previously, this required running multiple vmagent instances with different queue settings. See #10270.

• FEATURE: alerts: add new alerting rules PersistentQueueRunsOutOfSpaceIn12Hours and PersistentQueueRunsOutOfSpaceIn4Hours for vmagent persistent queue capacity. These alerts help users to take proactive actions before vmagent starts dropping metrics due to insufficient persistent queue space. See #10193

• FEATURE: All VictoriaMetrics components: add build version information to the home page for consistency with other projects. See #10249.

• FEATURE: all VictoriaMetrics components: add flag fs.disableMincore, which allows to disable mincore syscall. See #10327.

• FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: expose topN average memory bytes consumption queries in /api/v1/status/top_queries. It can help users to find queries that consume a lot of memory and potentially cause OOM. See #9330.

• FEATURE: vmctl: add metrics for tracking the migration progress. See vmctl - monitoring the migration process and #10276.

• BUGFIX: vmauth: stop backend health checks for URL prefixes defined in url_map during configuration reloads. Previously, stale backends kept being health-checked and produced repeated warning logs after reloads. See #10334.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: properly return /api/v1/status/tsdb response for time range outside partition index. See #10315.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: properly report *_requests_total, *_misses_total, *_resets_total, *_syncs_total, *_rotations_total metrics for indexdb/tagFiltersToMetricIDs, indexdb/metricID and indexdb/date_metricID caches. See #10275.

• BUGFIX: vmstorage in VictoriaMetrics cluster: correctly return tenants results for /admin/tenants when start or end are specified. See #10312. Thanks to @Defined2014 for the contribution.

• BUGFIX: vmui: fix "Percentage from total" calculation on the Cardinality Explorer page when multiple metrics match the filter. See #10323. Thanks to @PleasingFungus for the contribution.

• BUGFIX: vmagent: apply -promscrape.maxScrapeSize check to decompressed data instead of compressed data. See #9481.

• BUGFIX: vmalert: disallow setting the -notifier.url command-line flag to a null value. See #10355.

• BUGFIX: vmalert: fix alert restore when a group contains many rules and is slow to complete evaluation. Previously, the restore process might not retrieve the correct previous alert state. See #10335.

• BUGFIX: vmalert: do not skip sending alert notifications to -notifier.url if remote write requests to -remoteWrite.url fail. See #10376.

• BUGFIX: MetricsQL: fix changes() function when gaps between samples exceed the lookbehind window. Previously, it could yield a non-zero value even when the sample value remained unchanged. See #10280.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: previously ingestion could hit lock contention that triggered frequent context switches and storage connection saturation spikes; now the contention is removed to keep ingestion steady. See #10367.