AverageMarcus/cluster.fun
1
0
Fork 0
Code Issues 1 Pull Requests 6 Releases Activity

Update victoriametrics/vmagent Docker tag to v1.140.0 #689

Merged
AverageMarcus merged 1 commits from renovate/victoriametrics into master 2026-04-14 07:26:47 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate commented 2026-04-14 03:17:58 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
victoriametrics/vmagent minor v1.139.0 → v1.140.0

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)

v1.140.0

Compare Source

v1.140.0

Released at 2026-04-10

Update Note 1: vmsingle and vmselect in VictoriaMetrics cluster: CSV export (/api/v1/export/csv) now adds a header row as the first line of the response, so existing CSV-processing scripts may need to skip this header. See #​10666.

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

  • FEATURE: vmagent: add per-URL -remoteWrite.disableMetadata flag to disable metadata sending for specific remote storage URLs. See #​10711. Thanks to @​evkuzin for the contribution.

  • FEATURE: vmagent: add profile option to ec2_sd_configs for loading credentials from named AWS profiles in ~/.aws/credentials and ~/.aws/config, including source_profile chaining and role_arn resolution. See ec2_sd_configs docs. Issue #​1685. Thanks to @​andriibeee for the contribution.

  • FEATURE: introduce vm_filestream_fsync_duration_seconds_total and vm_filestream_fsync_calls_total metrics, which can be used for detecting slow storage if it cannot keep up with the current data ingestion rate. See #​10432. Thanks to @​mehrdadbn9 for the contribution.

  • FEATURE: vmctl: add dedicated thanos mode for migrating data from Thanos. This mode supports both raw and downsampled Thanos blocks, including all aggregate types (count, sum, min, max, counter). Each aggregate is imported as a separate metric with resolution and aggregate type suffixes (e.g., metric_name:5m:count). The new mode uses --thanos-* prefixed flags: --thanos-snapshot, --thanos-concurrency, --thanos-filter-time-start, --thanos-filter-time-end, --thanos-filter-label, --thanos-filter-label-value, and --thanos-aggr-types. See #​9262.

  • FEATURE: dashboards/alert-statistics: add pending and firing alerts stats; fix query in FIRING over time by group panel. See #​10571. Thanks to @​sias32 for the contribution.

  • FEATURE: vmalert: add random jitter to concurrent periodical flushers targeting the remote write destination. This helps spread remote write flushes across the flush interval, avoiding congestion at the remote write destination and enhancing queue data consumption. See #​10729.

  • FEATURE: vmalert: expose vmalert_remotewrite_sent_rows and vmalert_remotewrite_sent_bytes histograms to provide better visibility into remote write request sizes. See #​10727.

  • FEATURE: vmagent: allow setting -1 value for -remoteWrite.maxHourlySeries and -remoteWrite.maxDailySeries command-line flags. This automatically sets limits to the highest possible value in order to enable tracking without enforcing any limits. This is helpful for estimating current usage before applying real limits. See #​9614.

  • FEATURE: vminsert in VictoriaMetrics cluster: optimize vminsert buffer size per vmstorage node based on available CPU, memory and storage node count to reduce OOM risk. See #​10725.

  • FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: allow setting -1 value for -storage.maxHourlySeries and -storage.maxDailySeries command-line flags. This automatically sets limits to the highest possible value in order to enable tracking without enforcing any limits. This is helpful for estimating current usage before applying real limits. See #​9614.

  • FEATURE: vmalert: expose vmalert_remotewrite_queue_size and vmalert_remotewrite_queue_capacity to facilitate monitoring of remote write queue usage. See #​10765.

  • FEATURE: vmui: CSV export on the Raw Query tab now includes all labels from the executed query. VMUI no longer prepends a header row, as it is now provided by the backend. See #​10667 and #​10666. Thanks to @​lawrence3699 for the contribution.

  • FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: add header row to /api/v1/export/csv output and auto-detect header rows during import via /api/v1/import/csv. See #​10666. Thanks to @​andriibeee for the contribution.

  • FEATURE: all VictoriaMetrics components: expose operating system name and release version as metric vm_os_info. See #​10481.

  • FEATURE: vmalert: align group evaluation time with the eval_offset option to help manage group execution more effectively. See #​10772.

  • BUGFIX: vmbackup, vmbackupmanager: retry the requests that failed with unexpected EOF due to unstable network to S3 service. See #​10699.

  • BUGFIX: All VictoriaMetrics components: Fix an issue where unsupported metric metadata type was exposed for summaries and quantiles if a summary wasn't updated within a certain time window. See metrics#120 and metrics#121.

  • BUGFIX: vmagent: fix scrape_series_added metric to update only on successful scrapes, aligning its behavior with Prometheus. See #​10653.

  • BUGFIX: vmselect in VictoriaMetrics cluster: prevent partial responses from second-level vmselect nodes in multi-level cluster setups. Ensures response completeness and correctness, and avoids cache pollution in top-level vmselect. See #​10678.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: Fix storage connection saturation spikes at 00:00 UTC and improve data ingestion when the storage is restarted during the first hour of the day. See 10698.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: prevent rare panic during storage start-up at 100% disk usage. See #​10747 Thanks to @​nmn3m for the contribution.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: prevent data ingestion from getting completely stuck when storage is under heavy load. See #​10784. Thanks to @​fxrlv for the contribution.

