AverageMarcus/cluster.fun
1
0
Fork 0
Code Issues 1 Pull Requests 2 Releases Activity

Update victoriametrics/vmagent Docker tag to v1.94.0 #106

Merged
AverageMarcus merged 1 commits from renovate/victoriametrics-vmagent-1.x into master 2023-10-03 07:07:11 +00:00
Conversation 0 Commits 1 Files Changed 2 +2 -2
renovate commented 2023-10-03 00:02:07 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
victoriametrics/vmagent minor v1.93.5 -> v1.94.0

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)

v1.94.0

Compare Source

Released at 2023-10-02

  • FEATURE: MetricsQL: add support for numbers with underscore delimiters such as 1_234_567_890 and 1.234_567_890. These numbers are easier to read than 1234567890 and 1.234567890.

  • FEATURE: vmbackup: add support for server-side copy of existing backups. See these docs for details.

  • FEATURE: vmui: add the option to see the latest 25 queries. See this issue.

  • FEATURE: vmagent: add ability to set member num label for all the metrics scraped by a particular vmagent instance in a cluster of vmagents via -promscrape.cluster.memberLabel command-line flag. See these docs and this issue.

  • FEATURE: vmagent: do not log unexpected EOF when reading incoming metrics, since this error is expected and is handled during metrics' parsing. This reduces the amounts of noisy logs. See this issue.

  • FEATURE: vmagent: retry failed write request on the closed connection immediately, without waiting for backoff. This should improve data delivery speed and reduce amount of error logs emitted by vmagent when using idle connections. See related issue.

  • FEATURE: vmagent: reduces load on Kubernetes control plane during initial service discovery. See this issue for details.

  • FEATURE: VictoriaMetrics cluster: reduce the maximum recovery time at vmselect and vminsert when some of vmstorage nodes become unavailable because of networking issues from 60 seconds to 3 seconds by default. The recovery time can be tuned at vmselect and vminsert nodes with -vmstorageUserTimeout command-line flag if needed. Thanks to @​wjordan for the pull request.

  • FEATURE: vmui: add Prometheus data support to the "Explore cardinality" page. See this issue for details.

  • FEATURE: vmui: make the warning message more noticeable for text fields. See this issue.

  • FEATURE: vmui: add button for auto-formatting PromQL/MetricsQL queries. See this issue. Thanks to @​aramattamara for the pull request.

  • FEATURE: vmui: improve accessibility score to 100 according to Google's Lighthouse tests.

  • FEATURE: vmui: organize min, max, median values on the chart legend and tooltips for better visibility.

  • FEATURE: vmui: add explanation about cardinality explorer statistic inaccuracy in VictoriaMetrics cluster. See this issue.

  • FEATURE: vmui: add storage of query history in localStorage. See the pull request.

  • FEATURE: dashboards: provide copies of Grafana dashboards alternated with VictoriaMetrics datasource at dashboards/vm.

  • FEATURE: vmauth: added ability to set, override and clear request and response headers on a per-user and per-path basis. See this issue and these docs for details.

  • FEATURE: vmauth: add ability to retry requests to the remaining backends if they return response status codes specified in the retry_status_codes list. See this feature request.

  • FEATURE: vmauth: expose metrics vmauth_config_last_reload_* for tracking the state of config reloads, similarly to vmagent/vmalert components.

  • FEATURE: vmauth: do not print logs like SIGHUP received... once per configured -configCheckInterval cmd-line flag. This log will be printed only if config reload was invoked manually.

  • FEATURE: vmalert: add eval_offset attribute for Groups. If specified, Group will be evaluated at the exact time offset on the range of [0...evaluationInterval]. The setting might be useful for cron-like rules which must be evaluated at specific moments of time. See this issue for details.

  • FEATURE: vmalert: validate MetricsQL function names in alerting and recording rules when vmalert runs with -dryRun command-line flag. Previously it was allowed to use unknown (aka invalid) MetricsQL function names there. For example, foo() was counted as a valid query. See this feature request.

  • FEATURE: limit the length of string params in log messages to 500 chars. Longer string params are replaced with the first_250_chars..last_250_chars. This prevents from too long log lines, which can be emitted by VictoriaMetrics components.

  • FEATURE: docker compose environment: add vmauth component to cluster's docker-compose example for balancing load among multiple vmselect components.

  • FEATURE: MetricsQL: make sure that q2 series are returned after q1 series in the results of q1 or q2 query, in the same way as Prometheus does. See this issue.

  • FEATURE: MetricsQL: return empty result from bitmap_and(a, b), bitmap_or(a, b) and bitmap_xor(a, b) if a or b have no value at the particular timestamp. Previously 0 was returned in this case. See this issue.

  • FEATURE: stop exposing vm_merge_need_free_disk_space metric, since it has been appeared that it confuses users while doesn't bring any useful information. See this comment.

  • BUGFIX: Official Grafana dashboards for VictoriaMetrics: fix display of ingested rows rate for Samples ingested/s and Samples rate panels for vmagent's dasbhoard. Previously, not all ingested protocols were accounted in these panels. An extra panel Rows rate was added to Ingestion section to display the split for rows ingested rate by protocol.

  • BUGFIX: vmui: fix the bug causing render looping when switching to heatmap.

  • BUGFIX: VictoriaMetrics enterprise validate -dedup.minScrapeInterval value and -downsampling.period intervals are multiples of each other. See these docs.

  • BUGFIX: vmbackup: properly copy appliedRetention.txt files inside <-storageDataPath>/{data} folders during incremental backups. Previously the new appliedRetention.txt could be skipped during incremental backups, which could lead to increased load on storage after restoring from backup. See this issue.

  • BUGFIX: vmagent: suppress context canceled error messages in logs when vmagent is reloading service discovery config. This error could appear starting from v1.93.5. See this PR.

  • BUGFIX: vmagent: remove concurrency limit during parsing of scraped metrics, which was mistakenly applied to it. With this change cmd-line flag -maxConcurrentInserts won't have effect on scraping anymore.

  • BUGFIX: MetricsQL: allow passing median_over_time to aggr_over_time. See this issue.

  • BUGFIX: vminsert: fix ingestion via multitenant url for opentsdbhttp. See this issue. The bug has been introduced in v1.93.2.

  • BUGFIX: vmagent: fix support of legacy DataDog agent, which adds trailing slashes to urls. See this issue. Thanks to @​maxb for spotting the issue.

