All Versions
86
Latest Version
Avg Release Cycle
5 days
Latest Release
1294 days ago

Changelog History
Page 3

  • v1.40.1-cluster

    September 03, 2020
  • v1.40.0 Changes

    August 15, 2020

    ๐Ÿ”„ 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.40.0-cluster

    August 15, 2020
  • v1.39.4 Changes

    August 09, 2020

    ๐Ÿ”„ Changes since v1.39.3

    • ๐Ÿ”‹ FEATURE: improve query performance and concurrency on systems with big number of CPU cores (16+ vCPUs).
    • ๐Ÿ”‹ FEATURE: limit the maximum memory usage and reduce CPU trashing on vmstorage when multiple heavy queries are executed. See #648 .
    • ๐Ÿ”‹ FEATURE: improve PromQL compatibility at https://promlabs.com/promql-compliance-test-results-victoriametrics/ . See #673 , #674 , #675
    • FEATURE: vmagent: export scrape_samples_added per-target metric like Prometheus does. This metric may be useful for detecting targets with high churn rate for the exported metrics. See #683
    • ๐Ÿ”‹ FEATURE: vmalert: extend exported metrics. See #573 .
    • ๐Ÿ”‹ FEATURE: vmauth: properly trigger browser auth dialog. See #680
    • ๐Ÿ”‹ FEATURE: slow down concurrent searches when the number of concurrent inserts reaches the limit. This should improve data ingestion performance when heavy searches are executed. See #648 and #618
    • FEATURE: export vm_nfs_pending_dirs_to_remove metric for monitoring the number of pending directories that couldn't be removed due to NFS lock
    • BUGFIX: rename vm_cache_size_entries{type="storage/prefetchedMetricIDs"} to vm_cache_entries{type="storage/prefetchedMetricIDs"} to be consistent with other vm_cache_entries metrics
    • BUGFIX: vmauth: add missing -tls* flags to *-cluster release. See #677

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

    August 09, 2020
  • v1.39.3 Changes

    August 05, 2020

    ๐Ÿ”„ Changes since v1.39.2

    • FEATURE: add MetricsQL functions for calculating z-score over time range and over a group of time series. The following functions are added: zscore_over_time(m[d]) and zscore(q) by (group). They may be used for anomaly detection and alerting. See more details at MetricsQL docs.
    • ๐Ÿ”‹ FEATURE: show X-Forwarded-For contents on /api/v1/status/active_queries page. See #659 .
    • ๐Ÿ”‹ FEATURE: vmbackup, vmrestore: allow using ~/.aws/config without region. Determining bucket region via us-west-2. See vmbackup docs for details.
    • ๐Ÿ”‹ FEATURE: use warning level instead of info level for logging slow queries that take longer than -search.logSlowQueryDuration.
    • ๐Ÿ›  BUGFIX: vmagent: prevent from closing keep-alive connections to remote storage in case -remoteWrite.queues is set to value bigger than 1. See #663 .
    • ๐Ÿ›  BUGFIX: reduce the maximum number of concurrent merge workers to GOMAXPROCS/2. The limit has been raised to GOMAXPROCS in v1.39.2, but it has been appeared that this may increase query latency, because more CPU cores are busy with merges.
    • ๐Ÿ›  BUGFIX: do not adjust start and end query args passed to /api/v1/query_range when -search.disableCache command-line flag is set. See #563 .

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

    August 05, 2020
  • v1.39.2 Changes

    July 30, 2020

    ๐Ÿ”„ Changes since v1.39.1

    • ๐Ÿ”‹ FEATURE: vmalert: add -external.label command-line flag to specify global labelset for all rules. This flag supposed to help to distinguish the source of alert or recording rules when more than one vmalert runs for the same datasource or AlertManager. See #622
    • โž• FEATURE: show query origin (aka remote_addr or client address) on the /api/v1/status/active_queries page for every query.
    • ๐Ÿ”‹ FEATURE: add X-Forwarded-For header value to remoteAddr in error logs. See #659
    • ๐Ÿ›  BUGFIX: do not prioritize merging of small parts over merging of big parts, since this doesn't work as expected. The prioritizing could lead to starvation for big part merges, which could end up in too big number of parts that must be merged into big parts.
      Note : multiple big merges may be initiated after the migration from v1.39.0 or v1.39.1 to v1.39.2 or newer releases. It is OK - these merges should be finished soon. After that CPU load and disk IO usage should return to normal levels. See #648 and #618
    • ๐Ÿ›  BUGFIX: vmagent: add missing resp.Body.Close() call after pushing data to remote storage. Missing body close could disable HTTP keep-alive connections, which could lead to higher load on re-establishing connections to remote storage after each request to it. See #653
    • ๐Ÿ›  BUGFIX: vmalert,vminsert: properly preserve db tag from query string passed to Influx line protocol query. Previously db tag from the query string wasn't added to metrics after encountering db tag in the Influx line. See #653
    • ๐Ÿ›  BUGFIX: return empty values instead of 1 from group() if all the time series in the group have no values at the given timestamp. This aligns group() behaviour to Prometheus.
    • BUGFIX: improve rate_over_sum(m[d]) handling for cases when m contains zero or one data point on the time range d.
    • BUGFIX: properly update vm_slow_row_inserts_total metric when importing multiple data points per time series at once. Previously the vm_slow_row_inserts_total metric could be incremented multiple times for different data points per a single time series, while only a single increment is needed when inserting the first data point for this time series.

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

    July 30, 2020
  • v1.34.3 Changes

    March 11, 2020

    ๐Ÿ”„ Changes since v1.34.2

    • ๐Ÿ›  BUGFIX: properly add labels set via -remoteWrite.label to metrics before sending them to -remoteWrite.url. This has been broken in v1.34.2
    • ๐Ÿ›  BUGFIX: do not retry idempotent requests when scraping targets. See #357
    • ๐Ÿ›  BUGFIX: properly apply -remoteWrite.sendTimeout to fasthttp.HostClient
    • ๐Ÿ›  BUGFIX: return 500 status code instead of 200 status code on internal errors inside /snapshot/* handlers
    • โœจ ENHANCEMENT: vmagent,vminsert: add support for importing csv data via /api/v1/import/csv. See https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/README.md#how-to-import-csv-data
    • ENHANCEMENT: add optional max_rows_per_line query arg to /api/v1/export for limiting the number of data points that may be exported on a single line
    • ENHANCEMENT: do not allow non-supported fields in -remoteWrite.relabelConfig and file_sd_configs. See #363
    • โœจ ENHANCEMENT: vmagent: consistently update /targets page after SIGHUP
    • โœจ ENHANCEMENT: Makefile: add build and test rules with enabled race detector. These rules have -race suffix.

    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.