chore(deps): update victoriametrics/victoria-metrics docker tag to v1.133.0

[renovate]

This PR contains the following updates:

Package	Update	Change
victoriametrics/victoria-metrics	minor	v1.130.0 → v1.133.0

---

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/victoria-metrics)

v1.133.0

Compare Source

v1.133.0

Released at 2026-01-02

Update Note 1: vmsingle and vmstorage in VictoriaMetrics cluster: Upgrading to per-partition index requires registering all active time series. Expect slow down of data ingestion and queries during upgrade roll-out. This is a one-time operation. Additionally, for users with retention periods shorter than 1 month the disk usage may increase.

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

• FEATURE: vmagent and vmsingle: add support for global sampleLimit setting. This allows users to efficiently limit the number of samples accepted per scrape target. This also ensures target-level sample_limit can correctly override the global setting. See #​10145. Thanks to @​kobylyanskiy for the contribution.

• FEATURE: vmauth: expose vmauth_user_request_backend_requests_total and vmauth_unauthorized_user_request_backend_requests_total metrics, which track the number of requests sent to backends. These counts may exceed vmauth_user_requests_total and vmauth_unauthorized_user_requests_total when requests are retried across multiple backends. See #​10171.

• FEATURE: vmauth: expose vmauth_user_request_errors_total and vmauth_unauthorized_user_request_errors_total metrics, which track the number of user request errors. See #​10188.

• FEATURE: vmauth: add -maxQueueDuration command-line flag for waiting until the incoming request could be executed if -maxConcurrentRequests are already exceeded. This should help with graceful handling of a short spike in the number of concurrent requests without leading to a retry storm. See #​10078.

• FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: introduce per-partition index. This should reduce disk space occupied by indexDBs as they get deleted along with the corresponding partitions once those partitions become outside the retention window. Read more about the motivation behind this feature at #​7599 and what to expect at #​8134.

• BUGFIX: vmagent and vmsingle: properly add exported_ prefix to scraped metrics that have the same names as auto-generated metrics. Previously, some auto-generated metrics were not recognized, so scraped metrics with the same names could overwrite them. See #​10197. Thanks to @​fxrlv for the contribution.

• BUGFIX: vmagent: fix vmagent_rows_inserted_total{type="newrelic"} metric to correctly count samples. See #​10191. Thanks to @​fxrlv for the contribution.

• BUGFIX: vmauth: fix vmauth_user_request_backend_errors_total and vmauth_unauthorized_user_request_backend_errors_total to only reflect backend request errors. Previously, these counters could be overcounted with user request error. See #​10177.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: rotate dateMetricIDCache instead of resetting it. This should make the eviction less aggressive. Since the cache does not have fixed max size anymore the -storage.cacheSizeIndexDBDateMetricID flag has been removed. See #​10064 and PR #​10169.

• BUGFIX: vmsingle: properly add metrics metadata scraped with promscrape.config and selfScrapeInterval. See #​10175.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: fix stats collection for indexdb/tagFiltersToMetricIDs, indexdb/metricID, and indexdb/date_metricID caches. As per PR #​10131, the stats is collected for most utilized instance only, but if the size of all instances is 0 then the stats won't be collected at all. This may result in max cache size alternating between the actual value and 0. See #​10204 and #​10230.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: properly proxy requests to vmalert when -vmalert.proxyURL flag is set. See #​10178.

v1.132.0

Compare Source

v1.132.0

Released at 2025-12-12

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

• FEATURE: dashboards/operator: add panels for flags and configuration parameters values. See #​1341-operator.

• FEATURE: dashboards/single, dashboards/cluster: add Memory usage breakdown panels to Drilldown section. These panels help analyze overall memory distribution and diagnose anomalies or leaks. See #​10139.

• FEATURE: dashboards/single, dashboards/cluster: add Major page faults rate panels to Troubleshooting and Drilldown sections. See #​9974

• FEATURE: Influx line protocol data ingestion: reduce CPU and memory usage when parsing Influx lines with escaped chars - ,, \\, = and . See #​10053.

• FEATURE: OpenTelemetry data ingestion: reduce CPU usage when parsing metrics received via OpenTelemetry protocol. See 293d809.

• FEATURE: vmagent: add a warning to active targets panel when -dropOriginalLabels=true is set (default), indicating that some debug information may not be available. See #​9901.

• FEATURE: vmbackup, vmrestore, vmbackupmanager: add support for SSE KMS Key ID and ACL for use with S3-compatible storages. See #​9796. Thanks to @​sylr for the contribution.

• FEATURE: vminsert in VictoriaMetrics cluster: improve slowness-based rerouting logic. Now rerouting occurs only for the slowest storage node, and only if the cluster as a whole has enough available capacity to handle the additional load. This prevents unnecessary rerouting when the entire cluster is under heavy load or avoid "rerouting storm". The logic is disabled by default; to enable set -disableRerouting=false. See #​9890 for details.

