chore(deps): update victoriametrics/victoria-metrics docker tag to v1.110.0

[Fameing]

This PR contains the following updates:

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

---

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/victoria-metrics)

v1.110.0

Compare Source

v1.110.0

Released at 2025-01-24

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

• FEATURE: MetricsQL: allow executing queries with $__interval and $__rate_interval - these placeholders are automatically replaced with 1i (e.g. step arg value at /api/v1/query_range) during query execution. This simplifies copying queries from Grafana dashboards.

• FEATURE: vmsingle and vmselect in VictoriaMetrics cluster: add command-line flag -search.maxDeleteDuration(default 5m) to limit the duration of the /api/v1/admin/tsdb/delete_series call. Previously, the call is limited by -search.maxQueryDuration.

• FEATURE: dashboards: all dashboards that use VictoriaMetrics Grafana datasource were updated to use a new datasource ID.

• FEATURE: vmui: reflect column settings for the table view in URL, so the table view can be shared via link. See this issue.

• BUGFIX: vmsingle, vminsert in VictoriaMetrics cluster and vmagent: allow ingesting histograms with missing _sum metric via OpenTelemetry ingestion protocol in the same way as Prometheus does.

• BUGFIX: Single-node VictoriaMetrics and vmselect: respect staleness detection in increase, increase_pure and delta functions when time series has gaps and -search.maxStalenessInterval is set. See this issue for details.

• BUGFIX: all VictoriaMetrics enterprise components: properly trim whitespaces at the end of license provided via -license and -licenseFile command-line flags. Previously, the trailing whitespaces could cause the license verification to fail.

• BUGFIX: vmauth: fix possible runtime panic during requests processing under heavy load. See this issue for details.

• BUGFIX: vmselect: fix panic when trying to delete series by using multitenant read endpoint. See this issue for the details.

• BUGFIX: vmselect: prevent panic when vmselect receives an error response from vmstorage during the query execution and request processing for other vmstorage nodes is still in progress. See this issue for the details.

• BUGFIX: vmui: fix an issue where pressing the "Enter" key in the query editor did not execute the query. See this issue.

v1.109.1

Compare Source

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 and Alpine 3.21.2 release notes.

• FEATURE: vmsingle, vminsert in VictoriaMetrics cluster and vmagent: log metric names for signals with unsupported delta temporality on ingestion via OpenTelemetry protocol for metrics. Thanks to @​chenlujjj for the pull request.

• BUGFIX: Single-node VictoriaMetrics and vmselect: fix incorrect behavior of increase, increase_pure, delta caused by this pull request. This fix reverts to the previous behavior before v1.109.0. But allows controlling staleness detection for these functions explicitly via -search.maxStalenessInterval.

• BUGFIX: all VictoriaMetrics 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

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 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (145f193) to head (54ebb14).
Report is 7 commits behind head on develop.

Additional details and impacted files

@@               Coverage Diff               @@
##             develop     #2227       +/-   ##
===============================================
+ Coverage      79.89%   100.00%   +20.10%     
+ Complexity       660         7      -653     
===============================================
  Files            199         2      -197     
  Lines           3159        37     -3122     
  Branches         130         0      -130     
===============================================
- Hits            2524        37     -2487     
+ Misses           565         0      -565     
+ Partials          70         0       -70     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.