SeanOMik/k3s-cluster
1
0
Fork 0
Code Issues3 Pull requests5 Activity

feat(container): update image victoriametrics/vmagent to v1.114.0 #859

Merged
SeanOMik merged 1 commit from renovate/victoriametrics-vmagent-1.x into main 2025-03-27 13:09:17 +00:00
Conversation 0 Commits 1 Files changed 1 +1 -1
Renovate commented 2025-03-21 15:07:43 +00:00
Collaborator

This PR contains the following updates:

Package Update Change
victoriametrics/vmagent minor v1.113.0 -> v1.114.0

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)

v1.114.0

Compare Source

v1.114.0

Released at 2025-03-21

Update note 1: metric vm_mmaped_fileswas renamed to vm_mmapped_files to fix the typo in word mmapped.

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

  • FEATURE: vmsingle, vminsert in VictoriaMetrics cluster and vmagent: support zstd compression for OpenTelemetry and Datadog metrics ingestion. See this and this issues.

  • FEATURE: vmagent: improve vmagent performance on parsing big responses in stream parsing mode. See this issue for details. Thanks to @​makasim for the pull request.

  • FEATURE: vmagent and Single-node VictoriaMetrics: use original unmodified by relabeling job name as scrape_pool value for /api/v1/targets responses. This change fixes discrepancy with Prometheus as mentioned in this issue. Thanks to @​evkuzin for the pull request.

  • FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: add command-line flag -search.maxTSDBStatusTopNSeries to allow setting a limit for topN argument accepted by /api/v1/status/tsdb endpoint.

  • FEATURE: vmsingle and vmagent: support AWS EKS Pod Identity. See this issue for details.

  • FEATURE: vmsingle and vmselect: improve performance of or binary operator. The performance was degraded in v1.111.0. See this and this issues for details.

  • FEATURE: vmalert: expose vmalert_alerts_send_duration_seconds metric to measure the time taken to send alerts to the specified -notifier.url. Thanks to @​eyazici90 for the pull request.

  • FEATURE: dashboards/single, dashboards/cluster, dashboards/vmagent, dashboards/vmalert: add panel Memory allocations rate to ResourceUsage tab, that shows the rate of allocations in memory and can help identifying issues with increased pressure on GC.

  • FEATURE: vmbackup, vmrestore, vmbackupmanager: improve resilience to network issues by retrying requests failing due to IncompleteBody. Previously, such requests were not retried and leaded to restore/backup process failure. See this PR for details.

  • FEATURE: vmui: move legend customization settings, such as Hide common labels and Table view, closer to the legend area. This change should improve UX and make it easier for users to adjust legend visualization. See this issue

  • BUGFIX: stream aggregation: fix panic on rate output. See this issue.

  • BUGFIX: stream aggregation: prevent unexpected samples drop when deduplication and aggregation windows are enabled.

  • BUGFIX: Single-node VictoriaMetrics and vmstorage: fix metric that shows number of active time series when per-day index is disabled. Previously, once per-day index was disabled, the active time series metric would stop being populated and the Active time series chart would show 0. See this issue for details.

  • BUGFIX: vmbackupmanager: fix graceful shutdown delay when stopping the backup manager. Previously, sending a SIGINT would lead to a long delay before the backup manager would stop. See this issue for details.

  • BUGFIX: vmbackupmanager: prevent a backup being scheduled 1 second after the previous one. See this issue.

  • BUGFIX: vmbackupmanager: do not set vm_backup_last_run_failed metric to 1 when running vmbackupmanager with an empty storage. Previously, the metrics was set to 1 even though backup was not created yet. See this issue.

  • BUGFIX: MetricsQL: prevent from too big duration panic when the query contains too big Ni durations because of too big step value. See this issue.

  • BUGFIX: vmalert, vmctl, vmbackup, vmrestore, vmbackupmanager: properly apply TLS settings for URLs with scheme other than https. Previously, TLS settings were ignored for such URLs. That could lead to unexpected behavior when a request was receiving a redirect response to a URL with https scheme. See this issue for details.

  • BUGFIX: vmagent: prevent dropping persistent queue data when changes happened for -remoteWrite.showURL flag, query params or fragment in remote write URL. See this issue.

  • BUGFIX: vmagent: properly send staleness markers if scrape error occurs. See this issue for details.

  • BUGFIX: vmselect in VictoriaMetrics cluster: properly handle multitenant query request on storage communication error. See this issue for details.

  • BUGFIX: vmsingle, vmagent, vminsert in VictoriaMetrics cluster: reduce number of allocations that could increase CPU usage on ingestion. See this issue for details.

  • BUGFIX: fix typo in metric vm_mmaped_files by renaming it to vm_mmapped_files.

  • BUGFIX: vmalert: fix memory leak when sending alerts with -notifier.blackhole enabled. Bug was introduced in v1.112.0.

  • BUGFIX: vmalert: properly compare rules group.checksum and statically define group.id at creation time. See this PR for details.

  • BUGFIX: vmalert: fix memory leak during rule group updates on reload. Bug was introduced in v1.112.0. See this issue.

  • BUGFIX: vmgateway: fix the vmgateway_ratelimit_refresh_duration_seconds value, before it did not account for the actual time spent refreshing limits.

  • BUGFIX: vmsingle, vmselect in VictoriaMetrics cluster: prevent panic in case subquery step value exceeds max allowed value. Previously, the following query would lead to panic rate(sum(up)[11i:922335359011637780i]). See this issue.

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.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [victoriametrics/vmagent](https://github.com/VictoriaMetrics/VictoriaMetrics) | minor | `v1.113.0` -> `v1.114.0` | --- ### Release Notes <details> <summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)</summary> ### [`v1.114.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.114.0) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.113.0...v1.114.0) #### [v1.114.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.114.0) Released at 2025-03-21 **Update note 1: metric `vm_mmaped_files`was renamed to `vm_mmapped_files` to fix the typo in word `mmapped`.** - SECURITY: upgrade Go builder from Go1.24.0 to Go1.24.1. See the list of issues addressed in [Go1.24.1](https://github.com/golang/go/issues?q=milestone%3AGo1.24.1+label%3ACherryPickApproved). - FEATURE: [vmsingle](https://docs.victoriametrics.com/single-server-victoriametrics/), `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/cluster-victoriametrics/) and [vmagent](https://docs.victoriametrics.com/vmagent/): support zstd compression for OpenTelemetry and Datadog metrics ingestion. See [this](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8380) and [this](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8300) issues. - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent/): improve vmagent performance on parsing big responses in [stream parsing mode](https://docs.victoriametrics.com/vmagent/#stream-parsing-mode). See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8159) for details. Thanks to [@&#8203;makasim](https://github.com/makasim) for [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/8515). - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent/) and [Single-node VictoriaMetrics](https://docs.victoriametrics.com/): use original unmodified by [relabeling](https://docs.victoriametrics.com/#relabeling) job name as `scrape_pool` value for [/api/v1/targets](https://docs.victoriametrics.com/#prometheus-querying-api-usage) responses. This change fixes discrepancy with Prometheus as mentioned in [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5343). Thanks to [@&#8203;evkuzin](https://github.com/evkuzin) for [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/8457). - FEATURE: [vmsingle](https://docs.victoriametrics.com/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/cluster-victoriametrics/): add command-line flag `-search.maxTSDBStatusTopNSeries` to allow setting a limit for topN argument accepted by `/api/v1/status/tsdb` endpoint. - FEATURE: [vmsingle](https://docs.victoriametrics.com/single-server-victoriametrics/) and [vmagent](https://docs.victoriametrics.com/vmagent/): support AWS EKS Pod Identity. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5780) for details. - FEATURE: [vmsingle](https://docs.victoriametrics.com/single-server-victoriametrics/) and [vmselect](https://docs.victoriametrics.com/cluster-victoriametrics/): improve performance of `or` binary operator. The performance was degraded in [v1.111.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.111.0). See [this](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7759) and [this](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8382) issues for details. - FEATURE: [vmalert](https://docs.victoriametrics.com/vmalert/): expose `vmalert_alerts_send_duration_seconds` metric to measure the time taken to send alerts to the specified `-notifier.url`. Thanks to [@&#8203;eyazici90](https://github.com/eyazici90) for [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/8468). - FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229), [dashboards/cluster](https://grafana.com/grafana/dashboards/11176), [dashboards/vmagent](https://grafana.com/grafana/dashboards/12683), [dashboards/vmalert](https://grafana.com/grafana/dashboards/14950): add panel `Memory allocations rate` to ResourceUsage tab, that shows the rate of allocations in memory and can help identifying issues with increased pressure on GC. - FEATURE: [vmbackup](https://docs.victoriametrics.com/vmbackup/), [vmrestore](https://docs.victoriametrics.com/vmrestore/), [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager/): improve resilience to network issues by retrying requests failing due to `IncompleteBody`. Previously, such requests were not retried and leaded to restore/backup process failure. See [this PR](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/8547) for details. - FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): move legend customization settings, such as `Hide common labels` and `Table view`, closer to the legend area. This change should improve UX and make it easier for users to adjust legend visualization. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8031) - BUGFIX: [stream aggregation](https://docs.victoriametrics.com/stream-aggregation): fix panic on `rate` output. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8469). - BUGFIX: [stream aggregation](https://docs.victoriametrics.com/stream-aggregation): prevent unexpected samples drop when [deduplication](https://docs.victoriametrics.com/stream-aggregation/#deduplication) and [aggregation windows](https://docs.victoriametrics.com/stream-aggregation/#aggregation-windows) are enabled. - BUGFIX: [Single-node VictoriaMetrics](https://docs.victoriametrics.com/) and [vmstorage](https://docs.victoriametrics.com/victoriametrics/): fix metric that shows number of active time series when per-day index is disabled. Previously, once per-day index was disabled, the active time series metric would stop being populated and the `Active time series` chart would show 0. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8411) for details. - BUGFIX: [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager/): fix graceful shutdown delay when stopping the backup manager. Previously, sending a `SIGINT` would lead to a long delay before the backup manager would stop. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8554) for details. - BUGFIX: [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager/): prevent a backup being scheduled 1 second after the previous one. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8499). - BUGFIX: [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager/): do not set `vm_backup_last_run_failed` metric to `1` when running vmbackupmanager with an empty storage. Previously, the metrics was set to `1` even though backup was not created yet. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8490). - BUGFIX: [MetricsQL](https://docs.victoriametrics.com/metricsql/): prevent from `too big duration` panic when the query contains too big `Ni` durations because of too big `step` value. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8447). - BUGFIX: [vmalert](https://docs.victoriametrics.com/vmalert/), [vmctl](https://docs.victoriametrics.com/vmctl/), [vmbackup](https://docs.victoriametrics.com/vmbackup/), [vmrestore](https://docs.victoriametrics.com/vmrestore/), [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager/): properly apply TLS settings for URLs with scheme other than `https`. Previously, TLS settings were ignored for such URLs. That could lead to unexpected behavior when a request was receiving a redirect response to a URL with `https` scheme. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8494) for details. - BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent/): prevent dropping persistent queue data when changes happened for `-remoteWrite.showURL` flag, query params or fragment in remote write URL. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8477). - BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent/): properly send staleness markers if scrape error occurs. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8528) for details. - BUGFIX: `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/cluster-victoriametrics/): properly handle `multitenant` query request on storage communication error. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8461) for details. - BUGFIX: [vmsingle](https://docs.victoriametrics.com/single-server-victoriametrics/), [vmagent](https://docs.victoriametrics.com/vmagent/), `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/cluster-victoriametrics/): reduce number of allocations that could increase CPU usage on ingestion. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8501) for details. - BUGFIX: fix typo in metric `vm_mmaped_files` by renaming it to `vm_mmapped_files`. - BUGFIX: [vmalert](https://docs.victoriametrics.com/vmalert/): fix memory leak when sending alerts with `-notifier.blackhole` enabled. Bug was introduced in [v1.112.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.112.0). - BUGFIX: [vmalert](https://docs.victoriametrics.com/vmalert/): properly compare rules `group.checksum` and statically define `group.id` at creation time. See [this PR](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/8540) for details. - BUGFIX: [vmalert](https://docs.victoriametrics.com/vmalert/): fix memory leak during rule group updates on reload. Bug was introduced in [v1.112.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.112.0). See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8532). - BUGFIX: [vmgateway](https://docs.victoriametrics.com/vmgateway): fix the `vmgateway_ratelimit_refresh_duration_seconds` value, before it did not account for the actual time spent refreshing limits. - BUGFIX: [vmsingle](https://docs.victoriametrics.com/single-server-victoriametrics/), `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/cluster-victoriametrics/): prevent panic in case [subquery](https://docs.victoriametrics.com/metricsql/#subqueries) step value exceeds max allowed value. Previously, the following query would lead to panic `rate(sum(up)[11i:922335359011637780i])`. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8447). </details> --- ### 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. --- - [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xODcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjE4Ny4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZS9jb250YWluZXIiLCJ0eXBlL21pbm9yIl19-->
Renovate added 1 commit 2025-03-21 15:07:43 +00:00
SeanOMik merged commit 800cc327a6 into main 2025-03-27 13:09:17 +00:00
SeanOMik deleted branch renovate/victoriametrics-vmagent-1.x 2025-03-27 13:09:17 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference: SeanOMik/k3s-cluster#859
No description provided.
Delete branch "renovate/victoriametrics-vmagent-1.x"

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?