VictoriaMetrics releases

v1.136.9

Released at 2026-05-08

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

• BUGFIX: vmagent and vmsingle: properly obtain __meta_hetzner_hcloud_location and __meta_hetzner_hcloud_location_network_zone labels for hetzner_sd_configs. Hetzner changed discovery API response and returns location information from different field. See #10909. Thanks to @juliusrickert for contribution.

• BUGFIX: vmauth: now correctly respects disabling retries via -maxRequestBodySizeToRetry=0. Previously, disabling retries required setting both -maxRequestBodySizeToRetry and -requestBufferSize to 0. See #10857. Thanks to @andriibeee for the contribution.

• BUGFIX: vmbackupmanager: explicitly set the MD5 checksum for DeleteObjects requests. Starting with aws-sdk-go-v2/service/s3 v1.73.0, the SDK switched the checksum algorithm from MD5 to CRC32, which can break compatibility with some third-party S3 implementations, including Dell ECS. See #10907.

• BUGFIX: vmauth: attempt to route requests to the first backend when all backends are marked as broken. Previously, vmauth returned an error immediately without attempting any backend. This change may improve success rate in rare edge cases. See #10837.

• BUGFIX: vmsingle: and vmselect in VictoriaMetrics cluster: give priority to extra_label and extra_filters[] params defined in URL query string over those defined in request body form, to properly respect constraints imposed by vmauth. See #10908.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: set CORS headers on /api/v1/export, /api/v1/export/csv and /api/v1/export/native. See #10899. Thanks to @andriibeee for the contribution.

v1.122.22

Released at 2026-05-08

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 Go builder from Go1.26.2 to Go1.26.3. See the list of issues addressed in Go1.26.3.

• BUGFIX: vmagent and vmsingle: properly obtain __meta_hetzner_hcloud_location and __meta_hetzner_hcloud_location_network_zone labels for hetzner_sd_configs. Hetzner changed discovery API response and returns location information from different field. See #10909. Thanks to @juliusrickert for contribution.

• BUGFIX: vmsingle: and vmselect in VictoriaMetrics cluster: give priority to extra_label and extra_filters[] params defined in URL query string over those defined in request body form, to properly respect constraints imposed by vmauth. See #10908.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: set CORS headers on /api/v1/export, /api/v1/export/csv and /api/v1/export/native. See #10899. Thanks to @andriibeee for the contribution.

v1.143.0

Released at 2026-05-08

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

• FEATURE: all VictoriaMetrics components: suppress TCP health check errors when -tls flag is set. See #10538.

• FEATURE: vmagent and vmsingle: add __meta_hetzner_robot_datacenter label for robot role in hetzner_sd_configs. See #10909. Thanks to @juliusrickert for contribution.

• FEATURE: vmalert: add -rule.stripFilePath to support stripping rule file paths in logs and all API responses, including /metrics. See #5625.

• FEATURE: vmalert: add formatTime template function for formatting a Unix timestamp using the provided layout. For example, {{ now | formatTime "2006-01-02T15:04:05Z07:00" }} returns the current time in RFC3339 format. See issue #10624. Thanks to @andriibeee for the contribution.

• FEATURE: vmagent, vmsingle, vminsert in VictoriaMetrics cluster: add support for Prometheus native histogram during ingestion. See #10743.

• FEATURE: vmagent, vmsingle, vmselect in VictoriaMetrics cluster and vmstorage in VictoriaMetrics cluster: introduce the vm_fs_info metric. It exposes the filesystem type (e.g., ext4, xfs, nfs) used for -*Path related flags. See #10482.

• FEATURE: dashboards/vmagent: add Kafka (Enterprise) row with panels for monitoring traffic (bytes), messages in/out, producer and consumer errors. See #10728.

• BUGFIX: vmagent and vmsingle: properly obtain __meta_hetzner_hcloud_location and __meta_hetzner_hcloud_location_network_zone labels for hetzner_sd_configs. Hetzner changed discovery API response and returns location information from different field. See #10909. Thanks to @juliusrickert for contribution.

