Update victoriametrics/vmagent Docker tag to v1.155.0 #825

Merged
AverageMarcus merged 1 commits from renovate/victoriametrics into master 2026-10-27 07:08:34 +00:00
Collaborator

This PR contains the following updates:

Package Update Change
victoriametrics/vmagent minor v1.154.1 → v1.155.0

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)

v1.155.0

Compare Source

v1.155.0

Released at 2026-10-23

Update Note 1: vmselect in VictoriaMetrics cluster: /admin/tenants requests without start and end query args now return tenants for the current day. This is a breaking change because previously it was expected to return all tenants. If you still need to retrieve all tenants, set the start and end params so that the resulting time range fully includes the -retentionPeriod. Also note that vmctl is known to send requests to /admin/tenants under the hood when migrating data between VictoriaMetrics deployments. Therefore, make sure that you run vmctl with both *-filter-time-start and *-filter-time-end params. See the updated URL format and #​11791 for details.

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

  • SECURITY: upgrade base docker image (Alpine) from 3.24.2 to 3.24.3. See Alpine 3.24.4 release notes.

  • FEATURE: all VictoriaMetrics components: add -healthcheck command-line flag, which checks that the running process accepts connections at -httpListenAddr and exits with non-zero code if the check fails. This allows setting up Docker HEALTHCHECK in images without curl or wget. See these docs and VictoriaLogs#1565.

  • FEATURE: all VictoriaMetrics components: expose process_cpu_cores_host, process_cpu_cores_cgroup_quota, process_memory_host_bytes and process_memory_cgroup_bytes metrics. Cgroup metrics are -1 if no cgroup limit is set or the limit cannot be read. See #​11460.

  • FEATURE: vmui: deprecate Server URL editing and show a warning when using a saved custom URL. Existing custom URLs continue to work. See #​11735.

  • FEATURE: vmui: update the appearance of error, warning, info, and success messages. See #​11736.

  • FEATURE: vmui: add a tenant column to Top Queries and Active Queries when tenant information is available. See #​6346.

  • FEATURE: vmui: limit tenant discovery to the selected time range. See #​11784.

  • FEATURE: vmagent and Single-node VictoriaMetrics: limit the number of logged parse errors per each scrape of a target via -promscrape.maxParseErrorsPerScrape command-line flag (20 by default). The number of suppressed parse errors is logged after the scrape. This prevents log flooding from targets exposing many malformed lines. See #​8856.

  • FEATURE: vmalert: restore Prometheus compatibility for alerts state restoration, so Prometheus can be used as -remoteRead.url again. Previously, the restore query used MetricsQL function default_rollup() which Prometheus rejects, so the state of alerting rules with for > 0 was reset on every vmalert restart. See #​11574.

  • FEATURE: vmselect in VictoriaMetrics cluster: export vm_request_duration_seconds{path="/admin/tenants"} for tracking time it takes to fetch tenants from the database.

  • FEATURE: dashboards: apply the instance filter to the CPU pressure, Memory pressure, IO pressure, and Memory allocations rate panels in the Resource usage section of the VictoriaMetrics - cluster dashboard. Displays zero disk I/O and syscall rates. See #​11742.

  • FEATURE: alerts-health: add TooManySnapshots alerting rule. It notifies about instances where more than 2 snapshots are stored for at least 2 hours. Such snapshots are usually left behind by failed vmbackup / vmbackupmanager runs. They keep references to the already merged data parts and prevent background merges from freeing the disk space, which results in excessive disk usage. See #​9344.

  • BUGFIX: vmagent: prevent Kafka remote write getting stuck after TLS certificates are reloaded. Previously, when vmagent detected changed certificates and restarted the Kafka producer, pending sends to the old producer could hang forever and the remote write queue stopped draining until vmagent was restarted. Now such sends are retried with the new producer. See #​11737.

  • BUGFIX: vminsert in VictoriaMetrics cluster: prevent metric metadata drops after transient RPC handshake timeouts when connecting to vmstorage. See #​11762. Thanks to @​sakateka for contribution.

  • BUGFIX: vmsingle, vmagent and vminsert in VictoriaMetrics cluster: properly validate time series ingested via /api/v1/import/native. See #​11745. Thanks to @​meshchellomishel for contribution.

  • BUGFIX: vmsingle and vmagent: reduce memory usage during for Kubernetes service discovery, when scrape configuration has many entries that matches small subset of targets. See #​11751. Thanks to @​CamberLoid for contribution.

  • BUGFIX: vmsingle and vmstorage in VictoriaMetrics cluster: prevent search requests panic. See #​11788 for details.

  • BUGFIX: vmsingle and vmagent: set __meta_kubernetes_namespace and the namespace metadata to the namespace of the Endpoints or EndpointSlice object in role: endpoints and role: endpointslice service discovery when the referenced pod lives in another namespace. Previously the namespace of the pod was used, unlike Prometheus. See #​11798. Thanks to @​cestercian for contribution.

  • BUGFIX: vmauth: skip keys with unsupported kty or crv, missing required members or invalid values in the JWKS fetched via OIDC discovery instead of rejecting the whole key set, as required by RFC 7517. Previously, a single unsupported or malformed key in the JWKS caused vmauth to reject all JWTs from that issuer, including tokens signed with supported keys. See #​11748.

  • BUGFIX: vmui: stop saving the automatically calculated query step in shared URLs, so opening a link recalculates the step for the selected time range and screen width. Explicitly configured steps remain fixed. See #​11638.

  • BUGFIX: vmselect in VictoriaMetrics cluster: change the default time range for /admin/tenants HTTP endpoint to search tenants only for the current day instead of searching the entire [0, now] time range. This should prevent unnecessary load on vmstorage and prevent OOMs. See the updated URL format and #​11791 for 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [victoriametrics/vmagent](https://github.com/VictoriaMetrics/VictoriaMetrics) | minor | `v1.154.1` → `v1.155.0` | --- ### Release Notes <details> <summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)</summary> ### [`v1.155.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.155.0) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.154.1...v1.155.0) ##### [v1.155.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.155.0) Released at 2026-10-23 **Update Note 1:** `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): `/admin/tenants` requests without `start` and `end` query args now return tenants for the current day. This is a breaking change because previously it was expected to return all tenants. If you still need to retrieve all tenants, set the `start` and `end` params so that the resulting time range fully includes the `-retentionPeriod`. Also note that [vmctl](https://docs.victoriametrics.com/victoriametrics/vmctl/victoriametrics/) is known to send requests to `/admin/tenants` under the hood when migrating data between VictoriaMetrics deployments. Therefore, make sure that you run `vmctl` with both `*-filter-time-start` and `*-filter-time-end` params. See the updated [URL format](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#url-format) and [#&#8203;11791](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11791) for details. - SECURITY: upgrade Go builder from Go1.27.2 to Go1.27.3. See [the list of issues addressed in Go1.27.3](https://github.com/golang/go/issues?q=milestone%3AGo1.27.3%20label%3ACherryPickApproved). - SECURITY: upgrade base docker image (Alpine) from 3.24.2 to 3.24.3. See [Alpine 3.24.4 release notes](https://alpinelinux.org/posts/Alpine-3.21.9-3.22.7-3.23.7-3.24.3-released.html). - FEATURE: all VictoriaMetrics components: add `-healthcheck` command-line flag, which checks that the running process accepts connections at `-httpListenAddr` and exits with non-zero code if the check fails. This allows setting up Docker `HEALTHCHECK` in images without `curl` or `wget`. See [these docs](https://docs.victoriametrics.com/victoriametrics/url-examples/#health) and [VictoriaLogs#1565](https://github.com/VictoriaMetrics/VictoriaLogs/issues/1565). - FEATURE: all VictoriaMetrics components: expose `process_cpu_cores_host`, `process_cpu_cores_cgroup_quota`, `process_memory_host_bytes` and `process_memory_cgroup_bytes` metrics. Cgroup metrics are `-1` if no cgroup limit is set or the limit cannot be read. See [#&#8203;11460](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11460). - FEATURE: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): deprecate Server URL editing and show a warning when using a saved custom URL. Existing custom URLs continue to work. See [#&#8203;11735](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11735). - FEATURE: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): update the appearance of error, warning, info, and success messages. See [#&#8203;11736](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/11736). - FEATURE: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): add a tenant column to Top Queries and Active Queries when tenant information is available. See [#&#8203;6346](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6346). - FEATURE: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): limit tenant discovery to the selected time range. See [#&#8203;11784](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11784). - FEATURE: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/) and [Single-node VictoriaMetrics](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/): limit the number of logged parse errors per each scrape of a target via `-promscrape.maxParseErrorsPerScrape` command-line flag (20 by default). The number of suppressed parse errors is logged after the scrape. This prevents log flooding from targets exposing many malformed lines. See [#&#8203;8856](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8856). - FEATURE: [vmalert](https://docs.victoriametrics.com/victoriametrics/vmalert/): restore Prometheus compatibility for alerts state restoration, so Prometheus can be used as `-remoteRead.url` again. Previously, the restore query used MetricsQL function `default_rollup()` which Prometheus rejects, so the state of alerting rules with `for > 0` was reset on every vmalert restart. See [#&#8203;11574](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11574). - FEATURE: `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): export `vm_request_duration_seconds{path="/admin/tenants"}` for tracking time it takes to fetch [tenants](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#multitenancy) from the database. - FEATURE: [dashboards](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/master/dashboards): apply the instance filter to the `CPU pressure`, `Memory pressure`, `IO pressure`, and `Memory allocations rate` panels in the Resource usage section of the [VictoriaMetrics - cluster](https://grafana.com/grafana/dashboards/11176-victoriametrics-cluster/) dashboard. Displays zero disk I/O and syscall rates. See [#&#8203;11742](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/11742). - FEATURE: [alerts-health](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/deployment/docker/rules/alerts-health.yml): add `TooManySnapshots` alerting rule. It notifies about instances where more than 2 [snapshots](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#how-to-work-with-snapshots) are stored for at least 2 hours. Such snapshots are usually left behind by failed `vmbackup` / `vmbackupmanager` runs. They keep references to the already merged data parts and prevent [background merges](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#storage) from freeing the disk space, which results in excessive disk usage. See [#&#8203;9344](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/9344). - BUGFIX: [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): prevent [Kafka remote write](https://docs.victoriametrics.com/victoriametrics/integrations/kafka/) getting stuck after TLS certificates are reloaded. Previously, when vmagent detected changed certificates and restarted the Kafka producer, pending sends to the old producer could hang forever and the remote write queue stopped draining until vmagent was restarted. Now such sends are retried with the new producer. See [#&#8203;11737](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11737). - BUGFIX: `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): prevent metric metadata drops after transient RPC handshake timeouts when connecting to `vmstorage`. See [#&#8203;11762](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/11762). Thanks to [@&#8203;sakateka](https://github.com/sakateka) for contribution. - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/), [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/) and `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): properly validate time series ingested via [`/api/v1/import/native`](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#how-to-import-data-in-native-format). See [#&#8203;11745](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/11745). Thanks to [@&#8203;meshchellomishel](https://github.com/meshchellomishel) for contribution. - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): reduce memory usage during for Kubernetes service discovery, when scrape configuration has many entries that matches small subset of targets. See [#&#8203;11751](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/11751). Thanks to [@&#8203;CamberLoid](https://github.com/CamberLoid) for contribution. - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): prevent search requests panic. See [#&#8203;11788](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11788) for details. - BUGFIX: [vmsingle](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/) and [vmagent](https://docs.victoriametrics.com/victoriametrics/vmagent/): set `__meta_kubernetes_namespace` and the namespace metadata to the namespace of the `Endpoints` or `EndpointSlice` object in [`role: endpoints`](https://docs.victoriametrics.com/victoriametrics/sd_configs/#kubernetes_sd_configs) and `role: endpointslice` service discovery when the referenced pod lives in another namespace. Previously the namespace of the pod was used, unlike Prometheus. See [#&#8203;11798](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11798). Thanks to [@&#8203;cestercian](https://github.com/cestercian) for contribution. - BUGFIX: [vmauth](https://docs.victoriametrics.com/victoriametrics/vmauth/): skip keys with unsupported `kty` or `crv`, missing required members or invalid values in the JWKS fetched via [OIDC discovery](https://docs.victoriametrics.com/victoriametrics/vmauth/#oidc-discovery) instead of rejecting the whole key set, as required by [RFC 7517](https://www.rfc-editor.org/rfc/rfc7517#section-5). Previously, a single unsupported or malformed key in the JWKS caused vmauth to reject all JWTs from that issuer, including tokens signed with supported keys. See [#&#8203;11748](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11748). - BUGFIX: [vmui](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#vmui): stop saving the automatically calculated query step in shared URLs, so opening a link recalculates the step for the selected time range and screen width. Explicitly configured steps remain fixed. See [#&#8203;11638](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11638). - BUGFIX: `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/): change the default time range for [/admin/tenants](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#multitenancy) HTTP endpoint to search tenants only for the current day instead of searching the entire `[0, now]` time range. This should prevent unnecessary load on `vmstorage` and prevent OOMs. See the updated [URL format](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#url-format) and [#&#8203;11791](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/11791) for details. </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 [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xODQuMSIsInVwZGF0ZWRJblZlciI6IjQ0LjE4NC4xIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=-->
renovate added 1 commit 2026-10-27 03:10:59 +00:00
renovate force-pushed renovate/victoriametrics from 38b24eb776 to 8895a77df1 2026-10-27 03:10:59 +00:00 Compare
AverageMarcus merged commit d623f3bc16 into master 2026-10-27 07:08:34 +00:00
AverageMarcus deleted branch renovate/victoriametrics 2026-10-27 07:08:34 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: AverageMarcus/cluster.fun#825