feat(container): update image victoriametrics/victoria-metrics to v1.109.1 #651

Merged
SeanOMik merged 1 commit from renovate/victoriametrics-victoria-metrics-1.x into main 2025-01-19 15:21:04 +00:00
Collaborator

This PR contains the following updates:

Package Update Change
victoriametrics/victoria-metrics minor v1.108.1 -> v1.109.1

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/victoria-metrics)

v1.109.1

Compare Source

Released at 2025-01-17

v1.109.0

Compare Source

v1.109.0

Released at 2025-01-14

Update note: This release contains issue that might affect correctness of increase, increase_pure and delta functions. It affects only vmselect or VictoriaMetrics single-node on query time. Please, rollback vmselects to the closest previous version or update to v1.109.1.

  • FEATURE: all the VictoriaMetrics components: increase the default value for GOGC from 30 to 100. This should reduce CPU usage at the cost of slightly higher memory usage. Single-node VictoriaMetrics, vmagent and vmstorage components continue using GOGC=30, since they are optimized for low memory allocations and low memory usage, so they do not benefit from the increased GOGC value too much. It is possible to override the default GOGC value in any VictoriaMetrics component by setting GOGC environment variable to the desired value. For example, GOGC=200 ./path/to/vmagent starts vmagent with GOGC=200. See these docs about GOGC tuning. See this issue.

  • FEATURE: vmui: add export data functionality for the Raw Query page and the ability to import exported data into the Query Analyzer page. See this issue.

  • FEATURE: vmui: add markdown support for comments during data export. this pull request.

  • FEATURE: vmagent and Single-node VictoriaMetrics: added min and max metrics for Datadog Sketches API metrics, changed _ metric name separator to . if metrics are not sanitized for consistency.

  • FEATURE: vmagent and Single-node VictoriaMetrics: add service discovery support for Marathon. See these docs and this issue.

  • FEATURE: Single-node VictoriaMetrics: support -maxIngestionRate cmd-line flag to ratelimit samples/sec ingested. See this issue for details.

  • FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: improve query performance on systems with high number of CPU cores. See this PR for details.

  • FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: add command-line flag -search.maxBinaryOpPushdownLabelValues to allow using labels with more candidate values as push down filter in binary operation. See this pull request. Thanks to @​tydhot for implementation.

  • FEATURE: vmsingle and vmstorage in VictoriaMetrics cluster: add command-line flag storage.finalDedupScheduleCheckInterval to control the final deduplication process interval. See this issue for details.

  • FEATURE: Single-node VictoriaMetrics and vmstorage in VictoriaMetrics cluster: add a separate cache type for storing sparse entries when performing large index scans. This significantly reduces memory usage when applying downsampling filters and retention filters during background merge. See this issue for the details.

  • BUGFIX: dashboards: consistently use vmagent_remotewrite_pending_data_bytes on vmagent dashboard to represent persistent queue size.

  • BUGFIX: vmalert: fix the auto-generated metrics ALERTS and ALERTS_FOR_STATE for alerting rules. Previously, metrics might have incorrect labels and affect the restore process. See this issue.

  • BUGFIX: vmalert: do not append tenant info to VictoriaLogs datasource request path in clusterMode. See this doc for how to use multitenancy in VictoriaLogs.

  • BUGFIX: vmauth: properly set host field at debug information formatted with dump_request_on_errors: true setting.

  • BUGFIX: vmauth: properly handle discovery for ipv6 addresses. Thanks to @​badie for the pull request.

  • BUGFIX: vmctl: fix support for migrating influx series without any tag. See this issue. Thanks to @​bitbidu for reporting.

  • BUGFIX: vminsert: storage nodes defined in -storageNode are now sorted, ensuring that varying node orders across different vminsert instances do not result in inconsistent replication.

  • BUGFIX: vmsingle and vminsert in VictoriaMetrics cluster: properly ingest influx line protocol metrics with empty tags. See this issue for details.

  • BUGFIX: vmselect: allow to override the default unique time series limit in vmstorage with command-line flags like -search.maxUniqueTimeseries, -search.maxLabelsAPISeries. See this issue.

  • BUGFIX: vmselect: properly set tenancy information when evaluating numbers in a query. Previously, the tenancy information could lead to mismatch between query result and a number. See this issue for the details.

  • BUGFIX: vmalert: fix marshaling of request body for Alertmanager notification. See this issue for the details.

  • BUGFIX: Single-node VictoriaMetrics and vmselect: don't take into account the last raw sample before the lookbehind window is sample exceeds the staleness interval. This affects correctness of increase, increase_pure, delta functions when preforming calculations on time series with gaps. See this pull request for 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.


  • 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/victoria-metrics](https://github.com/VictoriaMetrics/VictoriaMetrics) | minor | `v1.108.1` -> `v1.109.1` | --- ### Release Notes <details> <summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/victoria-metrics)</summary> ### [`v1.109.1`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.109.1) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.109.0...v1.109.1) Released at 2025-01-17 - SECURITY: upgrade base docker image (Alpine) from 3.21.0 to 3.21.2. See [Alpine 3.21.1 release notes](https://alpinelinux.org/posts/Alpine-3.21.1-released.html) and [Alpine 3.21.2 release notes](https://alpinelinux.org/posts/Alpine-3.18.11-3.19.6-3.20.5-3.21.2-released.html). - 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/): log metric names for signals with unsupported delta temporality on ingestion via [OpenTelemetry protocol for metrics](https://docs.victoriametrics.com/#sending-data-via-opentelemetry). Thanks to [@&#8203;chenlujjj](https://github.com/chenlujjj) for [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/8018). - BUGFIX: [Single-node VictoriaMetrics](https://docs.victoriametrics.com/) and [vmselect](https://docs.victoriametrics.com/cluster-victoriametrics/): fix incorrect behavior of increase, increase_pure, delta caused by [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/8002). This fix reverts to the previous behavior before [v1.109.0](https://docs.victoriametrics.com/changelog/#v11090). But allows controlling staleness detection for these functions explicitly via `-search.maxStalenessInterval`. - BUGFIX: all VictoriaMetrics [enterprise](https://docs.victoriametrics.com/enterprise/) components: remove unnecessary delay before failing if all online verification attempts have failed. This should reduce the time required for the component to proceed if all online verification attempts have failed. ### [`v1.109.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.109.0) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.108.1...v1.109.0) #### [v1.109.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.109.0) Released at 2025-01-14 **Update note: This release contains [issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/8045) that might affect correctness of increase, increase_pure and delta functions. It affects only vmselect or VictoriaMetrics single-node on query time. Please, rollback vmselects to the closest previous version or update to [v1.109.1](https://docs.victoriametrics.com/changelog/#v11091).** - FEATURE: all the VictoriaMetrics components: increase the default value for [`GOGC`](https://tip.golang.org/doc/gc-guide#GOGC) from `30` to `100`. This should reduce CPU usage at the cost of slightly higher memory usage. [Single-node VictoriaMetrics](https://docs.victoriametrics.com/), [vmagent](https://docs.victoriametrics.com/vmagent/) and [vmstorage](https://docs.victoriametrics.com/cluster-victoriametrics/#architecture-overview) components continue using `GOGC=30`, since they are optimized for low memory allocations and low memory usage, so they do not benefit from the increased GOGC value too much. It is possible to override the default `GOGC` value in any VictoriaMetrics component by setting `GOGC` environment variable to the desired value. For example, `GOGC=200 ./path/to/vmagent` starts `vmagent` with `GOGC=200`. See [these docs](https://tip.golang.org/doc/gc-guide#GOGC) about `GOGC` tuning. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7902). - FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): add export data functionality for the `Raw Query` page and the ability to import exported data into the `Query Analyzer` page. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7628). - FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): add `markdown` support for comments during data export. [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/7828). - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent/) and [Single-node VictoriaMetrics](https://docs.victoriametrics.com/): added `min` and `max` metrics for Datadog Sketches API metrics, changed `_` metric name separator to `.` if metrics are not sanitized for consistency. - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent/) and [Single-node VictoriaMetrics](https://docs.victoriametrics.com/): add service discovery support for [Marathon](https://mesosphere.github.io/marathon/). See [these docs](https://docs.victoriametrics.com/sd_configs/#marathon_sd_configs) and [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6642). - FEATURE: [Single-node VictoriaMetrics](https://docs.victoriametrics.com/): support `-maxIngestionRate` cmd-line flag to ratelimit samples/sec ingested. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7377) for details. - FEATURE: [vmsingle](https://docs.victoriametrics.com/single-server-victoriametrics/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/cluster-victoriametrics/): improve query performance on systems with high number of CPU cores. See [this PR](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/7416) for details. - 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.maxBinaryOpPushdownLabelValues` to allow using labels with more candidate values as push down filter in binary operation. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/7243). Thanks to [@&#8203;tydhot](https://github.com/tydhot) for implementation. - FEATURE: [vmsingle](https://docs.victoriametrics.com/single-server-victoriametrics/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/cluster-victoriametrics/): add command-line flag `storage.finalDedupScheduleCheckInterval` to control the final deduplication process interval. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7880) for details. - FEATURE: [Single-node VictoriaMetrics](https://docs.victoriametrics.com/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/cluster-victoriametrics/): add a separate cache type for storing sparse entries when performing large index scans. This significantly reduces memory usage when applying [downsampling filters](https://docs.victoriametrics.com/#downsampling) and [retention filters](https://docs.victoriametrics.com/#retention-filters) during background merge. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7182) for the details. - BUGFIX: [dashboards](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/dashboards): consistently use `vmagent_remotewrite_pending_data_bytes` on vmagent dashboard to represent persistent queue size. - BUGFIX: [vmalert](https://docs.victoriametrics.com/vmalert/): fix the auto-generated metrics `ALERTS` and `ALERTS_FOR_STATE` for alerting rules. Previously, metrics might have incorrect labels and affect the restore process. See this [issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7796). - BUGFIX: [vmalert](https://docs.victoriametrics.com/victorialogs/vmalert/): do not append tenant info to VictoriaLogs datasource request path in [clusterMode](https://docs.victoriametrics.com/vmalert/#multitenancy). See [this doc](https://docs.victoriametrics.com/victorialogs/vmalert/#how-to-use-multitenancy-in-rules) for how to use multitenancy in VictoriaLogs. - BUGFIX: [vmauth](https://docs.victoriametrics.com/vmauth/): properly set `host` field at debug information formatted with `dump_request_on_errors: true` setting. - BUGFIX: [vmauth](https://docs.victoriametrics.com/vmauth/): properly handle discovery for ipv6 addresses. Thanks to [@&#8203;badie](https://github.com/badie) for the [pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/7955). - BUGFIX: [vmctl](https://docs.victoriametrics.com/vmctl/): fix support for migrating influx series without any tag. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7921). Thanks to [@&#8203;bitbidu](https://github.com/bitbidu) for reporting. - BUGFIX: [vminsert](https://docs.victoriametrics.com/vminsert/): storage nodes defined in `-storageNode` are now sorted, ensuring that varying node orders across different vminsert instances do not result in inconsistent replication. - BUGFIX: [vmsingle](https://docs.victoriametrics.com/single-server-victoriametrics/) and `vminsert` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/cluster-victoriametrics/): properly ingest `influx` line protocol metrics with empty tags. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7933) for details. - BUGFIX: [vmselect](https://docs.victoriametrics.com/cluster-victoriametrics/): allow to override the default unique time series limit in vmstorage with command-line flags like `-search.maxUniqueTimeseries`, `-search.maxLabelsAPISeries`. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7852). - BUGFIX: [vmselect](https://docs.victoriametrics.com/cluster-victoriametrics/): properly set tenancy information when evaluating numbers in a query. Previously, the tenancy information could lead to mismatch between query result and a number. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7987) for the details. - BUGFIX: [vmalert](https://docs.victoriametrics.com/vmalert/): fix marshaling of request body for Alertmanager notification. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7985) for the details. - BUGFIX: [Single-node VictoriaMetrics](https://docs.victoriametrics.com/) and [vmselect](https://docs.victoriametrics.com/cluster-victoriametrics/): don't take into account the last raw sample before the lookbehind window is sample exceeds the staleness interval. This affects correctness of increase, increase_pure, delta functions when preforming calculations on time series with gaps. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/8002) for details. </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:eyJjcmVhdGVkSW5WZXIiOiIzOS45MC4yIiwidXBkYXRlZEluVmVyIjoiMzkuOTAuMiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsicmVub3ZhdGUvY29udGFpbmVyIiwidHlwZS9taW5vciJdfQ==-->
Renovate force-pushed renovate/victoriametrics-victoria-metrics-1.x from d862d7311c to 31bef6b07c 2025-01-17 12:08:44 +00:00 Compare
Renovate changed title from feat(container): update image victoriametrics/victoria-metrics to v1.109.0 to feat(container): update image victoriametrics/victoria-metrics to v1.109.1 2025-01-17 12:08:51 +00:00
SeanOMik merged commit a42f2b8388 into main 2025-01-19 15:21:04 +00:00
SeanOMik deleted branch renovate/victoriametrics-victoria-metrics-1.x 2025-01-19 15:21:04 +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#651
No description provided.