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

Update victoriametrics/vmagent Docker tag to v1.136.0 #654

Merged
AverageMarcus merged 1 commits from renovate/victoriametrics into master 2026-02-17 17:54:42 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate commented 2026-02-17 03:16:53 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
victoriametrics/vmagent minor v1.135.0 → v1.136.0

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)

v1.136.0

Compare Source

v1.136.0

Released at 2026-02-13

  • SECURITY: upgrade Go builder from Go1.25.6 to Go1.26.0. See Go 1.26 release notes.

  • SECURITY: upgrade base docker image (Alpine) from 3.23.2 to 3.23.3. See Alpine 3.23.3 release notes.

  • FEATURE: dashboards/single, dashboards/cluster, dashboards/vmagent: add clickable source code links to the Logging rate panel in Drilldown. Users can use it to navigate directly to the source code location that generated those logs, making debugging and code exploration easier. See #​10406.

  • FEATURE: vmui: add Queries with most memory to execute section in Top Queries page of vmui. It can help users to find queries that consume most memory and potentially cause OOM. See #​9330.

  • FEATURE: vmui: make label value autocomplete context-aware by suggesting values only from series matching already selected label filters. See #​9269.

  • BUGFIX: all VictoriaMetrics components: respect default http client proxy env variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY). See #​10385. Thanks to @​zane-deg for the contribution.

  • BUGFIX: vmagent and vmsingle: properly expose kubernetes_sd discovery network dialer metrics vm_promscrape_discovery_kubernetes_conn_*. See #​10382.

  • BUGFIX: vmsingle: slightly reduce memory usage for metrics-metadata ingestion. See #​10392.

  • BUGFIX: VictoriaMetrics enterprise vmagent and vmsingle: introduce time‑based manual offset commit for kafka consumer to fix performance degradation with enabled manual commit. After this change, the consumer will commit partition offsets in batch per second to avoid high commit QPS on the Kafka broker. It's no longer recommended to set enable.auto.commit=true in -kafka.consumer.topic.options, as vmagent will automatically manage it. See #​10395.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: fix vm_deduplicated_samples_total{type="select"} to correctly count deduplicated identical samples with the same timestamp and value. See #​10400.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: properly prettify metricsql queries with regex. See metricsql#60. Thanks to @​freeseacher for the contribution.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: previously the Graphite render API used a fixed process timeout that could expire before long queries completed; now the timeout follows the query deadline, so users can extend it via -search.maxQueryDuration or the timeout argument in the query. See #​8484.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: properly report last partition metrics at the end of current month. See #​10387.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: avoid slow-path deduplication for time series with staleness markers. See #​10384. Thanks to @​fxrlv for the contribution.

  • BUGFIX: vmsingle, vminsert in VictoriaMetrics cluster and vmagent: ensure proper reset of buf size for OpenTelemetry ingestion, and allow flushing when buf size exceeds 4MiB. Previously, when a small number of requests carried a large volume of time series or labels, buf was over-expanded and recycled to the pool, resulting in excessive memory usage. See #​10378.

  • BUGFIX: vmsingle and vmselect in VictoriaMetrics cluster: correctly display hierarchy of actions in query trace during index searches. Before, search within the specific index was placed out of scope in the trace. See #​10459.

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.135.0` → `v1.136.0` | --- ### Release Notes <details> <summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)</summary> ### [`v1.136.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.136.0) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.135.0...v1.136.0) ##### [v1.136.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.136.0) Released at 2026-02-13 - SECURITY: upgrade Go builder from Go1.25.6 to Go1.26.0. See [Go 1.26 release notes](https://go.dev/doc/go1.26). - SECURITY: upgrade base docker image (Alpine) from 3.23.2 to 3.23.3. See [Alpine 3.23.3 release notes](https://www.alpinelinux.org/posts/Alpine-3.20.9-3.21.6-3.22.3-3.23.3-released.html). - 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): add clickable source code links to the `Logging rate` panel in `Drilldown`. Users can use it to navigate directly to the source code location that generated those logs, making debugging and code exploration easier. See [#&#8203;10406](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10406). - FEATURE: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): add `Queries with most memory to execute` section in `Top Queries` page of `vmui`. It can help users to find queries that consume most memory and potentially cause OOM. See [#&#8203;9330](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9330). - FEATURE: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): make label value autocomplete context-aware by suggesting values only from series matching already selected label filters. See [#&#8203;9269](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9269). - BUGFIX: all VictoriaMetrics components: respect default http client proxy env variables (`HTTP_PROXY`, `HTTPS_PROXY`, `NO_PROXY`). See [#&#8203;10385](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10385). Thanks to [@&#8203;zane-deg](https://github.com/zane-deg) for the contribution. - BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent/) and [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/): properly expose `kubernetes_sd` discovery network dialer metrics `vm_promscrape_discovery_kubernetes_conn_*`. See [#&#8203;10382](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10382). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/): slightly reduce memory usage for [metrics-metadata](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#metrics-metadata) ingestion. See [#&#8203;10392](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10392). - BUGFIX: VictoriaMetrics [enterprise](https://docs.victoriametrics.com/enterprise/) [vmagent](https://docs.victoriametrics.com/vmagent/) and [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/): introduce time‑based manual offset commit for [kafka consumer](https://docs.victoriametrics.com/victoriametrics/integrations/kafka/) to fix performance degradation with enabled manual commit. After this change, the consumer will commit partition offsets in batch per second to avoid high commit QPS on the Kafka broker. It's no longer recommended to set `enable.auto.commit=true` in `-kafka.consumer.topic.options`, as `vmagent` will automatically manage it. See [#&#8203;10395](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10395). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): fix `vm_deduplicated_samples_total{type="select"}` to correctly count deduplicated identical samples with the same timestamp and value. See [#&#8203;10400](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10400). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): properly prettify metricsql queries with `regex`. See [metricsql#60](https://github.com/VictoriaMetrics/metricsql/issues/60). Thanks to [@&#8203;freeseacher](https://github.com/freeseacher) for the contribution. - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): previously the [Graphite render API](https://docs.victoriametrics.com/victoriametrics/integrations/graphite/#render-api) used a fixed process timeout that could expire before long queries completed; now the timeout follows the query deadline, so users can extend it via `-search.maxQueryDuration` or the `timeout` [argument in the query](https://docs.victoriametrics.com/victoriametrics/keyconcepts/#query-data). See [#&#8203;8484](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8484). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): properly report last partition metrics at the end of current month. See [#&#8203;10387](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10387). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): avoid slow-path deduplication for time series with [staleness markers](https://docs.victoriametrics.com/victoriametrics/vmagent/#prometheus-staleness-markers). See [#&#8203;10384](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10384). Thanks to [@&#8203;fxrlv](https://github.com/fxrlv) for the contribution. - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/), `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/) and [vmagent](https://docs.victoriametrics.com/vmagent/): ensure proper reset of `buf` size for OpenTelemetry ingestion, and allow flushing when `buf` size exceeds 4MiB. Previously, when a small number of requests carried a large volume of time series or labels, `buf` was over-expanded and recycled to the pool, resulting in excessive memory usage. See [#&#8203;10378](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10378). - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): correctly display hierarchy of actions in [query trace](https://docs.victoriametrics.com/victoriametrics/#query-tracing) during index searches. Before, search within the specific index was placed out of scope in the trace. See [#&#8203;10459](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/10459). </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:eyJjcmVhdGVkSW5WZXIiOiI0My4xOS4yIiwidXBkYXRlZEluVmVyIjoiNDMuMTkuMiIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6W119-->
renovate added 1 commit 2026-02-17 03:16:54 +00:00
Update victoriametrics/vmagent Docker tag to v1.136.0 0930e7cd59
AverageMarcus merged commit c8fd05f0df into master 2026-02-17 17:54:42 +00:00
AverageMarcus deleted branch renovate/victoriametrics 2026-02-17 17:54:42 +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#654
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?