chore(deps): update victoriametrics/victoria-metrics docker tag to v1.109.1 #743
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.108.1
->v1.109.1
Release Notes
VictoriaMetrics/VictoriaMetrics (victoriametrics/victoria-metrics)
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
from30
to100
. This should reduce CPU usage at the cost of slightly higher memory usage. Single-node VictoriaMetrics, vmagent and vmstorage components continue usingGOGC=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 defaultGOGC
value in any VictoriaMetrics component by settingGOGC
environment variable to the desired value. For example,GOGC=200 ./path/to/vmagent
startsvmagent
withGOGC=200
. See these docs aboutGOGC
tuning. See this issue.FEATURE: vmui: add export data functionality for the
Raw Query
page and the ability to import exported data into theQuery 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
andmax
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 flagstorage.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
andALERTS_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 withdump_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 ingestinflux
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.
This PR was generated by Mend Renovate. View the repository job log.