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

Update victoriametrics/vmagent Docker tag to v1.124.0 #540

Merged
AverageMarcus merged 1 commits from renovate/victoriametrics into master 2025-08-19 05:27:07 +00:00
Conversation 0 Commits 1 Files Changed 2 +2 -2
renovate commented 2025-08-19 03:22:43 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
victoriametrics/vmagent minor v1.123.0 -> v1.124.0

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)

v1.124.0

Compare Source

v1.124.0

Released at 2025-08-15

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

  • FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: protect graphite /render API endpoint with new flag -search.maxGraphitePathExpressionLen. See this PR #​9534 for details.

  • FEATURE: expose vm_total_disk_space_bytes metric at the /metrics page, which shows the total disk space for the data directory specified via -storageDataPath. This metric can be useful for building alerts and graphs for the percentatge of free disk space via vm_free_disk_space_bytes / vm_total_disk_space_bytes. See this comment.

  • FEATURE: all: leave non-existing environment variables as is in config files instead of failure. For example, if the file referred by -promscrape.config contains %{NON_EXISTING_ENV_VAR} placeholder, then it is left as is instead of failing to load the file. This simplifies the usage of environment variables in config files and in command-line flags according to these docs. Users can easily notice non-existing env vars in config files and in command-line flags by looking at their values - they will literally contain %{NON_EXISTING_ENV_VAR} strings.

  • FEATURE: vmselect, vminsert and vmstorage in VictoriaMetrics cluster: add rpc handshake timeout configuration via -rpc.handshakeTimeout flag (default 5s). Set deadline for the entire handshake process instead of per-operation timeout. See #​9345 for more details.

  • FEATURE: vmagent: add -enableMetadata command-line flag to allow sending metadata to the configured -remoteWrite.url, metadata can be scraped from targets, received via VictoriaMetrics remote write, Prometheus remote write v1 or OpenTelemetry protocol. See #​2974.

  • BUGFIX: vmagent: treat single remoteWrite.disableOnDiskQueue flag the same way as if it is explicitly specified for each remote write url. See #​9565 for details.

  • BUGFIX: vmalert-tool: print a proper error message when templating function fails during execution. Previously, vmalert-tool could throw a misleading panic message instead.

  • BUGFIX: vmauth: properly read proxy-protocol header. See this PR #​9546 for details.

  • BUGFIX: dashboards/vmagent: fix samples rate panel not showing data in case vmagent is not scraping metrics. Previously, the panel would not display "samples in" results if vmagent only accepts metrics via push protocols.

  • BUGFIX: vmselect in VictoriaMetrics cluster: prevent resource leak on partial responses for /federate API requests. This this PR 9536 for details. Thanks to the @​fxrlv.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: prevent performance degradation on hitting daily or hourly series cardinality limits. See this issue 9554 for details.

  • BUGFIX: MetricsQL: gracefully handle histogram_quantile calculation for histograms where buckets are created on demand. This change isn't needed for users who use native instrumentation SDKs for metrics from VictoriaMetrics, Prometheus or OpenTelemetry.

  • BUGFIX: MetricsQL: return a proper error message when the function argument is expected to be a string or scalar.

  • BUGFIX: dashboards/victoriametrics-cluster: fix panels showing 99th percentile of series or samples read per query or per series. Before, panels were showing the summarized value across all vmselect instances, which didn't make much sense. Now, panels show the max value across the vmselect instances, making it easier to understand complexity of the heaviest queries served.

  • BUGFIX: vmalert: fix potential data race and missing firing states when replaying alerting rule with -replay.ruleEvaluationConcurrency>1.

  • BUGFIX: vmalert: fix the {{ $activeAt }} variable value in annotation templating when the alert has already triggered. See this issue #​9543 for details.

  • BUGFIX: vmbackup, vmbackupmanager: allow enabling checksum calculation for PUT requests by using -s3ChecksumAlgorithm command-line flag. This is required for S3 configurations with WORM being enabled. See #​9532.

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 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.123.0` -> `v1.124.0` | --- ### Release Notes <details> <summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)</summary> ### [`v1.124.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.124.0) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.123.0...v1.124.0) ##### [v1.124.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.124.0) Released at 2025-08-15 - SECURITY: upgrade Go builder from Go1.24.5 to Go1.24.6. See [the list of issues addressed in Go1.24.6](https://github.com/golang/go/issues?q=milestone%3AGo1.24.6+label%3ACherryPickApproved). - FEATURE: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and [vmselect](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/) in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): protect graphite `/render` API endpoint with new flag `-search.maxGraphitePathExpressionLen`. See this PR [#&#8203;9534](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9534) for details. - FEATURE: expose `vm_total_disk_space_bytes` metric at the [`/metrics` page](https://docs.victoriametrics.com/#monitoring), which shows the total disk space for the data directory specified via [`-storageDataPath`](https://docs.victoriametrics.com/#storage). This metric can be useful for building alerts and graphs for the percentatge of free disk space via `vm_free_disk_space_bytes / vm_total_disk_space_bytes`. See [this comment](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9523#issuecomment-3149459926). - FEATURE: all: leave non-existing environment variables as is in config files instead of failure. For example, if the file referred by `-promscrape.config` contains `%{NON_EXISTING_ENV_VAR}` placeholder, then it is left as is instead of failing to load the file. This simplifies the usage of environment variables in config files and in command-line flags according to [these docs](https://docs.victoriametrics.com/victoriametrics/#environment-variables). Users can easily notice non-existing env vars in config files and in command-line flags by looking at their values - they will literally contain `%{NON_EXISTING_ENV_VAR}` strings. - FEATURE: `vmselect`, `vminsert` and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): add rpc handshake timeout configuration via `-rpc.handshakeTimeout` flag (default 5s). Set deadline for the entire handshake process instead of per-operation timeout. See [#&#8203;9345](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9345) for more details. - FEATURE: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): add `-enableMetadata` command-line flag to allow sending metadata to the configured `-remoteWrite.url`, metadata can be scraped from targets, received via VictoriaMetrics remote write, Prometheus remote write v1 or OpenTelemetry protocol. See [#&#8203;2974](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2974). - BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent/): treat single `remoteWrite.disableOnDiskQueue` flag the same way as if it is explicitly specified for each remote write url. See [#&#8203;9565](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9565) for details. - BUGFIX: [vmalert-tool](https://docs.victoriametrics.com/victoriametrics/vmalert-tool/): print a proper error message when templating function fails during execution. Previously, vmalert-tool could throw a misleading panic message instead. - BUGFIX: [vmauth](https://docs.victoriametrics.com/victoriametrics/vmauth/): properly read proxy-protocol header. See this PR [#&#8203;9546](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9546) for details. - BUGFIX: [dashboards/vmagent](https://grafana.com/grafana/dashboards/12683): fix samples rate panel not showing data in case vmagent is not scraping metrics. Previously, the panel would not display "samples in" results if vmagent only accepts metrics via push protocols. - BUGFIX: [vmselect](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/) in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): prevent resource leak on partial responses for `/federate` API requests. This this PR [9536](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/9536) for details. Thanks to the [@&#8203;fxrlv](https://github.com/fxrlv). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): prevent performance degradation on hitting daily or hourly series cardinality limits. See this issue [9554](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9554) for details. - BUGFIX: [MetricsQL](https://docs.victoriametrics.com/victoriametrics/metricsql/): gracefully handle `histogram_quantile` calculation for histograms where buckets are created on demand. This change isn't needed for users who use native instrumentation SDKs for metrics from [VictoriaMetrics](https://github.com/VictoriaMetrics/metrics), [Prometheus](https://prometheus.io/docs/instrumenting/clientlibs/) or [OpenTelemetry](https://opentelemetry.io/docs/languages/). - BUGFIX: [MetricsQL](https://docs.victoriametrics.com/victoriametrics/metricsql/): return a proper error message when the function argument is expected to be a string or scalar. - BUGFIX: [dashboards/victoriametrics-cluster](https://grafana.com/grafana/dashboards/11176): fix panels showing 99th percentile of series or samples read per query or per series. Before, panels were showing the summarized value across all vmselect instances, which didn't make much sense. Now, panels show the max value across the vmselect instances, making it easier to understand complexity of the heaviest queries served. - BUGFIX: [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/): fix potential data race and missing firing states when replaying alerting rule with `-replay.ruleEvaluationConcurrency>1`. - BUGFIX: [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/): fix the `{{ $activeAt }}` variable value in annotation templating when the alert has already triggered. See this issue [#&#8203;9543](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9543) for details. - BUGFIX: [vmbackup](https://docs.victoriametrics.com/vmbackup/), [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager/): allow enabling checksum calculation for PUT requests by using `-s3ChecksumAlgorithm` command-line flag. This is required for S3 configurations with WORM being enabled. See [#&#8203;9532](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9532). </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 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:eyJjcmVhdGVkSW5WZXIiOiI0MS44MS4xIiwidXBkYXRlZEluVmVyIjoiNDEuODEuMSIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6W119-->
renovate added 1 commit 2025-08-19 03:22:44 +00:00
Update victoriametrics/vmagent Docker tag to v1.124.0 d953074087
AverageMarcus merged commit d600d44640 into master 2025-08-19 05:27:07 +00:00
AverageMarcus deleted branch renovate/victoriametrics 2025-08-19 05:27:07 +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#540
No description provided.
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?