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

Update victoriametrics/vmagent Docker tag to v1.96.0 #152

Merged
AverageMarcus merged 1 commits from renovate/victoriametrics into master 2023-12-15 10:12:46 +00:00
Conversation 0 Commits 1 Files Changed 2 +2 -2
renovate commented 2023-12-13 00:03:46 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
victoriametrics/vmagent minor v1.95.1 -> v1.96.0

Release Notes

VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)

v1.96.0

Compare Source

Released at 2023-12-13

vmalert's metrics vmalert_alerting_rules_error and vmalert_recording_rules_error were replaced with vmalert_alerting_rules_errors_total and vmalert_recording_rules_errors_total. See this issue for details.

  • SECURITY: upgrade base docker image (Alpine) from 3.18.4 to 3.19.0. See alpine 3.19.0 release notes.

  • SECURITY: upgrade Go builder from Go1.21.4 to Go1.21.5. See the list of issues addressed in Go1.21.5.

  • FEATURE: vmauth: add ability to send requests to the first available backend and fall back to other hot standby backends when the first backend is unavailable. This allows building highly available setups as shown in these docs. See this issue.

  • FEATURE: vmselect: allow specifying multiple groups of vmstorage nodes with independent -replicationFactor per each group. See these docs and this feature request for details.

  • FEATURE: vmselect: allow opening vmui and investigating Top queries and Active queries when the vmselect is overloaded with concurrent queries (e.g. when more than -search.maxConcurrentRequests concurrent queries are executed). Previously an attempt to open Top queries or Active queries at vmui could result in couldn't start executing the request in ... seconds, since -search.maxConcurrentRequests=... concurrent requests are executed error, which could complicate debugging of overloaded vmselect or single-node VictoriaMetrics.

  • FEATURE: vmagent: add -enableMultitenantHandlers command-line flag, which allows receiving data via VictoriaMetrics cluster urls at vmagent and converting tenant ids to (vm_account_id, vm_project_id) labels before sending the data to the configured -remoteWrite.url. See these docs for details.

  • FEATURE: vmagent: add -remoteWrite.disableOnDiskQueue command-line flag, which can be used for disabling data queueing to disk when the remote storage cannot keep up with the data ingestion rate. See these docs and this feature request.

  • FEATURE: vmagent: add support for reading and writing samples via Google PubSub. See these docs.

  • FEATURE: vmagent: show all the dropped targets together with the reason why they are dropped at http://vmagent:8429/service-discovery page. Previously targets, which were dropped because of target sharding weren't displayed on this page. This could complicate service discovery debugging. See this issue and this feature request.

  • FEATURE: reduce the default value for -import.maxLineLen command-line flag from 100MB to 10MB in order to prevent excessive memory usage during data import via /api/v1/import.

  • FEATURE: vmagent: add keep_if_contains and drop_if_contains relabeling actions. See these docs for details.

  • FEATURE: vmagent: export vm_promscrape_scrape_pool_targets metric to track the number of targets each scrape job discovers. See this feature request.

  • FEATURE: vmalert: provide /vmalert/api/v1/rule and /api/v1/rule API endpoints to get the rule object in JSON format. See these docs for details.

  • FEATURE: vmalert: deprecate process gauge metrics vmalert_alerting_rules_error and vmalert_recording_rules_error in favour of vmalert_alerting_rules_errors_total and vmalert_recording_rules_errors_total counter metrics. Counter metric type is more suitable for error counting as it preserves the state change between the scrapes. See this issue for details.

  • FEATURE: MetricsQL: add day_of_year() function, which returns the day of the year for each of the given unix timestamps. See this issue for details. Thanks to @​luckyxiaoqiang for the pull request.

  • FEATURE: all VictoriaMetrics binaries: expose additional metrics at /metrics page, which may simplify debugging of VictoriaMetrics components (see this feature request):

    • go_sched_latencies_seconds - the histogram, which shows the time goroutines have spent in runnable state before actually running. Big values point to the lack of CPU time for the current workload.
    • go_mutex_wait_seconds_total - the counter, which shows the total time spent by goroutines waiting for locked mutex. Big values point to mutex contention issues.
    • go_gc_cpu_seconds_total - the counter, which shows the total CPU time spent by Go garbage collector.
    • go_gc_mark_assist_cpu_seconds_total - the counter, which shows the total CPU time spent by goroutines in GC mark assist state.
    • go_gc_pauses_seconds - the histogram, which shows the duration of GC pauses.
    • go_scavenge_cpu_seconds_total - the counter, which shows the total CPU time spent by Go runtime for returning memory to the Operating System.
    • go_memlimit_bytes - the value of GOMEMLIMIT environment variable.

  • FEATURE: vmui: enhance autocomplete functionality with caching. See this issue.

  • FEATURE: add field version to the response for /api/v1/status/buildinfo API for using more efficient API in Grafana for receiving label values. Add additional info about setup Grafana datasource. See this issue and these docs for details.

  • FEATURE: add -search.maxResponseSeries command-line flag for limiting the number of time series a single query to /api/v1/query or /api/v1/query_range can return. This limit can protect Grafana from high memory usage when the query returns too many series. See this feature request.

  • FEATURE: Alerting rules for VictoriaMetrics: ease aggregation for certain alerting rules to keep more useful labels for the context. Before, all extra labels except job and instance were ignored. See this pull request and this follow-up commit. Thanks to @​7840vz.

  • FEATURE: vmctl: allow reversing the migrating order from the newest to the oldest data for vm-native and remote-read modes via --vm-native-filter-time-reverse and --remote-read-filter-time-reverse command-line flags respectively. See: https://docs.victoriametrics.com/vmctl.html#using-time-based-chunking-of-migration and this feature request.

  • BUGFIX: MetricsQL: properly calculate values for the first point on the graph for queries, which do not use rollup functions. For example, previously count(up) could return lower than expected values for the first point on the graph. This also could result in lower than expected values in the middle of the graph like in this issue when the response caching isn't disabled. The issue has been introduced in v1.95.0.

  • BUGFIX: vmagent: prevent from FATAL: cannot flush metainfo panic when -remoteWrite.multitenantURL command-line flag is set. See this issue.

  • BUGFIX: vmagent: properly decode zstd-encoded data blocks received via VictoriaMetrics remote_write protocol. See this issue comment.

  • BUGFIX: vmagent: properly add new labels at output_relabel_configs during stream aggregation. Previously this could lead to corrupted labels in output samples. Thanks to @​ChengChung for providing detailed report for this bug.

  • BUGFIX: vmalert-tool: allow using arbitrary eval_time in alert_rule_test case. Previously, test cases with eval_time not being a multiple of evaluation_interval would fail.

  • BUGFIX: vmalert: sanitize label names before sending the alert notification to Alertmanager. Before, vmalert would send notifications with labels containing characters not supported by Alertmanager validator, resulting into validation errors like msg="Failed to validate alerts" err="invalid label set: invalid name "foo.bar".

  • BUGFIX: vmbackupmanager: fix vmbackupmanager not deleting previous object versions from S3 when applying retention policy with -deleteAllObjectVersions command-line flag.

  • BUGFIX: vminsert: fix panic when ingesting data via NewRelic protocol into VictoriaMetrics cluster. See this issue.

  • BUGFIX: properly escape < character in responses returned via /federate endpoint. See this issue.

  • BUGFIX: vmctl: check for Error field in response from influx client during migration. Before, only network errors were checked. Thanks to @​wozz for the pull request.

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.95.1` -> `v1.96.0` | --- ### Release Notes <details> <summary>VictoriaMetrics/VictoriaMetrics (victoriametrics/vmagent)</summary> ### [`v1.96.0`](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.96.0) [Compare Source](https://github.com/VictoriaMetrics/VictoriaMetrics/compare/v1.95.1...v1.96.0) Released at 2023-12-13 **vmalert's metrics `vmalert_alerting_rules_error` and `vmalert_recording_rules_error` were replaced with `vmalert_alerting_rules_errors_total` and `vmalert_recording_rules_errors_total`. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5160) for details.** - SECURITY: upgrade base docker image (Alpine) from 3.18.4 to 3.19.0. See [alpine 3.19.0 release notes](https://www.alpinelinux.org/posts/Alpine-3.19.0-released.html). - SECURITY: upgrade Go builder from Go1.21.4 to Go1.21.5. See [the list of issues addressed in Go1.21.5](https://github.com/golang/go/issues?q=milestone%3AGo1.21.5+label%3ACherryPickApproved). - FEATURE: [vmauth](https://docs.victoriametrics.com/vmauth.html): add ability to send requests to the first available backend and fall back to other `hot standby` backends when the first backend is unavailable. This allows building highly available setups as shown in [these docs](https://docs.victoriametrics.com/vmauth.html#high-availability). See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4792). - FEATURE: `vmselect`: allow specifying multiple groups of `vmstorage` nodes with independent `-replicationFactor` per each group. See [these docs](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#vmstorage-groups-at-vmselect) and [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5197) for details. - FEATURE: `vmselect`: allow opening [vmui](https://docs.victoriametrics.com/#vmui) and investigating [Top queries](https://docs.victoriametrics.com/#top-queries) and [Active queries](https://docs.victoriametrics.com/#active-queries) when the `vmselect` is overloaded with concurrent queries (e.g. when more than `-search.maxConcurrentRequests` concurrent queries are executed). Previously an attempt to open `Top queries` or `Active queries` at `vmui` could result in `couldn't start executing the request in ... seconds, since -search.maxConcurrentRequests=... concurrent requests are executed` error, which could complicate debugging of overloaded `vmselect` or single-node VictoriaMetrics. - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): add `-enableMultitenantHandlers` command-line flag, which allows receiving data via [VictoriaMetrics cluster urls](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#url-format) at `vmagent` and converting [tenant ids](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#multitenancy) to (`vm_account_id`, `vm_project_id`) labels before sending the data to the configured `-remoteWrite.url`. See [these docs](https://docs.victoriametrics.com/vmagent.html#multitenancy) for details. - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): add `-remoteWrite.disableOnDiskQueue` command-line flag, which can be used for disabling data queueing to disk when the remote storage cannot keep up with the data ingestion rate. See [these docs](https://docs.victoriametrics.com/vmagent.html#disabling-on-disk-persistence) and [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2110). - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): add support for reading and writing samples via [Google PubSub](https://cloud.google.com/pubsub). See [these docs](https://docs.victoriametrics.com/vmagent.html#google-pubsub-integration). - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): show all the dropped targets together with the reason why they are dropped at `http://vmagent:8429/service-discovery` page. Previously targets, which were dropped because of [target sharding](https://docs.victoriametrics.com/vmagent.html#scraping-big-number-of-targets) weren't displayed on this page. This could complicate service discovery debugging. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5389) and [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4018). - FEATURE: reduce the default value for `-import.maxLineLen` command-line flag from 100MB to 10MB in order to prevent excessive memory usage during data import via [/api/v1/import](https://docs.victoriametrics.com/#how-to-import-data-in-json-line-format). - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): add `keep_if_contains` and `drop_if_contains` relabeling actions. See [these docs](https://docs.victoriametrics.com/vmagent.html#relabeling-enhancements) for details. - FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): export `vm_promscrape_scrape_pool_targets` [metric](https://docs.victoriametrics.com/vmagent.html#monitoring) to track the number of targets each scrape job discovers. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5311). - FEATURE: [vmalert](https://docs.victoriametrics.com/vmalert.html): provide `/vmalert/api/v1/rule` and `/api/v1/rule` API endpoints to get the rule object in JSON format. See [these docs](https://docs.victoriametrics.com/vmalert.html#web) for details. - FEATURE: [vmalert](https://docs.victoriametrics.com/vmalert.html): deprecate process gauge metrics `vmalert_alerting_rules_error` and `vmalert_recording_rules_error` in favour of `vmalert_alerting_rules_errors_total` and `vmalert_recording_rules_errors_total` counter metrics. [Counter](https://docs.victoriametrics.com/keyConcepts.html#counter) metric type is more suitable for error counting as it preserves the state change between the scrapes. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5160) for details. - FEATURE: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): add [day_of_year()](https://docs.victoriametrics.com/MetricsQL.html#day_of_year) function, which returns the day of the year for each of the given unix timestamps. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5345) for details. Thanks to [@&#8203;luckyxiaoqiang](https://github.com/luckyxiaoqiang) for the [pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5368/). - FEATURE: all VictoriaMetrics binaries: expose additional metrics at `/metrics` page, which may simplify debugging of VictoriaMetrics components (see [this feature request](https://github.com/VictoriaMetrics/metrics/issues/54)): - `go_sched_latencies_seconds` - the [histogram](https://docs.victoriametrics.com/keyConcepts.html#histogram), which shows the time goroutines have spent in runnable state before actually running. Big values point to the lack of CPU time for the current workload. - `go_mutex_wait_seconds_total` - the [counter](https://docs.victoriametrics.com/keyConcepts.html#counter), which shows the total time spent by goroutines waiting for locked mutex. Big values point to mutex contention issues. - `go_gc_cpu_seconds_total` - the [counter](https://docs.victoriametrics.com/keyConcepts.html#counter), which shows the total CPU time spent by Go garbage collector. - `go_gc_mark_assist_cpu_seconds_total` - the [counter](https://docs.victoriametrics.com/keyConcepts.html#counter), which shows the total CPU time spent by goroutines in GC mark assist state. - `go_gc_pauses_seconds` - the [histogram](https://docs.victoriametrics.com/keyConcepts.html#histogram), which shows the duration of GC pauses. - `go_scavenge_cpu_seconds_total` - the [counter](https://docs.victoriametrics.com/keyConcepts.html#counter), which shows the total CPU time spent by Go runtime for returning memory to the Operating System. - `go_memlimit_bytes` - the value of [GOMEMLIMIT](https://pkg.go.dev/runtime#hdr-Environment_Variables) environment variable. - FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): enhance autocomplete functionality with caching. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5348). - FEATURE: add field `version` to the response for `/api/v1/status/buildinfo` API for using more efficient API in Grafana for receiving label values. Add additional info about setup Grafana datasource. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5370) and [these docs](https://docs.victoriametrics.com/#grafana-setup) for details. - FEATURE: add `-search.maxResponseSeries` command-line flag for limiting the number of time series a single query to [`/api/v1/query`](https://docs.victoriametrics.com/keyConcepts.html#instant-query) or [`/api/v1/query_range`](https://docs.victoriametrics.com/keyConcepts.html#range-query) can return. This limit can protect Grafana from high memory usage when the query returns too many series. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5372). - FEATURE: [Alerting rules for VictoriaMetrics](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/master/deployment/docker#alerts): ease aggregation for certain alerting rules to keep more useful labels for the context. Before, all extra labels except `job` and `instance` were ignored. See this [pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5429) and this [follow-up commit](https://github.com/VictoriaMetrics/VictoriaMetrics/commit/8fb68152e67712ed2c16dcfccf7cf4d0af140835). Thanks to [@&#8203;7840vz](https://github.com/7840vz). - FEATURE: [vmctl](https://docs.victoriametrics.com/vmctl.html): allow reversing the migrating order from the newest to the oldest data for [vm-native](https://docs.victoriametrics.com/vmctl.html#migrating-data-from-victoriametrics) and [remote-read](https://docs.victoriametrics.com/vmctl.html#migrating-data-by-remote-read-protocol) modes via `--vm-native-filter-time-reverse` and `--remote-read-filter-time-reverse` command-line flags respectively. See: https://docs.victoriametrics.com/vmctl.html#using-time-based-chunking-of-migration and [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5376). - BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly calculate values for the first point on the graph for queries, which do not use [rollup functions](https://docs.victoriametrics.com/MetricsQL.html#rollup-functions). For example, previously `count(up)` could return lower than expected values for the first point on the graph. This also could result in lower than expected values in the middle of the graph like in [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5388) when the response caching isn't disabled. The issue has been introduced in [v1.95.0](https://docs.victoriametrics.com/CHANGELOG.html#v1950). - BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): prevent from `FATAL: cannot flush metainfo` panic when [`-remoteWrite.multitenantURL`](https://docs.victoriametrics.com/vmagent.html#multitenancy) command-line flag is set. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5357). - BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): properly decode zstd-encoded data blocks received via [VictoriaMetrics remote_write protocol](https://docs.victoriametrics.com/vmagent.html#victoriametrics-remote-write-protocol). See [this issue comment](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5301#issuecomment-1815871992). - BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): properly add new labels at `output_relabel_configs` during [stream aggregation](https://docs.victoriametrics.com/stream-aggregation.html). Previously this could lead to corrupted labels in output samples. Thanks to [@&#8203;ChengChung](https://github.com/ChengChung) for providing [detailed report for this bug](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5402). - BUGFIX: [vmalert-tool](https://docs.victoriametrics.com/#vmalert-tool): allow using arbitrary `eval_time` in [alert_rule_test](https://docs.victoriametrics.com/vmalert-tool.html#alert_test_case) case. Previously, test cases with `eval_time` not being a multiple of `evaluation_interval` would fail. - BUGFIX: [vmalert](https://docs.victoriametrics.com/vmalert.html): sanitize label names before sending the alert notification to Alertmanager. Before, vmalert would send notifications with labels containing characters not supported by Alertmanager validator, resulting into validation errors like `msg="Failed to validate alerts" err="invalid label set: invalid name "foo.bar"`. - BUGFIX: [vmbackupmanager](https://docs.victoriametrics.com/vmbackupmanager.html): fix `vmbackupmanager` not deleting previous object versions from S3 when applying retention policy with `-deleteAllObjectVersions` command-line flag. - BUGFIX: [vminsert](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html): fix panic when ingesting data via [NewRelic protocol](https://docs.victoriametrics.com/#how-to-send-data-from-newrelic-agent) into VictoriaMetrics cluster. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5416). - BUGFIX: properly escape `<` character in responses returned via [`/federate`](https://docs.victoriametrics.com/#federation) endpoint. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5431). - BUGFIX: [vmctl](https://docs.victoriametrics.com/vmctl.html): check for Error field in response from influx client during migration. Before, only network errors were checked. Thanks to [@&#8203;wozz](https://github.com/wozz) for the [pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5446). ##### 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) - [vmalert-tool](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/app/vmalert-tool/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:eyJjcmVhdGVkSW5WZXIiOiIzNy45MS40IiwidXBkYXRlZEluVmVyIjoiMzcuOTEuNCIsInRhcmdldEJyYW5jaCI6Im1hc3RlciJ9-->
renovate added 1 commit 2023-12-13 00:03:46 +00:00
AverageMarcus merged commit 3fea0685cb into master 2023-12-15 10:12:46 +00:00
AverageMarcus deleted branch renovate/victoriametrics 2023-12-15 10:12:46 +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#152
No description provided.
Delete Branch "renovate/victoriametrics"

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?