VictoriaMetrics v1.46.0 Release Notes

Release Date: 2020-11-07 // over 3 years ago
  • ๐Ÿ”„ 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.