Configuration

📅 Schedule: (UTC)

  • 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 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 | Update | Change | |---|---|---| | [victoriametrics/vmagent](https://github.com/VictoriaMetrics/VictoriaMetrics) | minor | `v1.139.0` → `v1.140.0` | --- ### Release Notes <details> <summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)</summary> ### [`v1.140.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.140.0) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.139.0...v1.140.0) ##### [v1.140.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.140.0) Released at 2026-04-10 **Update Note 1:** [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): [CSV export](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#how-to-export-csv-data) (`/api/v1/export/csv`) now adds a header row as the first line of the response, so existing CSV-processing scripts may need to skip this header. See [#&#8203;10666](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10666). - SECURITY: upgrade Go builder from Go1.26.1 to Go1.26.2. See [the list of issues addressed in Go1.26.2](https://github.com/golang/go/issues?q=milestone%3AGo1.26.2%20label%3ACherryPickApproved). - FEATURE: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): add per-URL `-remoteWrite.disableMetadata` flag to disable metadata sending for specific remote storage URLs. See [#&#8203;10711](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10711). Thanks to [@&#8203;evkuzin](https://github.com/evkuzin) for the contribution. - FEATURE: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): add `profile` option to `ec2_sd_configs` for loading credentials from named AWS profiles in `~/.aws/credentials` and `~/.aws/config`, including `source_profile` chaining and `role_arn` resolution. See [ec2\_sd\_configs docs](https://docs.victoriametrics.com/victoriametrics/sd_configs/#ec2_sd_configs). Issue [#&#8203;1685](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1685). Thanks to [@&#8203;andriibeee](https://github.com/andriibeee) for the contribution. - FEATURE: introduce `vm_filestream_fsync_duration_seconds_total` and `vm_filestream_fsync_calls_total` metrics, which can be used for detecting slow storage if it cannot keep up with the current data ingestion rate. See [#&#8203;10432](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10432). Thanks to [@&#8203;mehrdadbn9](https://github.com/mehrdadbn9) for the contribution. - FEATURE: [vmctl](https://docs.victoriametrics.com/victoriametrics/vmctl/): add dedicated `thanos` mode for [migrating data from Thanos](https://docs.victoriametrics.com/victoriametrics/vmctl/thanos/). This mode supports both raw and downsampled Thanos blocks, including all aggregate types (count, sum, min, max, counter). Each aggregate is imported as a separate metric with resolution and aggregate type suffixes (e.g., `metric_name:5m:count`). The new mode uses `--thanos-*` prefixed flags: `--thanos-snapshot`, `--thanos-concurrency`, `--thanos-filter-time-start`, `--thanos-filter-time-end`, `--thanos-filter-label`, `--thanos-filter-label-value`, and `--thanos-aggr-types`. See [#&#8203;9262](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9262). - FEATURE: [dashboards/alert-statistics](https://grafana.com/grafana/dashboards/24553): add pending and firing alerts stats; fix query in `FIRING over time by group` panel. See [#&#8203;10571](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10571). Thanks to [@&#8203;sias32](https://github.com/sias32) for the contribution. - FEATURE: [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/): add random jitter to concurrent periodical flushers targeting the remote write destination. This helps spread remote write flushes across the flush interval, avoiding congestion at the remote write destination and enhancing queue data consumption. See [#&#8203;10729](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10729). - FEATURE: [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/): expose `vmalert_remotewrite_sent_rows` and `vmalert_remotewrite_sent_bytes` histograms to provide better visibility into remote write request sizes. See [#&#8203;10727](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10727). - FEATURE: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): allow setting `-1` value for `-remoteWrite.maxHourlySeries` and `-remoteWrite.maxDailySeries` command-line flags. This automatically sets limits to the highest possible value in order to enable tracking without enforcing any limits. This is helpful for estimating current usage before applying real limits. See [#&#8203;9614](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9614). - FEATURE: `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): optimize vminsert buffer size per vmstorage node based on available CPU, memory and storage node count to reduce OOM risk. See [#&#8203;10725](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10725). - FEATURE: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): allow setting `-1` value for `-storage.maxHourlySeries` and `-storage.maxDailySeries` command-line flags. This automatically sets limits to the highest possible value in order to enable tracking without enforcing any limits. This is helpful for estimating current usage before applying real limits. See [#&#8203;9614](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9614). - FEATURE: [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/): expose `vmalert_remotewrite_queue_size` and `vmalert_remotewrite_queue_capacity` to facilitate monitoring of remote write queue usage. See [#&#8203;10765](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10765). - FEATURE: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): CSV export on the `Raw Query` tab now includes all labels from the executed query. VMUI no longer prepends a header row, as it is now provided by the backend. See [#&#8203;10667](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10667) and [#&#8203;10666](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10666). Thanks to [@&#8203;lawrence3699](https://github.com/lawrence3699) for the contribution. - FEATURE: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): add header row to `/api/v1/export/csv` output and auto-detect header rows during import via `/api/v1/import/csv`. See [#&#8203;10666](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10666). Thanks to [@&#8203;andriibeee](https://github.com/andriibeee) for the contribution. - FEATURE: all VictoriaMetrics components: expose operating system name and release version as metric `vm_os_info`. See [#&#8203;10481](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10481). - FEATURE: [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/): align group evaluation time with the `eval_offset` option to help manage group execution more effectively. See [#&#8203;10772](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10772). - BUGFIX: [vmbackup](https://docs.victoriametrics.com/vmbackup/), [vmbackupmanager](https://docs.victoriametrics.com/victoriametrics/vmbackupmanager/): retry the requests that failed with unexpected EOF due to unstable network to S3 service. See [#&#8203;10699](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10699). - BUGFIX: All VictoriaMetrics components: Fix an issue where `unsupported` metric metadata type was exposed for summaries and quantiles if a summary wasn't updated within a certain time window. See [metrics#120](https://github.com/VictoriaMetrics/metrics/issues/120) and [metrics#121](https://github.com/VictoriaMetrics/metrics/pull/121). - BUGFIX: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): fix `scrape_series_added` metric to update only on successful scrapes, aligning its behavior with Prometheus. See [#&#8203;10653](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10653). - BUGFIX: `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): prevent partial responses from second-level vmselect nodes in [multi-level cluster setups](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#multi-level-cluster-setup). Ensures response completeness and correctness, and avoids cache pollution in top-level vmselect. See [#&#8203;10678](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10678). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): Fix storage connection saturation spikes at 00:00 UTC and improve data ingestion when the storage is restarted during the first hour of the day. See [10698](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10698). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): prevent rare panic during storage start-up at 100% disk usage. See [#&#8203;10747](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10747) Thanks to [@&#8203;nmn3m](https://github.com/nmn3m) for the contribution. - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): prevent data ingestion from getting completely stuck when storage is under heavy load. See [#&#8203;10784](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10784). Thanks to [@&#8203;fxrlv](https://github.com/fxrlv) for the contribution. </details> --- ### Configuration 📅 **Schedule**: (UTC) - 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 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. --- - [ ] <!-- rebase-check -->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-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xMTMuMCIsInVwZGF0ZWRJblZlciI6IjQzLjExMy4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=-->
renovate added 1 commit 2026-04-14 03:17:58 +00:00
Update victoriametrics/vmagent Docker tag to v1.140.0 6a5bffd57f
AverageMarcus merged commit 12d1903e8e into master 2026-04-14 07:26:47 +00:00
AverageMarcus deleted branch renovate/victoriametrics 2026-04-14 07:26:47 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
renovate AverageMarcus
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: AverageMarcus/cluster.fun#689
Delete Branch "renovate/victoriametrics"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?