VictoriaMetrics Long-Term Support (LTS): H2 2025 Update

As we’re into the second half of the year, we’d like to take this opportunity to provide an update on the most recent changes in our Long-Term Support (LTS) releases.

LTS releases are published for the Enterprise versions of VictoriaMetrics and are designed for production workloads under SLA, providing long-term support lines of releases for VictoriaMetrics customers.

Every LTS line receives bug fixes and security fixes for 12 months after the initial release. New LTS lines are published every 6 months, meaning the latest two LTS lines are supported at any given moment. This gives up to 6 months for the migration to new LTS lines for VictoriaMetrics Enterprise users.

While the latest LTS versions are an enterprise-license feature, VictoriaMetrics Enterprise is based on open source, meaning version 1.122.0 is open source and everyone can update to it.

All the bugfixes and security fixes, which are included in LTS releases, are available in the latest open source release. Please upgrade VictoriaMetrics products regularly to the latest available open source release.

We’ve recently released VictoriaMetrics LTS v1.122.1, which begins a new line of Long-Term Support releases. This version will receive bugfixes and security patches for 12 months, ensuring maximum stability for production environments.

The previous LTS release, v1.111, will continue to receive bug fixes until February 2026.

The v1.102 LTS line has reached its end-of-life and is no longer supported. We strongly recommend upgrading to v1.122.1 to continue receiving critical updates.

https://docs.victoriametrics.com/victoriametrics/lts-releases/

The -snapshotsMaxAge flag default has 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 GitHub issue #9344 for details

Full changelog for v1.122.0

The -retryMaxTime flag has been deprecated. Please use -retryMaxInterval flag instead.
See GitHub issue #9169 for more details

Full changelog for v1.121.0

You need to use specific version tags for docker images to continue receiving updates.
See GitHub issue #7336 for more details

Full changelog for v1.117.1

Calls to /api/v1/status/tsdb may temporarily fail until vmstorage and vmselect are updated to the same version.

Full changelog for v1.116.0

vmagent’s data distribution algorithm of remote write is changed from round-robin to consistent hashing when -remoteWrite.shardByURL is enabled. This means vmagents with -remoteWrite.shardByURL will re-shard series after the upgrade, which may result in temporary higher churn rate and memory usage on remote destinations.
See GitHub issue #8546 for more details

Full changelog for v1.116.0

Metric vm_mmaped_files was renamed to vm_mmapped_files to fix the typo in word mmapped.

Full changelog for v1.114.0

VictoriaMetrics Single-node and vmagent include a fix which enforces IPv6 addresses escaping for containers discovered with Kubernetes service discovery and role: pods which do not have exposed ports defined. This means that addresses for these containers will always be wrapped in square brackets. This might affect some relabeling rules which were relying on previous behaviour.

Full changelog for v1.113.0

vmalert disallows using time-buckets stats pipe in alerting or recording rules with VictoriaLogs as datasource. Time buckets used with stats query API may produce unexpected results for users and result in cardinality issues.

Full changelog for v1.113.0

vmalert disallows specifying eval_offset and eval_delay options in the same group. The eval_offset option ensures the group is evaluated at the exact offset in the range of [0…interval]. However, with eval_delay, this behavior cannot be guaranteed without further adjusting the evaluation time, which could lead to more confusion.

This metric records time spent on search operations in the index. It was introduced in v1.56.0. However, this metric was used neither in dashboards nor in alerting rules. It also has high cardinality because index search operations latency can differ by 3 orders of magnitude. Hence, dropping it as unused.

Full changelog for v1.111.0

-eula command-line flag is skipped when validating the 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

Full changelog for v1.122.0

https://docs.victoriametrics.com/victoriametrics/changelog/

Security patches are only guaranteed in LTS lines (Enterprise) or in the latest open source release.

If you’re using the open source version, be advised to regularly upgrade VictoriaMetrics products to their latest available releases.

To learn more about LTS releases for the Enterprise versions of VictoriaMetrics, get in touch.

If you have any questions or need assistance, feel free to reach out to our team in our public Slack channel.