• BUGFIX: vminsert in VictoriaMetrics cluster: properly discover addresses of storage nodes with enterprise automatic-vmstorage-discovery. Bug was introduced at v1.141.0.

• BUGFIX: vmauth: now correctly respects disabling retries via -maxRequestBodySizeToRetry=0. Previously, disabling retries required setting both -maxRequestBodySizeToRetry and -requestBufferSize to 0. See #10857. Thanks to @andriibeee for the contribution.

• BUGFIX: vmbackupmanager: explicitly set the MD5 checksum for DeleteObjects requests. Starting with aws-sdk-go-v2/service/s3 v1.73.0, the SDK switched the checksum algorithm from MD5 to CRC32, which can break compatibility with some third-party S3 implementations, including Dell ECS. See #10907.

• BUGFIX: vmauth: attempt to route requests to the first backend when all backends are marked as broken. Previously, vmauth returned an error immediately without attempting any backend. This change may improve success rate in rare edge cases. See #10837.

• BUGFIX: vmsingle: and vmselect in VictoriaMetrics cluster: give priority to extra_label and extra_filters[] params defined in URL query string over those defined in request body form, to properly respect constraints imposed by vmauth. See #10908.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: set CORS headers on /api/v1/export, /api/v1/export/csv and /api/v1/export/native. See #10899. Thanks to @andriibeee for the contribution.

v1.136.8

Released at 2026-04-30

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: vminsert in VictoriaMetrics cluster: properly discover addresses of storage nodes with enterprise automatic-vmstorage-discovery. Bug was introduced at v1.141.0.

v1.142.0

Released at 2026-04-28

• BUGFIX: vmagent, vmsingle and vminsert in VictoriaMetrics cluster: properly add OpenTelemetry Unit suffix to the metric name and metadata Help when -opentelemetry.usePrometheusNaming flag is enabled. Previously, if http_requests has Unit: seconds and the next metric cpu_usage has no Unit, cpu_usage would be ingested as cpu_usage_seconds. See #10889.

v1.136.7

Released at 2026-04-28

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: vmagent, vmsingle and vminsert in VictoriaMetrics cluster: properly add OpenTelemetry Unit suffix to the metric name and metadata Help when -opentelemetry.usePrometheusNaming flag is enabled. Previously, if http_requests has Unit: seconds and the next metric cpu_usage has no Unit, cpu_usage would be ingested as cpu_usage_seconds. See #10889.

v1.141.0

Released at 2026-04-24

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

• FEATURE: all VictoriaMetrics components: add support for reading cpu/memory limits configured via systemd slices. Previously, only limits set directly on the process's own cgroup were detected. See #10635. Thanks to @andriibeee for the contribution.

• FEATURE: vmctl: improve error handling at opentsdb migration. See #10797

• FEATURE: vmui: now Run query link on the Alerting Rules page correctly propagates the alert’s interval and evaluation time. See #10366.

• FEATURE: alerts: add new MetricNameStatsCacheUtilizationIsTooHigh alerting rule to track overutilization of Metric names usage stats tracker (used in Cardinality Explorer). See #10840.

• FEATURE: stream aggregation: add vm_streamaggr_counter_resets_total metric for total*, increase* and rate* outputs that is useful for aggregation behaviour tracking. These metrics help to identify issues described in Troubleshooting: counter resets. See #10807.

• FEATURE: vmsingle and vmstorage and vmselect in VictoriaMetrics cluster: add the support of ingestion and retrieval of samples with timestamps in the future. The new -futureRetention flag controls how far in the future the timestamps are allowed to be. See #827 and #10718.

• FEATURE: dashboards/vmagent, dashboards/cluster: add metadata row ingestion rate queries to related panels. See #10868.

• BUGFIX: vminsert in VictoriaMetrics cluster: fix increased memory usage after upgrade to v1.140.0 by properly accounting for internal buffer count when calculating per-storage buffer size. See #10725. Thanks to @fxrlv for the contribution.