• FEATURE: vmsingle, vmagent: add support of Zabbix Connector ingestion format. See #​6087. Thanks to @​SinotQ for the contribution.

• FEATURE: vmui: improve legend auto-collapse with a higher threshold, a warning message, and a toggle option. See #​10075.

• BUGFIX: all VictoriaMetrics components: properly validate remaining system memory limit. Previously it could have negative values. See #​10083.

• BUGFIX: vmalert: don't increase vmalert_alerting_rules_errors_total/vmalert_recording_rules_errors_total for request context cancellation, which may occur during graceful shutdown or group configuration update. See #​10128. Thanks to @​tIGO for the contribution.

• BUGFIX: vmauth: verify backend network reachability with a TCP dial before marking it healthy. Previously, backends were auto-restored after -failTimeout even if the network was still unreachable, causing requests to hang repeatedly. vmauth now performs a 1s TCP dial check before returning a backend to the healthy pool. See #​9997.

• BUGFIX: vmctl: properly handle process termination during prompt confirmation. Previously, termination signal was ignored and process was still waiting for user input. See #​10104.

• BUGFIX: vmgateway: properly recover from proxy requests errors. Previously, vmgateway may return empty response.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: report stats only for most utilized instances of indexdb/tagFiltersToMetricIDs and indexdb/date_metricID caches. This makes it clear when a cache is full and an action needs to be taken (such as adding more memory or adjusting cache limits). See #​10131.

• BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: disable rollup result cache for instant queries that contain rate function with a lookbehind window larger than -search.minWindowForInstantRollupOptimization. Previously, utilizing the cache might yield incorrect results when time series samples are not continuous. See #​10098.

• BUGFIX: vmstorage in VictoriaMetrics cluster: do not wait after closing the last connections from vminsert when shutting down. The bug was introduced in #​9487. See #​10136.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: dateMetricIDCache metrics were renamed to follow the naming pattern used for other caches. vm_date_metric_id_cache_resets_total becomes vm_cache_resets_total{type="indexdb/date_metricID"} and vm_date_metric_id_cache_syncs_total became vm_cache_syncs_total{type="indexdb/date_metricID"}. See #​10152.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: fix performance degradation caused by redundant indexdb lookups at the start of each hour. See #​10114. Thanks to @​fxrlv for the contribution.

• BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: fix potential datapoint lost in response when query at the last millisecond of the day. See #​9804.

v1.131.0

Compare Source

v1.131.0

Released at 2025-11-28

• FEATURE: dashboards/victoriametrics-cluster: show "Disk space usage % by type" as stacked graph in Cluster dashboard. See #​9932.

• FEATURE: vmagent and vmsingle: Apply separate log throttlers per OpenTelemetry log type. This should help diagnose delta-temporality issues. See #​9447 for more details. Thank to @​veleek for the contribution.

• FEATURE: vmbackupmanager: add -backupTypeTagName flag that sets tag to each backup object with a name equal to flag value and value, that equals to backup type (hourly, daily, monthly, latest, weekly). Useful for AWS S3 lifecycle policy management.

• FEATURE: vmselect in VictoriaMetrics cluster: reduce query requests latency, CPU and Memory usage for multi-level select requests. See #​9899 for details.

• FEATURE: vmui: improve Alerting page styling so rule labels are clearly separated. See #​9856.

• BUGFIX: vmagent, vmsingle and vminsert in VictoriaMetrics cluster: Prevent accept() from blocking when a client connects to -opentsdbListenAddr but sends no data or sends it too slowly. Previously, such connections could stall acceptance of new clients. See #​9987 for details.

• BUGFIX: vmalert: don't increase vmalert_alerts_send_errors_total for request context cancellation, which may occur during graceful shutdown or group configuration update. See #​10027.

• BUGFIX vmagent, vmsingle and vminsert in VictoriaMetrics cluster: Account for excess white spaces in influx write string. See #​10049.

• BUGFIX: vminsert in VictoriaMetrics cluster: properly use list of discovered storage nodes when using vmstorage discovery. Discovery was using an original list of nodes when attempting to establish connection starting from v1.130.0.

• BUGFIX: vmui: remove the “step” control from the Raw Query page, since it didn't affect the chart rendering. See #​9667.

• BUGFIX: vmui: fix display of multiple points at the same timestamp on the Raw Query page. See #​9666.

• BUGFIX: vmui: fix ability to select multiple metrics in Explore Metrics tab. See #​9995.

• BUGFIX: vmselect in VictoriaMetrics cluster: respect replicationFactor and globalReplicationFactor settings when some of vmstorage nodes are overloaded. See #​10030 for details. Thanks to @​tIGO for the contribution.

• BUGFIX: vmstorage in VictoriaMetrics cluster and vmsingle: properly increment vm_missing_metric_names_for_metric_id_total metric.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.