v1.122.1

Released at 2025-08-01

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: do not configure -httpListenAddr.useProxyProtocol for -httpInternalListenAddr. See this issue #9515 for details.
• BUGFIX: vmui: always display the tenant selector if the list of tenants is not empty. See #9396.

v1.110.15

Released at 2025-08-01

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: vmui: always display the tenant selector if the list of tenants is not empty. See #9396.

v1.123.0

Released at 2025-08-01

• FEATURE: vmsingle and vmagent: add ipv6 address as a metadata label to gce_sd_configs. See #9370 PR. Thanks to the @dstevensson.

• FEATURE: all the VictoriaMetrics components: support NetBSD builds. See this #9473 PR for details. Thanks to the @iamleot.

• FEATURE: vmselect in VictoriaMetrics cluster: disable retries for requests to vmstorage when handshake or dial errors occur. Retries in such cases are ineffective and can amplify the problem. See #9345 and #9484 for details.

• FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: introduce -storage.idbPrefillStart flag (default: 1h) to control how early next indexdb prefill starts before rotation. Increasing the value may reduce CPU spikes during rotation. See #9393-comment for details.

• FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: Add support for dynamically enabling new series logging via the /internal/log_new_series API and corresponding authFlag -logNewSeriesAuthKey. The logging is enabled for one minute and is automatically disabled afterward. This is a more convenient alternative to the -logNewSeries flag. See 8879 for details. Thanks to the @leiwingqueen

• FEATURE: vmagent and vmsingle: improve Kubernetes service discovery performance with large amount of configured role selectors. See this #9354 issue for details. Thanks to the @fxrlv

• FEATURE: vmctl: add an option to change path for temporary files storage when migrating from Prometheus snapshots. See #9505 for the details.

• FEATURE: vmagent and vmsingle: improve Kubernetes service discovery performance with large amount of configured role selectors. See this #9354 issue for details. Thanks to the @fxrlv

• BUGFIX: vmauth: do not configure -httpListenAddr.useProxyProtocol for -httpInternalListenAddr. See this issue #9515 for details.

• BUGFIX: vmui: always display the tenant selector if the list of tenants is not empty. See #9396.

v1.110.14

Released at 2025-07-18

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

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

• BUGFIX: all VictoriaMetrics components: fix process_cpu_cores_available metric to respect both logical CPU cores and cgroup CPU quota. Previously, it could report incorrect values in containerized environments with no cgroup limits. See #9449.

v1.102.26

Released at 2025-07-18

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

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

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

• BUGFIX: all VictoriaMetrics components: fix process_cpu_cores_available metric to respect both logical CPU cores and cgroup CPU quota. Previously, it could report incorrect values in containerized environments with no cgroup limits. See #9449.

v1.122.0

Released at 2025-07-18

Update Note 1: vmsingle and vmstorage in VictoriaMetrics cluster: The -snapshotsMaxAge flag default have been changed to 3d. This enables automatic deletion of snapshots older than 3 days. If you want to keep the previous behavior (never automatically deleting snapshots), please set -snapshotsMaxAge=0. See #9344 for the details.

Update Note 2: all the VictoriaMetrics Enterprise components: -eula command-line flag is skipped when validating VictoriaMetrics enterprise license. Instead, the -license or -licenseFile command-line flags must be used to provide a valid license key. See these docs for configuration examples.

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

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

• FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: enable automatic deletion of snapshots older than 3 days by default. This helps to avoid wasting disk space due to snapshots not being removed in case of backup failure. See #9344.

• FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: enable metric names stats tracker by default.

• FEATURE: MetricsQL: revert change on respecting staleness markers when calculating rate and increase functions described in #8891-comment. This change was introduced in v1.120.0.

• FEATURE: vmselect in VictoriaMetrics cluster: Increase idle timeout from 30s to 2m and ensure at least two connections remain open between vmselect and vmstorage. The change smooths out connection usage during traffic spikes. See #9464.

• FEATURE: dashboards/alert-statistics: add a new dashboard for displaying historical changes in state of alerts generated by vmalert. The new dashboard should help to identify flappy and noisy alerts, or alerts that never fired before.

• FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: reduce CPU usage caused by garbage collection during indexDB lookups on cache misses. See #9324 for details.

• BUGFIX: all VictoriaMetrics components: properly set process_cpu_cores_available metric to respect both logical CPU cores and cgroup CPU quota. Previously, it could report incorrect values in containerized environments with no cgroup limits. See #9449. Thanks to the @fxrlv.

• BUGFIX: vmagent and vmsingle: properly release memory for /target_response API requests. Previously it could used after return and it may lead to data races and potential data loss during scraping. See #9466. Thanks to the @fxrlv.

• BUGFIX: vmagent: Prevent panic when re-packing a corrupted block during protocol downgrade. See #9417.

• BUGFIX: vmselect in VictoriaMetrics cluster: fix handling of /api/v1/notifiers and /api/v1/metadata endpoints; previously, requests to these endpoints returned 400 Bad Request. vmsingle was not affected.

v1.110.13

Released at 2025-07-04

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: vmbackup, vmbackupmanager: automatically retry requests failing with Expired Token errors. This helps to avoid failed backups when using EKS Pod Identity for authentication. See #9280.
• BUGFIX: vmui: fix errors in console about loading of manifest.json when accessing UI through vmauth with Basic Auth enabled.
• BUGFIX: vmalert: fix alerts state restoration for alerting rules that are using templating in the labels. See #9305.
• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: properly return results for search requests with .+|^$ regex filter expression. See 9290 issue for details.