• BUGFIX: all VictoriaMetrics components: properly parse IPv6 source address when accepting connections with proxy protocol v2 enabled. See #10839. Thanks to @andriibeee for the contribution.

• BUGFIX: vmagent: properly attach tenant from __tenant_id__ label to the scraped metadata. See #10828.

• BUGFIX: vmagent: keep tenant ingested into vmagent via prometheus remotewrite endpoint. See #10828.

• BUGFIX: vmagent and vmsingle: -maxScrapeSize is now correctly applied when reading response bodies, including non-OK scrape error responses. See #10804.

• BUGFIX: vmagent: fix ec2_sd_configs returning 401 AuthFailure from AWS when credentials are obtained via IRSA, instance role or AWS_CONTAINER_CREDENTIALS_* env vars. The regression was introduced in v1.140.0. See #10815. Thanks to @andriibeee for the contribution.

• BUGFIX: vmauth: fix leak of backend TCP connections, file descriptors and goroutines when the client cancels the request after the backend response has been received. See #10833. Thanks to @andriibeee for the contribution.

• BUGFIX: vmauth: fix a rare panic during config reload when a backend is marked as broken. See #10806.

• BUGFIX: vmselect in VictoriaMetrics cluster: stop logging warnings about failed handshakes when the clusternative port receives TCP healthchecks from load balancers. See #10786. Thanks to @andriibeee for the contribution.

• BUGFIX: vmrestore: fix an issue where vmrestore could hang indefinitely when interrupted during backup download. See #10794.

• BUGFIX: vmsingle: properly execute graceful shutdown for vmsingle if -maxIngestionRate is configured. See #10795.

• BUGFIX: vmui: fix time display on Alerting Rules page to use selected timezone. See #10827.

• BUGFIX: vmui: use contrasting colors when displaying time series to improve visibility on light and dark themes. See #10869.

• BUGFIX: vmalert: delete labels from rule results if they are specified with an empty string value in rule or group labels. See #10766.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: fix incorrect evaluation of binary operations caused by an ordering bug (e.g. 10 - (3 + 3 + 4) being evaluated as 10 - 3 + 3 + 4). The issue was introduced in v1.140.0, v1.136.4, and v1.122.19. See #10856.

v1.122.21

Released at 2026-04-24

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 Go builder from Go1.25.9 to Go1.26.2. See the list of issues addressed in Go1.26.2.

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

• BUGFIX: all VictoriaMetrics components: properly parse IPv6 source address when accepting connections with proxy protocol v2 enabled. See #10839. Thanks to @andriibeee for the contribution.

• BUGFIX: vmagent and vmsingle: -maxScrapeSize is now correctly applied when reading response bodies, including non-OK scrape error responses. See #10804.

• BUGFIX: vminsert in VictoriaMetrics cluster: properly allocate vminsert buffer size per vmstorage node based on available CPU, memory and storage node count to reduce OOM risk. See #10725.

• BUGFIX: vmrestore: fix an issue where vmrestore could hang indefinitely when interrupted during backup download. See #10794.

• BUGFIX: vmsingle: properly execute graceful shutdown for vmsingle if -maxIngestionRate is configured. See #10795.

• BUGFIX: vmalert: delete labels from rule results if they are specified with an empty string value in rule or group labels. See #10766.

• BUGFIX: vmui: use contrasting colors when displaying time series to improve visibility on light and dark themes. See #10869.

v1.136.6

Released at 2026-04-24

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.3 to 3.23.4. See Alpine 3.23.4 release notes.

• BUGFIX: all VictoriaMetrics components: properly parse IPv6 source address when accepting connections with proxy protocol v2 enabled. See #10839. Thanks to @andriibeee for the contribution.

• BUGFIX: vmagent: properly attach tenant from __tenant_id__ label to the scraped metadata. See #10828.

