Skip to content

chore(deps): update victoriametrics/victoria-logs docker tag to v1.47.0#5360

Open
gardener-ci-robot wants to merge 1 commit intomasterfrom
renovate/victoriametrics-victoria-logs-1.x
Open

chore(deps): update victoriametrics/victoria-logs docker tag to v1.47.0#5360
gardener-ci-robot wants to merge 1 commit intomasterfrom
renovate/victoriametrics-victoria-logs-1.x

Conversation

@gardener-ci-robot
Copy link
Collaborator

@gardener-ci-robot gardener-ci-robot commented Feb 9, 2026 •
edited
Loading

This PR contains the following updates:

Package Update Change
victoriametrics/victoria-logs minor v1.37.2 → v1.47.0

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/victoria-logs)

v1.47.0

Compare Source

Changes since v1.46.0

  • FEATURE: vmselect: return the original error from vmstorage node in query response if -search.denyPartialResponse is set. See #​891

  • FEATURE: vmselect: add "isPartial":{true|false} field in JSON output for /api/v1/* functions from Prometheus querying API. "isPartial":true is set if the response contains partial data because of a part of vmstorage nodes were unavailable during query processing.

  • FEATURE: improve performance for /api/v1/series, /api/v1/labels and /api/v1/label/<labelName>/values on time ranges exceeding one day.

  • FEATURE: vmagent: reduce memory usage when service discovery detects big number of scrape targets and the set of discovered targets changes over time. See #​825

  • FEATURE: vmagent: add -promscrape.dropOriginalLabels command-line option, which can be used for reducing memory usage when scraping big number of targets. See #​825 (comment) for details.

  • FEATURE: vmalert: explicitly set extra labels to alert entities. See #​870

  • FEATURE: add -search.treatDotsAsIsInRegexps command-line flag, which can be used for automatic escaping of dots in regexp label filters used in queries. For example, if -search.treatDotsAsIsInRegexps is set, then the query foo{bar=~"aaa.bb.cc|dd.eee"} is automatically converted to foo{bar=~"aaa\\.bb\\.cc|dd\\.eee"}. This may be useful for querying Graphite metrics.

  • FEATURE: consistently return text-based HTTP responses such as plain/text and application/json with charset=utf-8. See #​897

  • FEATURE: update Go builder from v1.15.4 to v1.15.5. This should fix these issues in Go.

  • FEATURE: added /internal/force_flush http handler for flushing recently ingested data from in-memory buffers to persistent storage. See troubleshooting docs for more details.

  • FEATURE: added Graphite Tags API support. See these docs for details.

  • BUGFIX: do not return data points in the end of the selected time range for time series ending in the middle of the selected time range. See #​887 and #​845

  • BUGFIX: remove spikes at the end of time series gaps for increase() or delta() functions. See #​894

  • BUGFIX: vminsert: properly return HTTP 503 status code when all the vmstorage nodes are unavailable. See #​896

How to run VictoriaMetrics

Unpack the victoria-metrics-*.tar.gz archive and read these docs.

vmutils-*.tag.gz archive contains the following tools:

The corresponding docker images are available here.
Cluster version is available here.

vmctl releases are available here.

v1.46.0

Compare Source

Changes since v1.45.0

  • FEATURE: optimize requests to /api/v1/labels and /api/v1/label/<name>/values when start and end args are set.

  • FEATURE: reduce memory usage when query touches big number of time series.

  • FEATURE: vmagent: reduce memory usage when kubernetes_sd_config discovers big number of scrape targets (e.g. hundreds of thouthands) and the majority of these targets (99%) are dropped during relabeling. Previously labels for all the dropped targets were displayed at /api/v1/targets page. Now only up to -promscrape.maxDroppedTargets such targets are displayed. See #​878 for details.

  • FEATURE: vmagent: reduce memory usage when scraping big number of targets with big number of temporary labels starting with __. See #​825

  • FEATURE: vmagent: add /ready HTTP endpoint, which returns 200 OK status code when all the service discovery has been initialized. This may be useful during rolling upgrades. See #​875

  • BUGFIX: vmagent: eliminate data race when -promscrape.streamParse command-line is set. Previously this mode could result in scraped metrics with garbage labels. See #​825 (comment) for details.

  • BUGFIX: properly calculate topk_* and bottomk_* functions from MetricsQL for time series with gaps. See #​883

How to run VictoriaMetrics

Unpack the victoria-metrics-*.tar.gz archive and read these docs.

vmutils-*.tag.gz archive contains the following tools:

The corresponding docker images are available here.
Cluster version is available here.

vmctl releases are available here.

v1.45.0

Compare Source

Changes since v1.44.0

  • FEATURE: allow setting -retentionPeriod smaller than one month. I.e. -retentionPeriod=3d, -retentionPeriod=2w, etc. is supported now. See #​173

  • FEATURE: optimize more cases according to https://utcc.utoronto.ca/~cks/space/blog/sysadmin/PrometheusLabelNonOptimization . Now the following cases are optimized too:

    • rollup_func(foo{filters}[d]) op bar -> rollup_func(foo{filters}[d]) op bar{filters}
    • transform_func(foo{filters}) op bar -> transform_func(foo{filters}) op bar{filters}
    • num_or_scalar op foo{filters} op bar -> num_or_scalar op foo{filters} op bar{filters}

  • FEATURE: improve time series search for queries with multiple label filters. I.e. foo{label1="value", label2=~"regexp"}. See #​781

  • FEATURE: vmagent: add stream parse mode. This mode allows reducing memory usage when individual scrape targets expose tens of millions of metrics. For example, during scraping Prometheus in federation mode. See -promscrape.streamParse command-line option and stream_parse: true config option for scrape_config section in -promscrape.config. See #​825 and troubleshooting docs for vmagent.

  • FEATURE: vmalert: add -dryRun command-line option for validating the provided config files without the need to start vmalert service.

  • FEATURE: accept optional third argument of string type at topk_* and bottomk_* functions. This is label name for additional time series to return with the sum of time series outside top/bottom K. See MetricsQL docs for more details.

  • FEATURE: vmagent: expose /api/v1/targets page according to the corresponding Prometheus API. See #​643

  • BUGFIX: vmagent: properly handle OpenStack endpoint ending with v3.0 such as https://ostack.example.com:5000/v3.0 in the same way as Prometheus does. See #​728 (comment)

  • BUGFIX: drop trailing data points for time series with a single raw sample. See #​748

  • BUGFIX: do not drop trailing data points for instant queries to /api/v1/query. See #​845

  • BUGFIX: vmbackup: fix panic when -origin isn't specified. See #​856

  • BUGFIX: vmalert: skip automatically added labels on alerts restore. Label alertgroup was introduced in this issue and automatically added to generated time series. By mistake, this new label wasn't correctly purged on restore event and affected alert's ID uniqueness. See #​870

  • BUGFIX: vmagent: fix panic at scrape error body formating. See #​864

  • BUGFIX: vmagent: add leading missing slash to metrics path like Prometheus does. See #​835

  • BUGFIX: vmagent: drop packet if remote storage returns 4xx status code. This make the behaviour consistent with Prometheus.
    See #​873

  • BUGFIX: vmagent: properly handle 301 redirects. See #​869

How to run VictoriaMetrics

Unpack the victoria-metrics-*.tar.gz archive and read these docs.

vmutils-*.tag.gz archive contains the following tools:

The corresponding docker images are available here.
Cluster version is available here.

vmctl releases are available here.

v1.44.0

Changes since v1.43.0

  • FEATURE: automatically add missing label filters to binary operands as described at https://utcc.utoronto.ca/~cks/space/blog/sysadmin/PrometheusLabelNonOptimization . This should improve performance for queries with missing label filters in binary operands. For example, the following query should work faster now, because it shouldn't fetch and discard time series for node_filesystem_files_free metric without matching labels for the left side of the expression:

       node_filesystem_files{ host="$host", mountpoint="/" } - node_filesystem_files_free

  • FEATURE: vmagent: add Docker Swarm service discovery (aka dockerswarm_sd_config). See #​656

  • FEATURE: add ability to export data in CSV format. See these docs for details.

  • FEATURE: vmagent: add -promscrape.suppressDuplicateScrapeTargetErrors command-line flag for suppressing duplicate scrape target errors. See #​651 and https://victoriametrics.github.io/vmagent.html#troubleshooting .

  • FEATURE: vmagent: show original labels before relabeling is applied on duplicate scrape target errors. This should simplify debugging for incorrect relabeling. See #​651

  • FEATURE: vmagent: /targets page now accepts optional show_original_labels=1 query arg for displaying original labels for each target before relabeling is applied. This should simplify debugging for target relabeling configs. See #​651

  • FEATURE: add -finalMergeDelay command-line flag for configuring the delay before final merge for per-month partitions. The final merge is started after no new data is ingested into per-month partition during -finalMergeDelay.

  • FEATURE: add vm_rows_added_to_storage_total metric, which shows the total number of rows added to storage since app start. The sum(rate(vm_rows_added_to_storage_total)) can be smaller than sum(rate(vm_rows_inserted_total)) if certain metrics are dropped due to relabeling. The sum(rate(vm_rows_added_to_storage_total)) can be bigger than sum(rate(vm_rows_inserted_total)) if replication is enabled.

  • FEATURE: keep metric name after applying MetricsQL functions, which don't change time series meaning. The list of such functions:

    • keep_last_value
    • keep_next_value
    • interpolate
    • running_min
    • running_max
    • running_avg
    • range_min
    • range_max
    • range_avg
    • range_first
    • range_last
    • range_quantile
    • smooth_exponential
    • ceil
    • floor
    • round
    • clamp_min
    • clamp_max
    • max_over_time
    • min_over_time
    • avg_over_time
    • quantile_over_time
    • mode_over_time
    • geomean_over_time
    • holt_winters
    • predict_linear
      See #​674

  • BUGFIX: properly handle stale time series after K8S deployment. Previously such time series could be double-counted. See #​748

  • BUGFIX: return a single time series at max from absent() function like Prometheus does.

  • BUGFIX: vmalert: accept days, weeks and years in for: part of config like Prometheus does. See #​817

  • BUGFIX: fix mode_over_time(m[d]) calculations. Previously the function could return incorrect results.

How to run VictoriaMetrics

Unpack the victoria-metrics-*.tar.gz archive and read these docs.

vmutils-*.tag.gz archive contains the following tools:

The corresponding docker images are available here.
Cluster version is available here.

vmctl releases are available here.

v1.43.0

Compare Source

Changes since v1.42.0

  • FEATURE: reduce CPU usage for repeated queries over sliding time window when no new time series are added to the database.
    Typical use cases: repeated evaluation of alerting rules in vmalert or dashboard auto-refresh in Grafana.

  • FEATURE: vmagent: add OpenStack service discovery aka openstack_sd_config. See #​728

  • FEATURE: vmalert: make -maxIdleConnections configurable for datasource HTTP client. This option can be used for minimizing connection churn.
    See #​795 .

  • FEATURE: add -influx.maxLineSize command-line flag for configuring the maximum size for a single Influx line during parsing.
    See #​807

  • BUGFIX: properly handle inf values during background merge of LSM parts.
    Previously Inf values could result in NaN values for adjancent samples in time series. See #​805 .

  • BUGFIX: fill gaps on graphs for range_* and running_* functions. See #​806 .

  • BUGFIX: make a copy of label with new name during relabeling with action: labelmap in the same way as Prometheus does.
    Previously the original label name has been replaced. See #​812 .

  • BUGFIX: support parsing floating-point timestamp like Graphite Carbon does. Such timestmaps are truncated to seconds.

How to run VictoriaMetrics

Unpack the victoria-metrics-*.tar.gz archive and read these docs.

vmutils-*.tag.gz archive contains the following tools:

The corresponding docker images are available here.
Cluster version is available here.

vmctl releases are available here.

v1.42.0

Compare Source

Changes since v1.41.1

  • FEATURE: use all the available CPU cores when accepting data via a single TCP connection for all the supported protocols. Previously data ingested via a single TCP connection could use only a single CPU core. This could limit data ingestion performance. The main benefit of this feature is that data can be imported at max speed via a single connection - there is no need to open multiple concurrent connections to VictoriaMetrics or vmagent in order to achieve the maximum data ingestion speed.

  • FEATURE: cluster: improve performance for data ingestion path from vminsert to vmstorage nodes. The maximum data ingestion performance for a single connection between vminsert and vmstorage node scales with the number of available CPU cores on vmstorage side. This should help with #​791 .

  • FEATURE: add ability to export / import data in native format via /api/v1/export/native and /api/v1/import/native. This is the most optimized approach for data migration between VictoriaMetrics instances. Both single-node and cluster instances are supported. See #​787 (comment) .

  • FEATURE: add reduce_mem_usage query option to /api/v1/export in order to reduce memory usage during data export / import. See these docs for details.

  • FEATURE: improve performance for /api/v1/series handler when it returns big number of time series.

  • FEATURE: add vm_merge_need_free_disk_space metric, which can be used for estimating the number of deferred background data merges due to the lack of free disk space. See #​686 .

  • FEATURE: add OpenBSD support. See #​785 .

  • BUGFIX: properly apply -search.maxStalenessInterval command-line flag value. See #​784 .

  • BUGFIX: fix displaying data in Grafana tables. See #​720 .

  • BUGFIX: do not adjust the number of detected CPU cores found at /sys/devices/system/cpu/online. The adjustment was increasing the resulting GOMAXPROC by 1, which looked confusing to users. See #​685 (comment) .

  • BUGFIX: vmagent: do not show -remoteWrite.url in initial logs if -remoteWrite.showURL isn't set. See #​773 .

  • BUGFIX: properly handle case when /metrics/find finds both a leaf and a node for the given query=prefix.*. In this case only the node must be returned with stripped dot in the end of id as carbonapi does.

How to run VictoriaMetrics

Unpack the victoria-metrics-*.tar.gz archive and read these docs.

vmutils-*.tag.gz archive contains the following tools:

The corresponding docker images are available here.
Cluster version is available here.

vmctl releases are available here.

v1.41.1

Compare Source

Changes since v1.41.0
  • FEATURE: add /internal/force_merge handler for running forced compactions on historical per-month partitions. This may be useful for freeing up storage space after time series deletion. See https://victoriametrics.github.io/#forced-merge for more details.
  • FEATURE: reduce memory usage when querying time series with big number of samples in each series.
  • FEATURE: optimize searching for time series via regexp label filters. See #​781
  • FEATURE: vmagent: reduce memory usage when scraping targets with millions of metrics
  • FEATURE: vmagent: add support for role_arn and instance IAM tokens in EC2 service discovery. See #​771
  • FEATURE: vmagent: make persistent queue more durable after unclean shutdown (kill -9, OOM, hard reset). See #​687
  • FEATURE: vmagent: substitute -remoteWrite.url with secret-url value in logs, since it may contain sensitive info such as passwords or auth tokens. Pass -remoteWrite.showURL command-line flag in order to see real -remoteWrite.url in logs and at /metrics page. See #​773
  • FEATURE: vmagent: protect from concurrent access to the same -remoteWrite.tmpDataPath from multiple vmagent instances. Previously this could lead to data corruption.
  • FEATURE: vmalert: add support for datasource.lookback flag, which defines how far to look into the past when evaluating queries. See #​668
  • FEATURE: add -loggerDisableTimestamps command-line flag for disabling timestamps in logs. See #​778
  • FEATURE: attempt to obtain available CPU cores via /sys/devices/system/cpu/online. See #​685 (comment)
  • BUGFIX: release occupied resources on query timeouts in single-node VictoriaMetrics. Previously there was resource leak, which could lead to many open files. See #​716
  • BUGFIX: return proper results from /metrics/find?query=foo.*.bar according to Graphite Metrics API
  • BUGFIX: properly parse +Inf values during data ingestion via text-based protocols (Graphite, Influx, OpenTSDB, JSON). Previously such values were silently converted to 0. See VictoriaMetrics/vmctl#25
  • BUGFIX: log errors when timestamps or values cannot be parsed during data ingestion via text-based protocols. Previously such values were silently converted to 0. See #​99
  • BUGFIX: use time value rounded to seconds if it isn't passed to /api/v1/query. This fixes table results in Grafana. See #​720
How to run VictoriaMetrics

Unpack the victoria-metrics-*.tar.gz archive and read these docs.

vmutils-*.tag.gz archive contains the following tools:

The corresponding docker images are available here.
Cluster version is available here.

vmctl releases are available here.

v1.41.0

Compare Source

Changes since v1.40.1
  • FEATURE: reuse timestamp blocks for adjancent metric blocks with identical timestamps. This reduces disk space usage when scraping targets containing metrics with identical names such as node_cpu_seconds_total, histograms, quantiles, etc. Important: this changes on-disk data format. This makes impossible downgrading to releases below v1.41.0. These releases may panic with the following error after downgrading: 
           cannot read next block: invalid TimestampsBlockOffset at block header at offset ...
  • FEATURE: initial implementation of Graphite Metrics API - see these docs.
  • FEATURE: vmagent: add endpointslices discovery type to kubernetes_sd_config. This is similar to prometheus/prometheus#6838 , which has been added in Prometheus v2.21. See https://github.com/prometheus/prometheus/releases/tag/v2.21.0
  • FEATURE: vmagent: add __meta_dns_srv_record_target and __meta_dns_srv_record_port labels to dns_sd_config. This syncs dns service discovery with Prometheus 2.21 - see https://github.com/prometheus/prometheus/releases/tag/v2.21.0 and prometheus/prometheus#7678
  • FEATURE: vmagent: allow setting multiple identical -remoteWrite.url values. This may be useful when each url is authenticated via different -remoteWrite.basicAuth.username. See #​755
  • FEATURE: vmalert: update groups on config reload only if changes detected. This should speed up config reload for big number of groups when only a small part of these groups are updated. See #​691
  • FEATURE: vmalert: add Group name as label to generated alerts and timeseries. See #​611
  • FEATURE: support composite durations like Prometheus 2.21 does. The following durations are supported now: 1h5m35s or 1s543ms. See https://github.com/prometheus/prometheus/releases/tag/v2.21.0 and prometheus/prometheus#7713
  • FEATURE: add a jitter to -http.connTimeout in order to protect from Thundering herd problem when many connections are re-established at the same time.
  • FEATURE: allow passing timestamp via timestamp query arg when ingesting data at /api/v1/import/prometheus. See these docs. See #​750
  • FEATURE: update Go builder from v1.15.1 to v1.15.2. This fixes the following issues in Go runtime: https://github.com/golang/go/issues?q=milestone%3AGo1.15.2+label%3ACherryPickApproved
  • BUGFIX: vmagent: do not reset the remaining rows when pushing a part of data to remote storage during big scrapes. See #​753
  • BUGFIX: vmbackup, vmrestore: do not set AWS config profile to default by default, since it may break default AWS auth mechanism. See #​726
  • BUGFIX: do not store inf values, since they may lead to significant precision loss for previously stored values. See #​752
  • BUGFIX: skip infinite values when calculating smooth_exponential() function from MetricsQL. This should help with missing results in ttf() function. See #​757
  • BUGFIX: adjust integrate() calculations to be more similar to calculations from InfluxDB. See #​701
How to run VictoriaMetrics

Unpack the victoria-metrics-*.tar.gz archive and read these docs.

vmutils-*.tag.gz archive contains the following tools:

The corresponding docker images are available here.
Cluster version is available here.

v1.40.0

Compare Source

Changes since v1.39.4
  • FEATURE: release Kubernetes operator for VictoriaMetrics - see https://github.com/VictoriaMetrics/operator .
  • FEATURE: respect CPU limits set via cgroups. This should reduce CPU trashing and reduce memory usage for cases when VictoriaMetrics components run in containers (Docker, Kubernetes) with CPU limits. See #​685 .
  • FEATURE: support %{ENV_VAR} placeholders in yaml configs in all the vm* components. Such placeholders are substituted by the corresponding environment variable values. See #​583 .
  • FEATURE: vmagent: reduce memory usage when scraping big number of targets. Thanks to @​dxtrzhang for the original idea at #​688 . See #​689 .
  • FEATURE: reduce memory usage when exporting time series with big number of samples via /api/v1/export if max_rows_per_line is set to non-zero value. See #​685 .
  • FEATURE: add -memory.allowedBytes command-line flag for setting absolute memory limit for VictoriaMetrics caches.
  • FEATURE: allow passing multiple args to aggregate functions such as avg(q1, q2, q3). See MetricsQL docs for details.
  • FEATURE: update Go builder from Go1.14.7 to Go1.15.0.
  • BUGFIX: vmagent, vminsert: prevent from busy loop on repeated timeout errors when reading streams of ingested data. See #​696 .
  • BUGFIX: vmagent, vminsert: accept precision=us and precision=µ query args according to https://docs.influxdata.com/influxdb/v1.8/tools/api/#write-http-endpoint .
  • BUGFIX: vmagent: show real timestamp and real scrape duration on /targets page. Previously the scrape duration could be negative when calculated scrape timestamp drifts away from the real scrape timestamp.
  • BUGFIX: vmagent: properly retry requests on the server closed connection before returning the first response byte error during service discovery API calls and target scrapes.
How to run VictoriaMetrics

Unpack the victoria-metrics-*.tar.gz archive and read these docs.

vmutils-*.tag.gz archive contains the following tools:

The corresponding docker images are available here.
Cluster version is available here.

v1.39.0

Compare Source

Changes since v1.38.1

  • FEATURE: improve prioritizing of data ingestion over querying. This means that heavy queries shouldn't slow down data ingestion. See #​291 and #​648 .

  • FEATURE: respect -search.maxQueryDuration when searching for time series matching the given label filters. Previously the time spent on inverted index search could exceed the configured -search.maxQueryDuration.
    Note: this change modifies communication protocol between vmselect and vmstorage in cluster version of VictoriaMetrics in incompatible way. This is needed for propagating the deadline from vmselect to vmstorage. So vmselect prior v1.39.0 cannot talk to vmstorage v1.39.0 and higher. The same applies for vmselect v1.39.0 or higher and vmstorage prior to v1.39.0 - they also cannot communicate with each other. So all the vmselect and vmstorage nodes must be updated to v1.39.0 or higher in order to work properly.

  • FEATURE: optimize performance for queries with label filters touching big number of time series.

  • FEATURE: reduce memory usage for heavy queries touching big number of time series with long labels. See #​646 .

  • FEATURE: add group() aggregate function to MetricsQL. This function has been added in Prometheus 2.20. See prometheus/prometheus#7480 .

  • FEATURE: add rate_over_sum(m[d]) function to MetricsQL, which returns rate over sum of m values over d duration. Something like sum_over_time(m[d]) / d, but more accurate.

  • FEATURE: add mode_over_time(m[d]) function to MetricsQL. See https://en.wikipedia.org/wiki/Mode_(statistics) and https://stackoverflow.com/questions/61134078/promql-query-to-return-the-value-from-a-range-vector-which-occurs-maximum-no-of .

  • FEATURE: add mode() aggregate function. See MetricsQL docs for details.

  • FEATURE: add buckets_limit(k, buckets) function, which limits the number of buckets per time series to k. This function works with both Prometheus-style and VictoriaMetrics-style buckets. The function removes buckets with the lowest hits in order to preserve the highest accuracy. The function is useful for building heatmaps in Grafana from too big number of buckets. See https://medium.com/@​valyala/improving-histogram-usability-for-prometheus-and-grafana-bc7e5df0e350 for details.

  • FEATURE: add Grafana dashboard for vmagent. See https://victoriametrics.github.io/vmagent.html#monitoring .

  • FEATURE: update Go runtime from v1.14.4 to v1.14.6 . See https://github.com/golang/go/issues?q=milestone%3AGo1.14.6+label%3ACherryPickApproved and https://github.com/golang/go/issues?q=milestone%3AGo1.14.5+label%3ACherryPickApproved for a list of fixed issues in Go runtime.

  • FEATURE: keep all labels for time series from any() aggregate function. This improves usability for any(q) by (...) results. See https://victoriametrics.github.io/MetricsQL.html .

  • FEATURE: vmagent: add -remoteWrite.proxyURL command-line option. This option allows writing data to -remoteWrite.url via http, https or socks5 proxy. This is similar to proxy_url option in remote_write section of Prometheus. See https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remote_write

  • FEATURE: vmagent: add -remoteWrite.decimalPlaces command-line flag, which may be used for reducing disk space usage on the remote storage.

  • FEATURE: log remote address in error message from httpserver.Errorf. This should improve detection of the root cause of errors.

  • FEATURE: log the total available memory for concurrent requests on not enough memory errors. This should simplify root cause analysis.

  • FEATURE: take into account the time spent in wait queue before query execution as time spent on the query.

  • FEATURE: export vm_relabel_metrics_dropped_total metric that shows the number of metrics dropped due to relabeling.

  • BUGFIX: fix relabeling for metrics ingested via Influx line protocol. Previously the enabled relabeling with -relabelConfig command-line flag could result in missing labels if a single Influx line protocol message contains multiple field values. See #​638 .

  • BUGFIX: support d, w and y suffixes for durations passed to step in /api/v1/query_range like Prometheus does. See #​641

  • BUGFIX: do not return time series with empty list of datapoints from /api/v1/query_range. This should fix issue in Promxy. See jacksontj/promxy#329 .

  • BUGFIX: fix nil pointer dereference panic when unsuccessfully querying vmstorage.

  • BUGFIX: skip the first value in time series passed to increase() if it exceeds by more than 10x the delta between the next value and the first value. his should prevent from inflated increase() results for time series that start from big initial values. Such cases may occur when a label value changes in a metric without counter reset.

  • BUGFIX: properly calculate vm_cache_requests_total and vm_cache_misses_total metrics. Previously they could be inflated by multiple times.

  • BUGFIX: allow setting [d] window smaller than the interval between raw points for avg_over_time() function. This makes avg_over_time behavior consistent with sum_over_time and count_over_time behaviors. See #​636 .

  • BUGFIX: vmagent: allow passing empty -remoteWrite.urlRelabelConfig entries when multiple -remoteWrite.url flags are set.

How to run VictoriaMetrics

Unpack the victoria-metrics-*.tar.gz archive and read these docs.

vmutils-*.tag.gz archive contains the following tools:

The corresponding docker images are available here.
Cluster version is available here.

v1.38.0

Compare Source

Changes since v1.37.4
  • FEATURE: add ability to apply relabeling to all the incoming metrics if -relabelConfig command-line arg points to a file with a list of relabel_config entries. See https://victoriametrics.github.io/#relabeling
  • FEATURE: add /api/v1/status/active_queries page with the list of currently running queries. See #​528 .
  • FEATURE: add interpolate function to MetricsQL for filling gaps with linearly interpolated values.
  • FEATURE: add ability to set disable_compression and disable_keepalive options on a per-scrape_config basis. See #​580
  • FEATURE: prioritize data ingestion over heavy queries. Heavy queries could result in the lack of CPU resources for processing the current data ingestion stream. Prevent this by delaying queries' execution until free resources are available for data ingestion. Expose vm_search_delays_total metric, which may be used in for alerting when there is no enough CPU resources for data ingestion and/or for executing heavy queries. See #​291
  • FEATURE: improve data ingestion performance after using delete API. See #​596 .
  • BUGFIX: properly accept -1 timestamp in Graphite plaintext protocol. See #​610
  • BUGFIX: vmagent: send Accept header similar to Prometheus when scraping targets. This should fix scraping Spring Boot servers, which return incorrect response unless Accept: text/plain request header is set. See #​608
  • BUGFIX: vmagent: prevent from timeout misses on scrape retries, which could result in irregular scrape intervals.
  • BUGFIX: prevent from adding and/or selecting labels with empty values. See #​600
  • BUGFIX: improve adjustements for the last points on the graph. See #​606
  • BUGFIX: vmalert: Fix error log when remoteWrite queue size is full. See #​602
  • BUGFIX: vmalert: add retries to remotewrite. Remotewrite pkg now does limited number of retries if write request failed. This suppose to make vmalert state persisting more reliable. See #​605
  • BUGFIX: removed debug log message when -selfScrapeInterval is set
How to run VictoriaMetrics

Unpack the victoria-metrics-*.tar.gz archive and read these docs.

vmutils-*.tag.gz archive contains the following tools:

The corresponding docker images are available here.
Cluster version is available here.

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.

@gardener-ci-robot gardener-ci-robot added the kind/enhancement Enhancement, improvement, extension label Feb 9, 2026
@gardener-prow
Copy link

gardener-prow bot commented Feb 9, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign marc1404 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gardener-prow gardener-prow bot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. labels Feb 9, 2026
@gardener-ci-robot gardener-ci-robot force-pushed the renovate/victoriametrics-victoria-logs-1.x branch from bf050bc to df7b1e5 Compare February 12, 2026 15:33
@gardener-ci-robot gardener-ci-robot force-pushed the renovate/victoriametrics-victoria-logs-1.x branch from df7b1e5 to 4cfecde Compare February 23, 2026 13:34
@gardener-ci-robot gardener-ci-robot changed the title chore(deps): update victoriametrics/victoria-logs docker tag to v1.45.0 chore(deps): update victoriametrics/victoria-logs docker tag to v1.46.0 Feb 23, 2026
@gardener-ci-robot gardener-ci-robot force-pushed the renovate/victoriametrics-victoria-logs-1.x branch from 4cfecde to 8e7704b Compare February 25, 2026 22:40
@gardener-ci-robot gardener-ci-robot changed the title chore(deps): update victoriametrics/victoria-logs docker tag to v1.46.0 chore(deps): update victoriametrics/victoria-logs docker tag to v1.47.0 Feb 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. kind/enhancement Enhancement, improvement, extension size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@gardener-ci-robot