feat(container): update image victoriametrics/victoria-metrics to v1.131.0

[trap-renovate]

This PR contains the following updates:

Package	Update	Change
victoriametrics/victoria-metrics	minor	v1.129.1 -> v1.131.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/victoria-metrics)

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.

v1.130.0

Compare Source

v1.130.0

Released at 2025-11-14

Update Note 1: VictoriaMetrics enterprise vmsingle and vmstorage in VictoriaMetrics cluster: Make sure that, if -retentionFilter is used, its duration is lower than -retentionPeriod before upgrading; otherwise, the deployment will fail. Read more in retention filters documentation.

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

• FEATURE: vmagent: add ability to set attach_metadata.namespace=true option for all the kubernetes_sd_configs defined at -promscrape.config, or via -promscrape.kubernetes.attachNamespaceMetadataAll command-line flag. This allows attaching namespace labels and annotations to discovered targets for pod, service, endpoints, endpointslice, and ingress roles. See #​9880 for more details. Thank you, @​clementnuss, for the contribution.

• FEATURE: vmalert: print the error message as value if templating fails in alerting rule label or annotation values, and continue generating alerts. Previously, a templating error prevented alerts. See #​9853.

• FEATURE: vminsert in VictoriaMetrics cluster and vmsingle: add -enableMetadata command-line flag to enable metrics metadata ingestion. See #​2974 and the following doc.

• FEATURE: vmstorage in VictoriaMetrics cluster and vmsingle: add in-memory storage for storing and querying metrics metadata. See #​2974 and the following doc.

• FEATURE: vmui: add option to always show all points on the chart. See #​9699.

• FEATURE: vmui: improve overall chart rendering performance. See #​9699.

• FEATURE: vmui relabeling playground: relax the validation for the labels text area. It now accepts labels without curly braces (e.g. __name__=metric_name, label1=value1). The regression was introduced in #​8770. See #​9900 for details.

• FEATURE: all VictoriaMetrics components: Attach additional information to logs when throttling occurs. For example, vmagent throttles OpenTelemetry row parse error to one message every 5 seconds. See #​9498. Thanks to @​SamarthBagga for the PR 9752.

• BUGFIX: vmagent and vmsingle: prevent early exit when one of multiple service discovery configs (under the same service discovery type) fails. see this issue #​9949 for details.

• BUGFIX: vmagent and vmsingle: properly access service discovery servers with HTTP/2 protocol enabled. See this issue #​9981 for details. Thanks to the @​JayiceZ

• BUGFIX: vmalert: fix a potential race condition in the /api/v1/rule, /api/v1/alert and /api/v1/alerts APIs during rule hot reload. See this issue #​9551 for details.

• BUGFIX: vmalert: drop labels with empty values in generated alerts and time series. See #​9984.

• BUGFIX: vminsert, vmagent and vmsingle: properly apply maxDataSize memory limits to the zstd encoded requests. It protects ingest endpoints from malicious requests. See commit 10f7cd2f.

• BUGFIX: all VictoriaMetrics components: prevent from misleading log messages containing init new cache substring when opening various cache files at startup. See 9750.

• BUGFIX: vmui: fix display of isolated points on the chart. See #​9666.

• BUGFIX: vmui: fix median value calculation displayed below series graph. See #​9926.

• BUGFIX: VictoriaMetrics enterprise vmsingle and vmstorage in VictoriaMetrics cluster: disallow having a duration in -retentionFilter bigger than -retentionPeriod. Previously, it was allowed but had no effect, the data retention period remains limited to -retentionPeriod. See commit 9a8463df.

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Renovate Bot.

[github-actions]

Diff

@@ spec.template.spec.containers.victoria-metrics.image @@
# apps/v1/StatefulSet/monitor/victoria-metrics
! ± value change
- victoriametrics/victoria-metrics:v1.129.1
+ victoriametrics/victoria-metrics:v1.131.0

@@ spec.template.spec.containers.victoria-metrics.image @@
# apps/v1/StatefulSet/monitor/victoria-metrics
! ± value change
- victoriametrics/victoria-metrics:v1.129.1
+ victoriametrics/victoria-metrics:v1.131.0