VictoriaMetrics Files

v1.124.0

Released at 2025-08-15

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

• FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: protect graphite /render API endpoint with new flag -search.maxGraphitePathExpressionLen. See this PR #9534 for details.

• FEATURE: expose vm_total_disk_space_bytes metric at the /metrics page, which shows the total disk space for the data directory specified via -storageDataPath. This metric can be useful for building alerts and graphs for the percentatge of free disk space via vm_free_disk_space_bytes / vm_total_disk_space_bytes. See this comment.
• FEATURE: all: leave non-existing environment variables as is in config files instead of failure. For example, if the file referred by -promscrape.config contains %{NON_EXISTING_ENV_VAR} placeholder, then it is left as is instead of failing to load the file. This simplifies the usage of environment variables in config files and in command-line flags according to these docs. Users can easily notice non-existing env vars in config files and in command-line flags by looking at their values - they will literally contain %{NON_EXISTING_ENV_VAR} strings.
• FEATURE: vmselect, vminsert and vmstorage in VictoriaMetrics cluster: add rpc handshake timeout configuration via -rpc.handshakeTimeout flag (default 5s). Set deadline for the entire handshake process instead of per-operation timeout. See #9345 for more details.

• FEATURE: vmagent: add -enableMetadata command-line flag to allow sending metadata to the configured -remoteWrite.url, metadata can be scraped from targets, received via VictoriaMetrics remote write, Prometheus remote write v1 or OpenTelemetry protocol. See #2974.

• 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: dashboards/vmagent: fix samples rate panel not showing data in case vmagent is not scraping metrics. Previously, the panel would not display "samples in" results if vmagent only accepts metrics via push protocols.
• 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: dashboards/victoriametrics-cluster: fix panels showing 99th percentile of series or samples read per query or per series. Before, panels were showing the summarized value across all vmselect instances, which didn't make much sense. Now, panels show the max value across the vmselect instances, making it easier to understand complexity of the heaviest queries served.
• 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.