• BUGFIX: vmagent: keep tenant ingested into vmagent via prometheus remotewrite endpoint. See #10828.

• BUGFIX: vmagent and vmsingle: -maxScrapeSize is now correctly applied when reading response bodies, including non-OK scrape error responses. See #10804.

• BUGFIX: vmagent: fix ec2_sd_configs returning 401 AuthFailure from AWS when credentials are obtained via IRSA, instance role or AWS_CONTAINER_CREDENTIALS_* env vars. The regression was introduced in v1.140.0. See #10815. Thanks to @andriibeee for the contribution.

• BUGFIX: vmauth: fix leak of backend TCP connections, file descriptors and goroutines when the client cancels the request after the backend response has been received. See #10833. Thanks to @andriibeee for the contribution.

• BUGFIX: vmauth: fix a rare panic during config reload when a backend is marked as broken. See #10806.

• BUGFIX: vmselect in VictoriaMetrics cluster: stop logging warnings about failed handshakes when the clusternative port receives TCP healthchecks from load balancers. See #10786. Thanks to @andriibeee for the contribution.

• BUGFIX: vmrestore: fix an issue where vmrestore could hang indefinitely when interrupted during backup download. See #10794.

• BUGFIX: vmsingle: properly execute graceful shutdown for vmsingle if -maxIngestionRate is configured. See #10795.

• BUGFIX: vmui: fix time display on Alerting Rules page to use selected timezone. See #10827.

• BUGFIX: vmui: use contrasting colors when displaying time series to improve visibility on light and dark themes. See #10869.

• BUGFIX: vmalert: delete labels from rule results if they are specified with an empty string value in rule or group labels. See #10766.

v1.122.20

Released at 2026-04-23

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 vmselect in VictoriaMetrics cluster: fix incorrect evaluation of binary operations caused by an ordering bug (e.g. 10 - (3 + 3 + 4) being evaluated as 10 - 3 + 3 + 4). The issue was introduced in v1.140.0, v1.136.4, and v1.122.19. See #10856.

v1.136.5

Released at 2026-04-23

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: vmsingle and vmselect in VictoriaMetrics cluster: fix incorrect evaluation of binary operations caused by an ordering bug (e.g. 10 - (3 + 3 + 4) being evaluated as 10 - 3 + 3 + 4). The issue was introduced in v1.140.0, v1.136.4, and v1.122.19. See #10856.

v1.136.2

Released at 2026-03-13

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

• FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: Disable /graphite/tags/tagSeries and /graphite/tags/tagMultiSeries for Graphite tag registration since it is unlikely it is used in context of VictoriaMetrics. See 10544.

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

• BUGFIX: all VictoriaMetrics components: replace histogram with untyped metric metadata type for VictoriaMetrics histograms when -metrics.exposeMetadata is set. See #82.

• BUGFIX: vmauth: properly route requests to default_url. Previously, request_path query arg could be set incorrectly during concurrent requests. See #10626.

• BUGFIX: vmbackup, vmbackupmanager: do not enable ACL when uploading backups to S3-compatible endpoints by default. ACL is not always supported by S3-compatible endpoints and it is not recommended to use ACLs to limit access to objects. See #10539 for more details.

• BUGFIX: vmbackupmanager: overwrite s3 object metadata while syncing latest backups with other backup types. See #10639.

• BUGFIX: vmagent, vmsingle, vminsert and vmstorage in VictoriaMetrics cluster: properly attach host label to the time series ingested via /datadog/api/beta/sketches API. See #10557.

• BUGFIX: vmui: use increase_pure instead of rate for histogram heatmaps in Explore Metrics to correctly display the first observation in each new bucket. See #10365. Thanks to @ab0utbla-k for the contribution.

• BUGFIX: vmstorage in VictoriaMetrics cluster: fix inaccurate vm_filestream_write_duration_seconds_total due to duplicate counting . After the fix, vm_filestream_write_duration_seconds_total will track the duration spent on calling the write(2) system call properly. See #10564.