VictoriaMetrics Files

v1.122.2

Released at 2025-08-15

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

• BUGFIX: vmagent: treat single remoteWrite.disableOnDiskQueue flag the same way as if it is explicitly specified for each remote write url. See #9565 for details.

• BUGFIX: vmalert-tool: print a proper error message when templating function fails during execution. Previously, vmalert-tool could throw a misleading panic message instead.
• BUGFIX: vmauth: properly read proxy-protocol header. See this PR #9546 for details.
• BUGFIX: vmselect in VictoriaMetrics cluster: prevent resource leak on partial responses for /federate API requests. This this PR 9536 for details. Thanks to the @fxrlv.
• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: prevent performance degradation on hitting daily or hourly series cardinality limits. See this issue 9554 for details.
• BUGFIX: MetricsQL: gracefully handle histogram_quantile calculation for histograms where buckets are created on demand. This change isn't needed for users who use native instrumentation SDKs for metrics from VictoriaMetrics, Prometheus or OpenTelemetry.
• BUGFIX: MetricsQL: return a proper error message when the function argument is expected to be a string or scalar.
• BUGFIX: vmalert: fix potential data race and missing firing states when replaying alerting rule with -replay.ruleEvaluationConcurrency>1.
• BUGFIX: vmalert: fix the {{ $activeAt }} variable value in annotation templating when the alert has already triggered. See this issue #9543 for details.
• BUGFIX: vmbackup, vmbackupmanager: allow enabling checksum calculation for PUT requests by using -s3ChecksumAlgorithm command-line flag. This is required for S3 configurations with WORM being enabled. See #9532.