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

Merged

foosinn merged 1 commit from renovate-victoriametrics-victoria-metrics-1.x into main

2025-12-02 15:22:22 +00:00

renovate commented

2025-12-01 17:01:14 +00:00

Collaborator

This PR contains the following updates:

Package	Type	Update	Change
victoriametrics/victoria-metrics	final	minor	`v1.130.0-scratch` -> `v1.131.0-scratch`

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.

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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [victoriametrics/victoria-metrics](https://github.com/VictoriaMetrics/VictoriaMetrics) | final | minor | `v1.130.0-scratch` -> `v1.131.0-scratch` | --- ### Release Notes <details> <summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/victoria-metrics)</summary> ### [`v1.131.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.131.0) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.130.0...v1.131.0) #### [v1.131.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.131.0) Released at 2025-11-28 - FEATURE: [dashboards/victoriametrics-cluster](https://grafana.com/grafana/dashboards/11176): show "Disk space usage % by type" as stacked graph in Cluster dashboard. See [#9932](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9932). - FEATURE: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/) and [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/): Apply separate log throttlers per OpenTelemetry log type. This should help diagnose delta-temporality issues. See [#9447](https://github.com/VictoriaMetrics/victoriaMetrics/issues/9447) for more details. Thank to [@veleek](https://github.com/veleek) for the contribution. - FEATURE: [vmbackupmanager](https://docs.victoriametrics.com/victoriametrics/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](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html). - FEATURE: `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): reduce query requests latency, CPU and Memory usage for [multi-level](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#multi-level-cluster-setup) select requests. See [#9899](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9899) for details. - FEATURE: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): improve Alerting page styling so rule labels are clearly separated. See [#9856](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9856). - BUGFIX: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/), [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): 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](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9987) for details. - BUGFIX: [vmalert](https://docs.victoriametrics.com/victoriametrics/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](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10027). - BUGFIX [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/), [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): Account for excess white spaces in influx write string. See [#10049](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10049). - BUGFIX: `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): properly use list of discovered storage nodes when using [vmstorage discovery](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#automatic-vmstorage-discovery). Discovery was using an original list of nodes when attempting to establish connection starting from [v1.130.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.130.0). - BUGFIX: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): remove the “step” control from the Raw Query page, since it didn't affect the chart rendering. See [#9667](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9667). - BUGFIX: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): fix display of multiple points at the same timestamp on the Raw Query page. See [#9666](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9666). - BUGFIX: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): fix ability to select multiple metrics in `Explore Metrics` tab. See [#9995](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9995). - BUGFIX: `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): respect `replicationFactor` and `globalReplicationFactor` settings when some of vmstorage nodes are overloaded. See [#10030](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10030) for details. Thanks to [@tIGO](https://github.com/tIGO) for the contribution. - BUGFIX: `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/) and [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/): properly increment `vm_missing_metric_names_for_metric_id_total` metric. </details> --- ### 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 has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

renovate added 1 commit

2025-12-01 17:01:14 +00:00