v1.102.25

Released at 2025-07-04

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

• BUGFIX: vmbackup, vmbackupmanager: automatically retry requests failing with Expired Token errors. This helps to avoid failed backups when using EKS Pod Identity for authentication. See #9280.
• BUGFIX: vmalert: fix alerts state restoration for alerting rules that are using templating in the labels. See #9305.
• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: properly return results for search requests with .+|^$ regex filter expression. See 9290 issue for details.

v1.121.0

Released at 2025-07-04

Update Note 1: The -retryMaxTime flag has been deprecated. Please use -retryMaxInterval flag instead. For more details, see #9169.

• FEATURE: all the VictoriaMetrics Enterprise components: improve error message when an empty license is provided via the -license or -licenseFile command-line flags. See #9337 for the details.

• FEATURE: vmagent: add concurrency option to kafka remoteWrite producer. See 9249 issue for details.

• FEATURE: vmagent and Single-node VictoriaMetrics: support label_limit scrape parameter. It sets labels limit for each scraped sample from a target. If limit is exceeded, the scrape will be rejected and target marked with corresponding scrape error. The label_limit can be defined on global level, per job or during relabeling via __label_limit__ label. See scrape configs doc for details. See #7660 and #3233 issues.

• FEATURE: vmagent: introduce a new flag -retryMaxInterval as a replacement for the deprecated -retryMaxTime flag. The new flag more accurately reflects the behavior it controls. See #9169 for more details. Thanks to the @leiwingqueen.

• FEATURE: vmalert: add /api/v1/notifiers API endpoint for returning list of configured or discovered notifiers.

• FEATURE: vmalert: add datasource_type query argument for /api/v1/rules and /api/v1/alerts endpoints to filter response by rule's datasource type. See #8537.

• FEATURE: vmalert: respect group order defined in the rule file during replay mode to allow chained group if needed. See #9334.

• FEATURE: vmalert: add -replay.ruleEvaluationConcurrency to allow concurrent /query_range requests for a single rule. Increasing this value when replaying for a long time and a single request range is limited by -replay.maxDatapointsPerQuery. See this #7387 for details. Thanks to the @BenNF.

• FEATURE: vmbackupmanager: improve error messages when vmbackupmanager fails to create snapshot. See #9340 for the details.

• FEATURE: vmbackupmanager: support client-side TLS configuration for creating and deleting snapshots via -snapshot.tls* cmd-line flags.

• FEATURE: vmsingle and vmagent: remove duplicate kubernetes targets from service-discovery-debug page. See 8626 issue for details.

• FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: add command-line flag -search.logSlowQueryStatsHeaders for query execution stats. The new flag allows specifying the list of headers to log together with slow queries if user's request contains them. This flag is available only in VictoriaMetrics enterprise. See Query Stats for details.

• FEATURE: vmsingle and vmselect: add ability to proxy /api/v1/notifiers to vmalert when -vmalert.proxyURL is set. See 9267 PR for details.

• FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: add vm_cache_eviction_bytes_total counter metrics to reflect cache evictions due to expiration, misses and cache size. See 9293 PR for details. Thanks to the @BenNF

• FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: enhance MustReadAt panic message to include filename for easier debugging of out-of-range reads. See #9106.

• BUGFIX: dashboards/vmagent and dashboards/vmalert: fix ad-hoc filters auto-complete and filtering on panels that use MetricsQL specific expressions. See #8657.

• BUGFIX: MetricsQL: fix negative increase result when -search.maxLookback or -search.maxStalenessInterval are set and data contains gap. See #8935 (comment).

• BUGFIX: stream aggregation: properly clean quantiles output state during flush. See #9350.

• BUGFIX: vmalert: fix exposition of duplicated metrics for dynamically discovered notifiers via Consul and DNS. See #9260.

• BUGFIX: vmalert: remove inline styles from UI to align with --http.header.csp=default-src 'self' setting. See #9236.

• BUGFIX: vmalert: fix alerts state restoration for alerting rules that are using templating in the labels. See #9305.

• BUGFIX: vmbackup, vmbackupmanager: automatically retry requests failing with Expired Token errors. This helps to avoid failed backups when using EKS Pod Identity for authentication. See #9280.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: properly return results for search requests with .+|^$ regex filter expression. See 9290 issue for details.

• BUGFIX: vmui: fix errors in console about loading of manifest.json when accessing UI through vmauth with Basic Auth enabled.

• BUGFIX: vmui: disabled opening of autocomplete popup on initial page load.

v1.110.12

Released at 2025-06-20

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

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

• BUGFIX: vmsingle, vminsert in VictoriaMetrics cluster and vmagent: fixed duplication in Datadog sketches aggregation metrics. See #8836 for details.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: fix incorrect sorting of tag filters, which led to suboptimal tag filter evaluation order and potentially degraded query performance in rare cases. See #9127 for details.

• BUGFIX: vmselect in VictoriaMetrics cluster: expose /-/healthy and /-/ready endpoints as Prometheus does on vmselect endpoints, thus achieving full Prometheus compatibility for external dependencies.

• BUGFIX: vmbackup, vmbackupmanager: fix server-side copying of objects for Azure Blob Storage when using managed identity for authentication. Previously, it wasn't possible to use smart backups strategy for vmbackup as server-side copy would fail. See #9131.

• BUGFIX: vmbackupmanager: increase startup healthcheck delay for storage reachability from 30 seconds to 3 minutes. This is required to avoid vmbackupmanager restarts when storage node startup take more than 30 seconds (e.g. when storage nodes stores more than 5Tb of data).