How to run VictoriaMetrics

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

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

vmutils-*-enterprise.tar.gz archive contains the following additional enterprise 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 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.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [victoriametrics/vmagent](https://github.com/VictoriaMetrics/VictoriaMetrics) | minor | `v1.93.5` -> `v1.94.0` | --- ### Release Notes <details> <summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)</summary> ### [`v1.94.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.94.0) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.93.5...v1.94.0) Released at 2023-10-02 - FEATURE: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): add support for numbers with underscore delimiters such as `1_234_567_890` and `1.234_567_890`. These numbers are easier to read than `1234567890` and `1.234567890`. - FEATURE: [vmbackup](https://docs.victoriametrics.com/vmbackup.html): add support for server-side copy of existing backups. See [these docs](https://docs.victoriametrics.com/vmbackup.html#server-side-copy-of-the-existing-backup) for details. - FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): add the option to see the latest 25 queries. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4718). - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): add ability to set `member num` label for all the metrics scraped by a particular `vmagent` instance in [a cluster of vmagents](https://docs.victoriametrics.com/vmagent.html#scraping-big-number-of-targets) via `-promscrape.cluster.memberLabel` command-line flag. See [these docs](https://docs.victoriametrics.com/vmagent.html#scraping-big-number-of-targets) and [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4247). - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): do not log `unexpected EOF` when reading incoming metrics, since this error is expected and is handled during metrics' parsing. This reduces the amounts of noisy logs. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4817). - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): retry failed write request on the closed connection immediately, without waiting for backoff. This should improve data delivery speed and reduce amount of error logs emitted by vmagent when using idle connections. See related [issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4139). - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): reduces load on Kubernetes control plane during initial service discovery. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4855) for details. - FEATURE: [VictoriaMetrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html): reduce the maximum recovery time at `vmselect` and `vminsert` when some of `vmstorage` nodes become unavailable because of networking issues from 60 seconds to 3 seconds by default. The recovery time can be tuned at `vmselect` and `vminsert` nodes with `-vmstorageUserTimeout` command-line flag if needed. Thanks to [@&#8203;wjordan](https://github.com/wjordan) for [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/4423). - FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): add Prometheus data support to the "Explore cardinality" page. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4320) for details. - FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): make the warning message more noticeable for text fields. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4848). - FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): add button for auto-formatting PromQL/MetricsQL queries. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4681). Thanks to [@&#8203;aramattamara](https://github.com/aramattamara) for the [pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/4694). - FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): improve accessibility score to 100 according to [Google's Lighthouse](https://developer.chrome.com/docs/lighthouse/accessibility/) tests. - FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): organize `min`, `max`, `median` values on the chart legend and tooltips for better visibility. - FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): add explanation about [cardinality explorer](https://docs.victoriametrics.com/#cardinality-explorer) statistic inaccuracy in VictoriaMetrics cluster. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3070). - FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): add storage of query history in `localStorage`. See [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5022). - FEATURE: dashboards: provide copies of Grafana dashboards alternated with VictoriaMetrics datasource at [dashboards/vm](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/master/dashboards/vm). - FEATURE: [vmauth](https://docs.victoriametrics.com/vmauth.html): added ability to set, override and clear request and response headers on a per-user and per-path basis. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4825) and [these docs](https://docs.victoriametrics.com/vmauth.html#auth-config) for details. - FEATURE: [vmauth](https://docs.victoriametrics.com/vmauth.html): add ability to retry requests to the [remaining backends](https://docs.victoriametrics.com/vmauth.html#load-balancing) if they return response status codes specified in the `retry_status_codes` list. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4893). - FEATURE: [vmauth](https://docs.victoriametrics.com/vmauth.html): expose metrics `vmauth_config_last_reload_*` for tracking the state of config reloads, similarly to vmagent/vmalert components. - FEATURE: [vmauth](https://docs.victoriametrics.com/vmauth.html): do not print logs like `SIGHUP received...` once per configured `-configCheckInterval` cmd-line flag. This log will be printed only if config reload was invoked manually. - FEATURE: [vmalert](https://docs.victoriametrics.com/vmalert.html): add `eval_offset` attribute for [Groups](https://docs.victoriametrics.com/vmalert.html#groups). If specified, Group will be evaluated at the exact time offset on the range of \[0...evaluationInterval]. The setting might be useful for cron-like rules which must be evaluated at specific moments of time. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3409) for details. - FEATURE: [vmalert](https://docs.victoriametrics.com/vmalert.html): validate [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html) function names in alerting and recording rules when `vmalert` runs with `-dryRun` command-line flag. Previously it was allowed to use unknown (aka invalid) MetricsQL function names there. For example, `foo()` was counted as a valid query. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4933). - FEATURE: limit the length of string params in log messages to 500 chars. Longer string params are replaced with the `first_250_chars..last_250_chars`. This prevents from too long log lines, which can be emitted by VictoriaMetrics components. - FEATURE: [docker compose environment](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/master/deployment/docker): add `vmauth` component to cluster's docker-compose example for balancing load among multiple `vmselect` components. - FEATURE: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): make sure that `q2` series are returned after `q1` series in the results of `q1 or q2` query, in the same way as Prometheus does. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4763). - FEATURE: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): return empty result from [`bitmap_and(a, b)`](https://docs.victoriametrics.com/MetricsQL.html#bitmap_and), [`bitmap_or(a, b)`](https://docs.victoriametrics.com/MetricsQL.html#bitmap_or) and [`bitmap_xor(a, b)`](https://docs.victoriametrics.com/MetricsQL.html#bitmap_xor) if `a` or `b` have no value at the particular timestamp. Previously `0` was returned in this case. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4996). - FEATURE: stop exposing `vm_merge_need_free_disk_space` metric, since it has been appeared that it confuses users while doesn't bring any useful information. See [this comment](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/686#issuecomment-1733844128). - BUGFIX: [Official Grafana dashboards for VictoriaMetrics](https://grafana.com/orgs/victoriametrics): fix display of ingested rows rate for `Samples ingested/s` and `Samples rate` panels for vmagent's dasbhoard. Previously, not all ingested protocols were accounted in these panels. An extra panel `Rows rate` was added to `Ingestion` section to display the split for rows ingested rate by protocol. - BUGFIX: [vmui](https://docs.victoriametrics.com/#vmui): fix the bug causing render looping when switching to heatmap. - BUGFIX: [VictoriaMetrics enterprise](https://docs.victoriametrics.com/enterprise.html) validate `-dedup.minScrapeInterval` value and `-downsampling.period` intervals are multiples of each other. See [these docs](https://docs.victoriametrics.com/#downsampling). - BUGFIX: [vmbackup](https://docs.victoriametrics.com/vmbackup.html): properly copy `appliedRetention.txt` files inside `<-storageDataPath>/{data}` folders during [incremental backups](https://docs.victoriametrics.com/vmbackup.html#incremental-backups). Previously the new `appliedRetention.txt` could be skipped during incremental backups, which could lead to increased load on storage after restoring from backup. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5005). - BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): suppress `context canceled` error messages in logs when `vmagent` is reloading service discovery config. This error could appear starting from [v1.93.5](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.5). See [this PR](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5048). - BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): remove concurrency limit during parsing of scraped metrics, which was mistakenly applied to it. With this change cmd-line flag `-maxConcurrentInserts` won't have effect on scraping anymore. - BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): allow passing [median_over_time](https://docs.victoriametrics.com/MetricsQL.html#median_over_time) to [aggr_over_time](https://docs.victoriametrics.com/MetricsQL.html#aggr_over_time). See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5034). - BUGFIX: [vminsert](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html): fix ingestion via [multitenant url](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#multitenancy-via-labels) for opentsdbhttp. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5061). The bug has been introduced in [v1.93.2](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.2). - BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): fix support of legacy DataDog agent, which adds trailing slashes to urls. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5078). Thanks to [@&#8203;maxb](https://github.com/maxb) for spotting the issue. ##### How to run VictoriaMetrics Unpack the `victoria-metrics-*.tar.gz` archive and read [these docs](https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/Single-server-VictoriaMetrics#operation). `vmutils-*.tag.gz` archive contains the following tools: - [vmagent](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/app/vmagent/README.md) - [vmalert](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/app/vmalert/README.md) - [vmauth](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/app/vmauth/README.md) - [vmbackup](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/app/vmbackup/README.md) - [vmctl](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/app/vmctl/README.md) - [vmrestore](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/app/vmrestore/README.md) `vmutils-*-enterprise.tar.gz` archive contains the following additional [enterprise tools](https://victoriametrics.com/enterprise.html): - [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager.html) - [vmgateway](https://docs.victoriametrics.com/vmgateway.html) The corresponding docker images are available [here](https://hub.docker.com/r/victoriametrics/). Cluster version is available [here](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/cluster). </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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zLjIiLCJ1cGRhdGVkSW5WZXIiOiIzNy4zLjIiLCJ0YXJnZXRCcmFuY2giOiJtYXN0ZXIifQ==-->
renovate added 1 commit 2023-10-03 00:02:07 +00:00
AverageMarcus merged commit 590bd5d189 into master 2023-10-03 07:07:11 +00:00
AverageMarcus deleted branch renovate/victoriametrics-vmagent-1.x 2023-10-03 07:07:11 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AverageMarcus/cluster.fun#106
No description provided.
Delete Branch "renovate/victoriametrics-vmagent-1.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?