Kiu/VictoriaMetrics
Kiu/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-12-14 16:12:15 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
21170e558c
VictoriaMetrics/docs/CHANGELOG.md

770 lines
78 KiB
Markdown
Raw Normal View History

docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
---
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
sort: 100
weight: 100
prepare static docs to migration Signed-off-by: Artem Navoiev <tenmozes@gmail.com>
2023-04-30 12:31:45 +02:00
title: CHANGELOG
menu:
docs:
vmalert-tool: implement unittest (#4789) 1. split package rule under /app/vmalert, expose needed objects 2. add vmalert-tool with unittest subcmd https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2945
2023-10-13 13:54:33 +02:00
parent: 'victoriametrics'
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
weight: 100
prepare static docs to migration Signed-off-by: Artem Navoiev <tenmozes@gmail.com>
2023-04-30 12:31:45 +02:00
aliases:
- /CHANGELOG.html
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
---
docs/CHANGELOG.md: add `CHANGELOG` header
2020-11-07 00:14:34 +01:00
# CHANGELOG
docs/VictoriaLogs: add CHANGELOG.md
2023-07-18 08:14:05 +02:00
The following `tip` changes can be tested by building VictoriaMetrics components from the latest commits according to the following docs:
A good change for MD files (#2353) * Lint YAML * Remove extra comment * Fix command problem * Format MD files * Format & fix problem of MD files for docs * Another fix for MD files
2022-03-22 12:40:55 +01:00
docs/CHANGELOG.md: add instructions on how to build VictoriaMetrics components from source code in order to test tip changes
2022-02-08 15:43:51 +01:00
* [How to build single-node VictoriaMetrics](https://docs.victoriametrics.com/#how-to-build-from-sources)
* [How to build cluster version of VictoriaMetrics](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#building-from-sources)
* [How to build vmagent](https://docs.victoriametrics.com/vmagent.html#how-to-build-from-sources)
* [How to build vmalert](https://docs.victoriametrics.com/vmalert.html#how-to-build-from-sources)
* [How to build vmauth](https://docs.victoriametrics.com/vmauth.html#how-to-build-from-sources)
* [How to build vmctl](https://docs.victoriametrics.com/vmctl.html#how-to-build)
vmagent: added hetzner sd config (#5550) * added hetzner robot and hetzner cloud sd configs * remove gettoken fun and update docs * Updated CHANGELOG and vmagent docs * Updated CHANGELOG and vmagent docs --------- Co-authored-by: Nikolay <nik@victoriametrics.com>
2024-01-15 10:13:22 +01:00
Metrics of the latest version of VictoriaMetrics cluster are available for viewing at our
docs/changelog: add link to sandbox (#5050) Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-09-25 14:00:41 +02:00
[sandbox](https://play-grafana.victoriametrics.com/d/oS7Bi_0Wz_vm/victoriametrics-cluster-vm).
docs/LTS-releases.md: cosmetic fixes
2024-02-17 17:09:36 +01:00
The sandbox cluster installation runs under the constant load generated by
[prometheus-benchmark](https://github.com/VictoriaMetrics/prometheus-benchmark) and is used for testing latest releases.
See also [LTS releases](https://docs.victoriametrics.com/LTS-releases.html).
app/vmctl: fix performance degradation, add flag to disable backoff policy (#4097) * app/vmctl: change api for getting metric names * app/vmctl: fix tests * app/vmctl: add flag to enable backoff policy, fix test, performance improvements * app/vmctl: use one http client * app/vmctl: made linter happy * app/vmctl: updated documentation and CHANGELOG.md * app/vmctl: cleanup * app/vmctl: rename flag * app/vmctl: cleanup * app/vmctl: fix comments * app/vmctl: fix metrics parser problem, improve tests
2023-04-14 08:34:54 +02:00
docs/CHANGELOG.md: move tip to proper place
2021-05-20 16:56:03 +02:00
## tip
deployment/docker: update Go builder from Go1.21.5 to Go1.21.6
2024-01-16 16:00:16 +01:00
vendor: update github.com/VictoriaMetrics/metricsql from v0.72.1 to v0.73.0 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5383
2024-02-18 17:41:39 +01:00
* FEATURE: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): propagate [label filters](https://docs.victoriametrics.com/keyconcepts/#filtering) via all the [label manipulation functions](https://docs.victoriametrics.com/metricsql/#label-manipulation-functions). For example, `label_del(some_metric{job="foo"}, "instance") + other_metric{pod="bar"}` is now transformed to `label_del(some_metric{job="foo",pod="bar"}, "instance") + other_metric{job="foo",pod="bar"}`. This should reduce the amounts of time series processed during query execution.
app/vmselect/promql: add `count_values_over_time()` MetricsQL function See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5847
2024-02-22 12:39:07 +01:00
* FEATURE: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): add [count_values_over_time](https://docs.victoriametrics.com/MetricsQL.html#count_values_over_time) function. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5847).
app/vmstorage: expose vm_last_partition_parts metrics, which may help identifying performance issues related to the increased number of parts in the last partition
2024-02-15 13:51:19 +01:00
* FEATURE: [Single-node VictoriaMetrics](https://docs.victoriametrics.com/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/cluster-victoriametrics/): expose `vm_last_partition_parts` [metrics](https://docs.victoriametrics.com/#monitoring), which show the number of [parts in the latest partition](https://docs.victoriametrics.com/#storage). These metrics may help debugging query performance slowdown related to the increased number of parts in the last partition, since usually all the ingested data is written to the last partition and all the queries are performed over the recently ingested data, e.g. the last partition.
app/vmstorage: expose vm_snapshots metric, which shows the current number of snapshots While at it, refresh docs about snapshots - https://docs.victoriametrics.com/#how-to-work-with-snapshots
2024-02-22 17:32:53 +01:00
* FEATURE: [Single-node VictoriaMetrics](https://docs.victoriametrics.com/) and `vmstorage` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/cluster-victoriametrics/): expose `vm_snapshots` m[metric](https://docs.victoriametrics.com/#monitoring), which shows the current number of snapshots created via [snapshot API](https://docs.victoriametrics.com/#how-to-work-with-snapshots).
lib/promscrape/discovery/kuma: add support for `client_id` option See https://github.com/prometheus/prometheus/pull/13278
2024-02-18 18:19:36 +01:00
* FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): add support for `client_id` option into [kuma_sd_configs](https://docs.victoriametrics.com/sd_configs/#kuma_sd_configs) in the same way as Prometheus does. See [this pull request](https://github.com/prometheus/prometheus/pull/13278).
lib/promscrape: add support for `enable_compression` option in the same way as Prometheus does Updates https://github.com/prometheus/prometheus/pull/13166 Updates https://github.com/prometheus/prometheus/issues/12319 Do not document enable_compression option at docs/sd_configs.md, since vmagent already supports more clear disable_compression option - see https://docs.victoriametrics.com/vmagent/#scrape_config-enhancements
2024-02-18 18:40:34 +01:00
* FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): add support for `enable_compression` option in [scrape_configs](https://docs.victoriametrics.com/sd_configs/#scrape_configs) in order to be compatible with Prometheus scrape configs. See [this pull request](https://github.com/prometheus/prometheus/pull/13166) and [this feature request](https://github.com/prometheus/prometheus/issues/12319). Note that `vmagent` was always supporting [`disable_compression` option](https://docs.victoriametrics.com/vmagent/#scrape_config-enhancements) before Prometheus added `enable_compression` option.
vmctl : Provide TLS config options for Open TSDB datasource #5797 (#5832) Originally implemented here https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5797 --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: khushijain21 <khushij393@gmail.com> (cherry picked from commit bb1279bfc438693714d5a8181ad20400e5a8f7d1)
2024-02-20 16:22:58 +01:00
* FEATURE: [vmctl](https://docs.victoriametrics.com/vmctl.html): support client-side TLS configuration for [InfluxDB](https://docs.victoriametrics.com/vmctl/#migrating-data-from-influxdb-1x), [Remote Read protocol](https://docs.victoriametrics.com/vmctl/#migrating-data-by-remote-read-protocol) and [OpenTSDB](https://docs.victoriametrics.com/vmctl/#migrating-data-from-opentsdb). See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5748). Thanks to @khushijain21 for pull requests [1](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5783), [2](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5798), [3](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5797).
vendor: update github.com/VictoriaMetrics/metricsql from v0.72.1 to v0.73.0 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5383
2024-02-18 17:41:39 +01:00
* FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): preserve [`WITH` templates](https://play.victoriametrics.com/select/accounting/1/6a716b0f-38bc-4856-90ce-448fd713e3fe/expand-with-exprs) when clicking the `prettify query` button at the right side of query input field. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5383).
docs: move recent changes to Tip These changes were mistakenly put to existing release Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit dc25c30fdc69cf3a738450c236f1a035f8349975)
2024-02-20 14:58:15 +01:00
* FEATURE: [vmalert](https://docs.victoriametrics.com/#vmalert): support filtering by group, rule or labels in [vmalert's UI](https://docs.victoriametrics.com/vmalert/#web) for `/groups` and `/alerts` pages. See [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5791) by @victoramsantos.
app/vmstorage: expose vm_last_partition_parts metrics, which may help identifying performance issues related to the increased number of parts in the last partition
2024-02-15 13:51:19 +01:00
docs/CHANGELOG.md: document f8207e33a21db65bff9585e7a1aa0f144f1a1ae7
2024-02-17 16:52:53 +01:00
* BUGFIX: fix the misleading error `0ms is out of allowed range [0 ...` when passing `step=0` to [/api/v1/query](https://docs.victoriametrics.com/keyconcepts/#instant-query)
or [/api/v1/query_range](https://docs.victoriametrics.com/keyconcepts/#range-query). See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5795).
[lib/httputils] fixed floating-point error when parsing time in RFC3339 format (#5814) * [lib/promutils, lib/httputils] fixed floating-point error when parsing time in RFC3339 format (#5801) * fixed tests * fixed test * Revert "fixed test" This reverts commit 8a29764806bda7c3853a0b12b6b9704c71e5c65a. * Revert "fixed tests" This reverts commit 9ce13d1042caaaafcec33b4c97846cfafa27ce0f. * Revert "[lib/promutils, lib/httputils] fixed floating-point error when parsing time in RFC3339 format (#5801)" This reverts commit a7a04bd4 * [lib/httputils] fixed floating-point error when parsing time in RFC3339 format (#5801) --------- Co-authored-by: Nikolay <nik@victoriametrics.com>
2024-02-22 10:20:54 +01:00
* BUGFIX: [Single-node VictoriaMetrics](https://docs.victoriametrics.com/) and `vmselect` in [VictoriaMetrics cluster](https://docs.victoriametrics.com/cluster-victoriametrics/): fixed floating-point error when parsing time in RFC3339 format. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5801) for details.
docs: move recent changes to Tip These changes were mistakenly put to existing release Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit dc25c30fdc69cf3a738450c236f1a035f8349975)
2024-02-20 14:58:15 +01:00
* BUGFIX: [vmalert](https://docs.victoriametrics.com/#vmalert): consistently sort groups by name and filename on `/groups` page in UI. This should prevent non-deterministic sorting for groups with identical names.
app/vmselect: change export/csv timestamp format for rfc3339 to respect milliseconds (#5853) * app/vmselect: adds milliseconds to the csv export response for rfc3339 * milliseconds is a standard prescion for VictoriaMetrics query request responses https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5837 * app/victoria-metrics: adds tests for csv export/import follow-up after 3541a8d0cf96dd4f8563624c4aab6816615d0756 --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com>
2024-02-22 20:31:22 +01:00
* BUGFIX: [vmselect](https://docs.victoriametrics.com/): format time with milliseconds precision when `__timestamp__:rfc3339` is specified for [/api/v1/export/csv](https://docs.victoriametrics.com/#how-to-export-csv-data) API response. See this [issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5837) for details.
docs/CHANGELOG.md: document f8207e33a21db65bff9585e7a1aa0f144f1a1ae7
2024-02-17 16:52:53 +01:00
docs/CHANGELOG.md: cut v1.98.0 release
2024-02-14 15:00:50 +01:00
## [v1.98.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.98.0)
Released at 2024-02-14
all: upgrade Go builder from Go1.21.7 to Go1.22.0 See https://go.dev/doc/go1.22
2024-02-12 20:59:41 +01:00
* SECURITY: upgrade Go builder from Go1.21.6 to Go1.22.0. See [the list of issues addressed in Go1.21.7](https://github.com/golang/go/issues?q=milestone%3AGo1.21.7+label%3ACherryPickApproved),
plus [the changelog for Go1.22.0](https://go.dev/doc/go1.22).
all: update Go builder from Go1.21.6 to Go1.21.7 See https://github.com/golang/go/issues?q=milestone%3AGo1.21.7+label%3ACherryPickApproved
2024-02-07 03:00:35 +01:00
docs/CHANGELOG.md: various typo cleanups
2024-02-14 01:45:00 +01:00
* FEATURE: all VictoriaMetrics components: add support for TLS client certificate verification at `-httpListenAddr` (aka [mTLS](https://en.wikipedia.org/wiki/Mutual_authentication)). See [these docs](https://docs.victoriametrics.com/#mtls-protection) and [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5458).
* FEATURE: all VictoriaMetrics components: add support for accepting http requests over multiple distinct TCP addresses. This can be done by starting VictoriaMetrics component with multiple `-httpListenAddr` command-line flags. For example, `./victoria-metrics -httpListenAddr=some-host:12345 -httpListenAddr=localhost:8428` starts VictoriaMetrics, which accepts incoming http requests at both `some-host:12345` and `localhost:8428`. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1470).
* FEATURE: all VictoriaMetrics components: add support for empty command-line flag values in short array notation. For example, `-remoteWrite.sendTimeout=',20s,'` specifies three `-remoteWrite.sendTimeout` values - the first one and the last one have default values (`30s` in this case), while the second one is set to `20s`.
* FEATURE: [vmauth](https://docs.victoriametrics.com/vmauth.html): add support for [mTLS](https://en.wikipedia.org/wiki/Mutual_authentication)-based request routing to different backends depending on the subject of the TLS certificate provided by the client. See [these docs](https://docs.victoriametrics.com/vmauth.html#mtls-based-request-routing) and [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1547).
app/{vmagent,vminsert}: follow-up after a1d1ccd6f21c3ffa40b45112ec4d37ab7cb05d82 - Document the change at docs/CHANGELOG.md - Copy changes from docs/Single-server-VictoriaMetrics.md to README.md - Add missing handler for processing multitenant requests ( https://docs.victoriametrics.com/vmagent/#multitenancy ) - Substitute github.com/stretchr/testify dependency with 3 lines of code in the added tests - Comment unclear code at lib/protoparser/datadogsketches/parser.go , so @AndrewChubatiuk could update it and add permalinks to the original source code there. - Various code cleanups Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5584 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3091
2024-02-07 00:15:25 +01:00
* FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html) and [single-node VictoriaMetrics](https://docs.victoriametrics.com): add support for data ingestion via [DataDog lambda extension](https://docs.datadoghq.com/serverless/libraries_integrations/extension/) aka `/api/beta/sketches` endpoint. See [these docs](https://docs.victoriametrics.com/#how-to-send-data-from-datadog-agent) and [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3091). Thanks to @AndrewChubatiuk for [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5584).
docs/CHANGELOG.md: various typo cleanups
2024-02-14 01:45:00 +01:00
* FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): add `-remoteWrite.tlsHandshakeTimeout` command-line flag for tuning the timeout needed for establishing TLS connections to `-remoteWrite.url`. Bigger tls handshake timeouts should reduce the probability of `http: TLS handshake error from ...: EOF` errors at the remote storage side under high load. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1699).
docs/CHANGELOG.md: add a link to docs describing -disableReroutingOnUnavailable command-line flag
2024-02-08 16:03:01 +01:00
* FEATURE: [VictoriaMetrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html): add `-disableReroutingOnUnavailable` command-line flag to `vminsert`, which can be used for reducing resource usage spikes at `vmstorage` nodes during rolling restart. See [these docs](https://docs.victoriametrics.com/cluster-victoriametrics/#improving-re-routing-performance-during-restart). Thanks to @Muxa1L for [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5713).
app/vmselect: add ability to reset rollup result cache on startup by passing -search.resetRollupResultCacheOnStartup command-line flag Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/834
2024-02-08 13:40:37 +01:00
* FEATURE: add `-search.resetRollupResultCacheOnStartup` command-line flag for resetting [query cache](https://docs.victoriametrics.com/#rollup-result-cache) on startup. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/834).
vendor: update github.com/VictoriaMetrics/metricsql from v0.70.1 to v0.71.0 This adds an ability to propagate label filters across label_set() and alias() functions. This should help https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1827#issuecomment-1654095358
2024-02-13 05:32:25 +01:00
* FEATURE: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): propagate label filters across [label_set](https://docs.victoriametrics.com/MetricsQL.html#label_set) and [alias](https://docs.victoriametrics.com/MetricsQL.html#alias) functions. For example, `label_set(q1, "a", "b") + q2{c="d"}` is automatically transformed to `label_set(q1{c="d"}, "a", "b") + q2{a="b",c="d"}` now. This should improve performance for such queries. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1827#issuecomment-1654095358).
app/vmselect: add sum_eq_over_time, sum_gt_over_time and sum_le_over_time functions to MetricsQL See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4641
2024-02-13 22:40:04 +01:00
* FEATURE: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): add [sum_eq_over_time](https://docs.victoriametrics.com/MetricsQL.html#sum_eq_over_time), [sum_gt_over_time](https://docs.victoriametrics.com/MetricsQL.html#sum_gt_over_time) and [sum_le_over_time](https://docs.victoriametrics.com/MetricsQL.html#sum_le_over_time) functions. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4641).
docs/CHANGELOG.md: move descriptions for recently added features from `v1.97.1` to `tip`
2024-02-06 15:31:15 +01:00
* FEATURE: [dashboards/vmagent](https://grafana.com/grafana/dashboards/12683): add `Targets scraped/s` stat panel showing the number of targets scraped by the vmagent per-second.
* FEATURE: [dashboards/all](https://grafana.com/orgs/victoriametrics): add new panel `CPU spent on GC`. It should help identifying cases when too much CPU is spent on garbage collection, and advice users on how this can be addressed.
app/vmalert: support filtering for /api/v1/rule like Prometheus does (#5787) Follow-up after https://github.com/VictoriaMetrics/VictoriaMetrics/commit/62e5e2a4c8b6362ad61c2d7e20d0d6ba2aec58f5 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 8850c7431ddfea13417755213bed0b813cccae39)
2024-02-09 14:35:31 +01:00
* FEATURE: [vmalert](https://docs.victoriametrics.com/#vmalert): support [filtering](https://prometheus.io/docs/prometheus/2.49/querying/api/#rules) for `/api/v1/rules` API. See [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5749) by @victoramsantos.
docs: follow-up after 83e55456e212267e8c55151a541790bd4f820187 https://github.com/VictoriaMetrics/VictoriaMetrics/commit/83e55456e212267e8c55151a541790bd4f820187 Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit e1926f286b35ada4cd28008a59a91e9e37bac361)
2024-02-08 15:55:57 +01:00
* FEATURE: [vmbackup](https://docs.victoriametrics.com/vmbackup.html): support client-side TLS configuration for creating and deleting snapshots via `-snapshot.tls*` cmd-line flags. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5724). Thanks to @khushijain21 for the [pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5738).
docs/CHANGELOG.md: move descriptions for recently added features from `v1.97.1` to `tip`
2024-02-06 15:31:15 +01:00
docs: re-classify change of default http timeout to bugfix The change introduced in https://github.com/VictoriaMetrics/VictoriaMetrics/commit/d8c1db7953d2265c9cd3a2913f12aac07a99a45c#diff-2bfab3db5cc1baf4c6d3ff6b19901926e3bdf4411ec685dac973e5fcff1c723b was backported to v1.97.2. Therefore, it is a `bugfix` and should be explicitly mentioned in the changelog of v1.97.2 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-22 21:57:39 +01:00
* BUGFIX: all VictoriaMetrics components: do not close connections to `-httpListenAddr` every 2 minutes. This behavior didn't help spreading load among multiple backend servers behind load-balancing TCP proxy. Instead, it could lead to hard-to-debug issues like [this one](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1304#issuecomment-1636997037). If you still need periodically closing client connections because of some reason, then pass the desired timeout to `-http.connTimeout` command-line flag.
lib/promrelabel: store the original labels before returning them them to promutils.PutLabels() This should reduce memory allocations. This is a follow-up for b09bd6c42ad6a1f6129ebce8e0c0a6ebf492b074 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5389
2024-02-14 15:05:29 +01:00
* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): reduce CPU usage when `-promscrape.dropOriginalLabels` command-line flag is set. This issue has been introduced in [v1.96.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.96.0) when addressing [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5389).
app/vmauth: properly release memory during config reload (#5805) * app/vmauth: properly release memory during config reload previously metrics package hold a refrence for channels for users concurrent requests. it case of churn at `name` field of users configuration, new metric was created. But previous one wasn't deleted. It prevented full parsed configuration from being garbace collected. now all config related metrics are bound to corresponding metrics.Set and unregistered during config reload process. It also must fix an issue with incorrect values for current concurrent user requests https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4690 * wip --------- Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-02-13 19:49:17 +01:00
* BUGFIX: [vmauth](https://docs.victoriametrics.com/vmauth.html): properly release memory during config reload. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4690).
* BUGFIX: [vmauth](https://docs.victoriametrics.com/vmauth.html): properly expose `vmauth_unauthorized_user_concurrent_requests_capacity`, `vmauth_unauthorized_user_concurrent_requests_current`, `vmauth_user_concurrent_requests_capacity` and `vmauth_user_concurrent_requests_current` [metrics](https://docs.victoriametrics.com/vmauth.html#monitoring) after [config reload](https://docs.victoriametrics.com/vmauth.html#config-reload). Previously these metrics didn't work after config reload.
vendor: update github.com/VictoriaMetrics/metricsql from v0.70.0 to v0.70.1 This should help with the https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5604
2024-02-06 20:52:32 +01:00
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly propagate [label filters](https://docs.victoriametrics.com/keyconcepts/#filtering) from multiple arguments passed to [aggregate functions](https://docs.victoriametrics.com/metricsql/#aggregate-functions). For example, `sum({job="foo"}, {job="bar"}) by (job) + a` was improperly optimized to `sum({job="foo"}, {job="bar"}) by (job) + a{job="foo"}` before being executed. This could lead to unexpected results. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5604).
app/vmselect/promql: properly handle precision errors in rollup functions changes(), increases_over_time() and resets() shouldn't take into account value changes, which may occur because of precision errors. The maximum guaranteed precision for raw samples stored in VictoriaMetrics is 12 decimal digits. So do not count relative changes for values if they are smaller than 1e-12 comparing to the value. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/767
2024-02-08 01:30:55 +01:00
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly handle precision errors when calculating [changes](https://docs.victoriametrics.com/metricsql/#changes), [changes_prometheus](https://docs.victoriametrics.com/metricsql/#changes_prometheus), [increases_over_time](https://docs.victoriametrics.com/metricsql/#increases_over_time) and [resets](https://docs.victoriametrics.com/metricsql/#resets) functions. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/767).
docs/CHANGELOG.md: properly document the change at b74006e2caaefcc87ec52650515a4d823de5b661 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5774
2024-02-07 21:05:02 +01:00
* BUGFIX: all VictoriaMetrics components: consistently return 200 http status code from [`/-/reload` endpoint](https://docs.victoriametrics.com/vmagent/#configuration-update). Previously [single-node VictoriaMetrics](https://docs.victoriametrics.com/) was returning 204 http status code. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5774).
app/victoria-metrics: properly send staleness markers on victoriametrics shutdown if -selfScrapeInterval > 0 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/943 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1526
2024-02-08 14:29:17 +01:00
* BUGFIX: properly store [staleness markers](https://docs.victoriametrics.com/vmagent/#prometheus-staleness-markers) for [self-scraped metrics](https://docs.victoriametrics.com/#monitoring) on single-node VictoriaMetrics shutdown. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/943).
docs/CHANGELOG.md: clarify the bugfix description for e1bf8440eba155cd8d57bdbffb9cd45903019ab4
2024-02-08 12:01:19 +01:00
* BUGFIX: prevent from possible `too big indexBlockSize` panic when samples with too long label values (~64Kb) are ingested into VictoriaMetrics.
vmui: fix graph dragging (#5769) Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-02-06 21:32:03 +01:00
* BUGFIX: [vmui](https://docs.victoriametrics.com/#vmui): fix the graph dragging for Firefox and Safari. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5764).
vmui: fix handling invalid timezone (#5758) * vmui: fix handling invalid timezone (#5732) * vmui: switch browser timezone flag to isValid --------- Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-02-06 21:47:30 +01:00
* BUGFIX: [vmui](https://docs.victoriametrics.com/#vmui): fix handling invalid timezone. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5732).
vmui: improve select component functionality (#5755) * vmui: fix select closing on click outside (#5728) * vmui: clear entered text in select after selecting a value (#5727) --------- Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-02-06 21:50:04 +01:00
* BUGFIX: [vmui](https://docs.victoriametrics.com/#vmui): fix the bug where the select does not open. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5728).
* BUGFIX: [vmui](https://docs.victoriametrics.com/#vmui): clear entered text in select after selecting a value. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5727).
vmui: improve the context for autocomplete #5736 #5737 #5739 (#5804) Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-02-14 01:22:51 +01:00
* BUGFIX: [vmui](https://docs.victoriametrics.com/#vmui): improve the operation of the context for autocomplete. See [this](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5736), [this](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5737) and [this](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5739) issues.
dashboards: follow-up https://github.com/VictoriaMetrics/VictoriaMetrics/commit/4369bc1df2260e0e48657aad156534e3352a7657 * add more details to changelog * simplify panels description * remove capacity planning recommendation, as it proves it incompetent Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-08 09:51:43 +01:00
* BUGFIX: [dashboards](https://grafana.com/orgs/victoriametrics): update `Storage full ETA` panels for Single-node and Cluster dashboards to prevent them from showing negative or blank results caused by increase of deduplicated samples. Deduplicated samples were part of the expression to provide a better estimate for disk usage, but due to sporadic nature of [deduplication](https://docs.victoriametrics.com/#deduplication) in VictoriaMetrics it rather produced skewed results. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5747).
vendor: update github.com/VictoriaMetrics/metricsql from v0.70.0 to v0.70.1 This should help with the https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5604
2024-02-06 20:52:32 +01:00
docs: change header from h1 to h2 1.97.2. The markdown requires the proper structure in hierachy of title so h1 can not be a child of h1,h2... only be a separate item, in our structure title is the parent h1 Signed-off-by: Artem Navoiev <tenmozes@gmail.com>
2024-02-21 16:15:41 +01:00
## [v1.97.2](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.97.2)
docs/CHANGELOG.md: document v1.97.2 LTS release
2024-02-14 17:50:50 +01:00
Released at 2024-02-14
**v1.97.x is a line of LTS releases (e.g. long-time support). It contains important up-to-date bugfixes for [VictoriaMetrics enterprise](https://docs.victoriametrics.com/enterprise.html).
All these fixes are also included in [the latest community release](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest).
The v1.97.x line will be supported for at least 12 months since [v1.97.0](https://docs.victoriametrics.com/CHANGELOG.html#v1970) release**
* SECURITY: upgrade Go builder from Go1.21.6 to Go1.22.0. See [the list of issues addressed in Go1.21.7](https://github.com/golang/go/issues?q=milestone%3AGo1.21.7+label%3ACherryPickApproved),
plus [the changelog for Go1.22.0](https://go.dev/doc/go1.22).
docs: re-classify change of default http timeout to bugfix The change introduced in https://github.com/VictoriaMetrics/VictoriaMetrics/commit/d8c1db7953d2265c9cd3a2913f12aac07a99a45c#diff-2bfab3db5cc1baf4c6d3ff6b19901926e3bdf4411ec685dac973e5fcff1c723b was backported to v1.97.2. Therefore, it is a `bugfix` and should be explicitly mentioned in the changelog of v1.97.2 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-02-22 21:57:39 +01:00
* BUGFIX: all VictoriaMetrics components: do not close connections to `-httpListenAddr` every 2 minutes. This behavior didn't help spreading load among multiple backend servers behind load-balancing TCP proxy. Instead, it could lead to hard-to-debug issues like [this one](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1304#issuecomment-1636997037). If you still need periodically closing client connections because of some reason, then pass the desired timeout to `-http.connTimeout` command-line flag.
docs/CHANGELOG.md: document v1.97.2 LTS release
2024-02-14 17:50:50 +01:00
* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): reduce CPU usage when `-promscrape.dropOriginalLabels` command-line flag is set. This issue has been introduced in [v1.96.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.96.0) when addressing [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5389).
* BUGFIX: [vmauth](https://docs.victoriametrics.com/vmauth.html): properly release memory during config reload. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4690).
* BUGFIX: [vmauth](https://docs.victoriametrics.com/vmauth.html): properly expose `vmauth_unauthorized_user_concurrent_requests_capacity`, `vmauth_unauthorized_user_concurrent_requests_current`, `vmauth_user_concurrent_requests_capacity` and `vmauth_user_concurrent_requests_current` [metrics](https://docs.victoriametrics.com/vmauth.html#monitoring) after [config reload](https://docs.victoriametrics.com/vmauth.html#config-reload). Previously these metrics didn't work after config reload.
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly propagate [label filters](https://docs.victoriametrics.com/keyconcepts/#filtering) from multiple arguments passed to [aggregate functions](https://docs.victoriametrics.com/metricsql/#aggregate-functions). For example, `sum({job="foo"}, {job="bar"}) by (job) + a` was improperly optimized to `sum({job="foo"}, {job="bar"}) by (job) + a{job="foo"}` before being executed. This could lead to unexpected results. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5604).
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly handle precision errors when calculating [changes](https://docs.victoriametrics.com/metricsql/#changes), [changes_prometheus](https://docs.victoriametrics.com/metricsql/#changes_prometheus), [increases_over_time](https://docs.victoriametrics.com/metricsql/#increases_over_time) and [resets](https://docs.victoriametrics.com/metricsql/#resets) functions. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/767).
* BUGFIX: properly store [staleness markers](https://docs.victoriametrics.com/vmagent/#prometheus-staleness-markers) for [self-scraped metrics](https://docs.victoriametrics.com/#monitoring) on single-node VictoriaMetrics shutdown. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/943).
* BUGFIX: prevent from possible `too big indexBlockSize` panic when samples with too long label values (~64Kb) are ingested into VictoriaMetrics.
docs/CHANGELOG.md: cut v1.97.1
2024-02-01 14:08:40 +01:00
## [v1.97.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.97.1)
Released at 2024-02-01
docs: mark v1.97.x as long-term support release
2024-02-01 14:16:19 +01:00
**v1.97.x is a line of LTS releases (e.g. long-time support). It contains important up-to-date bugfixes for [VictoriaMetrics enterprise](https://docs.victoriametrics.com/enterprise.html).
All these fixes are also included in [the latest community release](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest).
The v1.97.x line will be supported for at least 12 months since [v1.97.0](https://docs.victoriametrics.com/CHANGELOG.html#v1970) release**
lib/promauth: follow-up for fca3b14b7b8ea8367603e02d497f5ae208a3fba2 - Simplify the code for handling BasicAuthConfig at lib/promauth/config.go - Move the description of the change into correct place at docs/CHANGELOG.md - Put tests for username in front of tests for password at lib/promauth/config_test.go Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5720 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5511
2024-01-31 18:45:13 +01:00
* FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): add support for `username_file` option at `basic_auth` section in [`scrape_configs`](https://docs.victoriametrics.com/sd_configs/#http-api-client-options). See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5511). Thanks to @wasim-nihal for [the initial implementation](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5720).
lib/prompbmarshal: return back custom protobuf marshaler for lib/prompbmarshal.WriteRequest The easyproto-based marshaler is 2x slower than the previous custom marshaler, so let's stick with it. This improves the performance for sending data to remote storage at vmagent and reduces CPU usage to pre-v1.97.0 levels.
2024-02-01 05:33:03 +01:00
* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): fix the increased CPU usage when sending the data to remote storage. The issue has been introduced in [v1.97.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.97.0).
app/vmselect/netstorage: properly handle the case when an empty brsPool points to the end of brs.brs This case is possible after a new brsPool is allocated. The fix is to verify whether len(brsPool) >= len(brs.brs) before trying to append a new item to brsPool and sharing its contents with brs.brs. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5733
2024-01-31 09:25:53 +01:00
* BUGFIX: fix `runtime error: slice bounds out of range` panic, which can occur during query execution. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5733). The bug has been introduced in `v1.97.0`.
app/vmselect/promql: really keep metric names when keep_metric_names modifier is applied to binary operator Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5556
2024-01-31 01:32:02 +01:00
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly handle `avg_over_time({some_filter}[d]) keep_metric_names` queries, where [`some_filter`](https://docs.victoriametrics.com/keyconcepts/#filtering) matches multiple time series with multiple names, while `d` is bigger or equal to `3h`. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5556).
docs/CHANGELOG.md: add missing links to the corresponding dashboards
2024-02-05 09:55:30 +01:00
* BUGFIX: [dashboards/single](https://grafana.com/grafana/dashboards/10229): fix typo in query for `version` annotation which falsely produced many version change events.
app/vmselect/promql: really keep metric names when keep_metric_names modifier is applied to binary operator Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5556
2024-01-31 01:32:02 +01:00
docs/CHANGELOG.md: cut v1.97.0
2024-01-30 21:45:04 +01:00
## [v1.97.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.97.0)
Released at 2024-01-30
docs: mark v1.97.x as long-term support release
2024-02-01 14:16:19 +01:00
**v1.97.x is a line of LTS releases (e.g. long-time support). It contains important up-to-date bugfixes for [VictoriaMetrics enterprise](https://docs.victoriametrics.com/enterprise.html).
All these fixes are also included in [the latest community release](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/latest).
The v1.97.x line will be supported for at least 12 months since [v1.97.0](https://docs.victoriametrics.com/CHANGELOG.html#v1970) release**
deployment/docker: upgrade base Docker image from Alpine 3.19.0 to 3.19.1 See https://www.alpinelinux.org/posts/Alpine-3.19.1-released.html
2024-01-30 21:47:14 +01:00
* SECURITY: upgrade base docker image (Alpine) from 3.19.0 to 3.19.1. See [alpine 3.19.1 release notes](https://www.alpinelinux.org/posts/Alpine-3.19.1-released.html).
deployment/docker: update Go builder from Go1.21.5 to Go1.21.6
2024-01-16 16:00:16 +01:00
* SECURITY: upgrade Go builder from Go1.21.5 to Go1.21.6. See [the list of issues addressed in Go1.21.6](https://github.com/golang/go/issues?q=milestone%3AGo1.21.6+label%3ACherryPickApproved).
lib/mergeset: really limit the number of in-memory parts to 15 It has been appeared that the registration of new time series slows down linearly with the number of indexdb parts, since VictoriaMetrics needs to check every indexdb part when it searches for TSID by newly ingested metric name. The number of in-memory parts grows when new time series are registered at high rate. The number of in-memory parts grows faster on systems with big number of CPU cores, because the mergeset maintains per-CPU buffers with newly added entries for the indexdb, and every such entry is transformed eventually into a separate in-memory part. The solution has been suggested in https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5212 by @misutoth - to limit the number of in-memory parts with buffered channel. This solution is implemented in this commit. Additionally, this commit merges per-CPU parts into a single part before adding it to the list of in-memory parts. This reduces CPU load when searching for TSID by newly ingested metric name. The https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5212 recommends setting the limit on the number of in-memory parts to 100, but my internal testing shows that much lower limit 15 works with the same efficiency on a system with 16 CPU cores while reducing memory usage for `indexdb/dataBlocks` cache by up to 50%. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5190
2024-01-24 02:27:49 +01:00
* FEATURE: improve new [time series](https://docs.victoriametrics.com/keyConcepts.html#time-series) registration speed on systems with high number of CPU cores. Thanks to @misutoth for the initial idea and [implementation](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5212).
lib/{mergeset,storage}: make background merge more responsive and scalable - Maintain a separate worker pool per each part type (in-memory, file, big and small). Previously a shared pool was used for merging all the part types. A single merge worker could merge parts with mixed types at once. For example, it could merge simultaneously an in-memory part plus a big file part. Such a merge could take hours for big file part. During the duration of this merge the in-memory part was pinned in memory and couldn't be persisted to disk under the configured -inmemoryDataFlushInterval . Another common issue, which could happen when parts with mixed types are merged, is uncontrolled growth of in-memory parts or small parts when all the merge workers were busy with merging big files. Such growth could lead to significant performance degradataion for queries, since every query needs to check ever growing list of parts. This could also slow down the registration of new time series, since VictoriaMetrics searches for the internal series_id in the indexdb for every new time series. The third issue is graceful shutdown duration, which could be very long when a background merge is running on in-memory parts plus big file parts. This merge couldn't be interrupted, since it merges in-memory parts. A separate pool of merge workers per every part type elegantly resolves both issues: - In-memory parts are merged to file-based parts in a timely manner, since the maximum size of in-memory parts is limited. - Long-running merges for big parts do not block merges for in-memory parts and small parts. - Graceful shutdown duration is now limited by the time needed for flushing in-memory parts to files. Merging for file parts is instantly canceled on graceful shutdown now. - Deprecate -smallMergeConcurrency command-line flag, since the new background merge algorithm should automatically self-tune according to the number of available CPU cores. - Deprecate -finalMergeDelay command-line flag, since it wasn't working correctly. It is better to run forced merge when needed - https://docs.victoriametrics.com/#forced-merge - Tune the number of shards for pending rows and items before the data goes to in-memory parts and becomes visible for search. This improves the maximum data ingestion rate and the maximum rate for registration of new time series. This should reduce the duration of data ingestion slowdown in VictoriaMetrics cluster on e.g. re-routing events, when some of vmstorage nodes become temporarily unavailable. - Prevent from possible "sync: WaitGroup misuse" panic on graceful shutdown. This is a follow-up for fa566c68a6ccf7385a05f649aee7e5f5a38afb15 . Thanks @misutoth to for the inspiration at https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5212 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5190 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3790 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3551 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3337 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3425 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3647 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3641 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/648 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/291
2024-01-26 21:39:49 +01:00
* FEATURE: make [background merge](https://docs.victoriametrics.com/#storage) more responsive and scalable. This should help the following issues: [5190](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5190), [3425](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3425), [648](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/648).
docs/CHANGELOG.md: fix a link in the description of 70cd09e736752d8b22697b57e24d600bcf358fee Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5581
2024-01-16 19:54:39 +01:00
* FEATURE: [graphite](https://docs.victoriametrics.com/#graphite-render-api-usage): add support for negative index in `groupByNode` and `aliasByNode` functions. Thanks to @rbizos for [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5581).
docs/CHANGELOG.md: document the enhancement, which reduces initial memory usage when `vmagent` scrapes targets with large responses Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5567
2024-01-30 19:51:04 +01:00
* FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): add support for discovering [Hetzner Cloud](https://www.hetzner.com/cloud) and [Hetzner Robot](https://docs.hetzner.com/robot) scrape targets. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3154) and [these docs](https://docs.victoriametrics.com/sd_configs.html#hetzner_sd_configs).
lib/protoparser/datadogv2: add support for reading protobuf-encoded requests at /api/v2/series endpoint Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4451 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5094
2024-01-14 20:06:01 +01:00
* FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): add support for [DataDog v2 data ingestion protocol](https://docs.datadoghq.com/api/latest/metrics/#submit-metrics). See [these docs](https://docs.victoriametrics.com/#how-to-send-data-from-datadog-agent) and [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4451).
docs/CHANGELOG.md: document the enhancement, which reduces initial memory usage when `vmagent` scrapes targets with large responses Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5567
2024-01-30 19:51:04 +01:00
* FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): reduce initial memory usage when scraping targets, which return huge responses (for example, [kube-state-metrics](https://github.com/kubernetes/kube-state-metrics) in large Kubernetes cluster may return 100MB+ responses), without the need to explicitly enable [stream parsing mode](https://docs.victoriametrics.com/vmagent/#stream-parsing-mode). See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5567).
app/{vmagent,vmalert}: add the ability to set OAuth2 endpoint params via the corresponding *.oauth2.endpointParams command-line flags This is a follow-up for 5ebd5a0d7b12ac8c8ba6282ac5be16a193d5239d Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5427
2023-12-20 20:35:16 +01:00
* FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): expose ability to set OAuth2 endpoint parameters per each `-remoteWrite.url` via the command-line flag `-remoteWrite.oauth2.endpointParams`. See [these docs](https://docs.victoriametrics.com/vmagent.html#advanced-usage). Thanks to @mhill-holoplot for the [pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5427).
lib/promscrape/discovery/kubernetes: add -promscrape.kubernetes.attachNodeMetadataAll command-line flag This flag allows setting attach_metadata.node=true for all the kubernetes_sd_configs defined at -promscrape.config Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4640 Thanks to wasim-nihal for the initial implementation at https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5593
2024-01-21 02:12:52 +01:00
* FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): add ability to set `attach_metadata.node=true` option for all the [`kubernetes_sd_configs`](https://docs.victoriametrics.com/sd_configs.html#kubernetes_sd_configs) defined at [`-promscrape.config`](https://docs.victoriametrics.com/vmagent.html#quick-start) via `-promscrape.kubernetes.attachNodeMetadataAll` command-line flag. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4640). Thanks to @wasim-nihal for [the initial implementation](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5593).
lib/streamaggr: skip unfinished aggregation state on shutdown by default (#5689) Sending unfinished aggregate states tend to produce unexpected anomalies with lower values than expected. The old behavior can be restored by specifying `flush_on_shutdown: true` setting in streaming aggregation config Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-01-26 22:45:23 +01:00
* FEATURE: [vmagent](https://docs.victoriametrics.com/vmagent.html): do not send unfinished [aggregation state](https://docs.victoriametrics.com/stream-aggregation.html) on shutdown or [hot config reload](https://docs.victoriametrics.com/stream-aggregation.html#configuration-update) by default, as it tend to produce unexpected anomalies with lower values. The old behavior can be restored by specifying `flush_on_shutdown: true` setting in streaming aggregation config. See more details [here](https://docs.victoriametrics.com/stream-aggregation.html#aggregation-outputs).
lib/streamaggr: expand `%{ENV}` placeholders in stream aggregation configs
2024-01-24 11:31:27 +01:00
* FEATURE: [streaming aggregation](https://docs.victoriametrics.com/stream-aggregation.html): expand `%{ENV_VAR}` placeholders in config files with the corresponding environment variable values.
app/{vmagent,vmalert}: add the ability to set OAuth2 endpoint params via the corresponding *.oauth2.endpointParams command-line flags This is a follow-up for 5ebd5a0d7b12ac8c8ba6282ac5be16a193d5239d Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5427
2023-12-20 20:35:16 +01:00
* FEATURE: [vmalert](https://docs.victoriametrics.com/vmagent.html): expose ability to set OAuth2 endpoint parameters via the following command-line flags:
- `-datasource.oauth2.endpointParams` for `-datasource.url`
- `-notifier.oauth2.endpointParams` for `-notifier.url`
- `-remoteRead.oauth2.endpointParams` for `-remoteRead.url`
- `-remoteWrite.oauth2.endpointParams` for `-remoteWrite.url`
app/vmauth: add ability to route requests to different backends depending on the request host
2023-12-13 23:46:36 +01:00
* FEATURE: [vmauth](https://docs.victoriametrics.com/vmauth.html): add ability to proxy incoming requests to different backends based on the requested host via `src_hosts` option at `url_map`. See [these docs](https://docs.victoriametrics.com/vmauth.html#generic-http-proxy-for-different-backends).
app/vmauth: adds metric_labels and backend_errors counter (#5585) * app/vmauth: adds metric_labels and backend_errors counter it must improve observability for user requests with new metric - per user backend errors counter. it's needed to calculate requests fail rate to the configured backends. metric_labels configuration allows to perform additional aggregations on top of multiple users from configuration section. It could be multiple clients or clients with separate read/write tokens https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5565 * wip --------- Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-01-21 03:40:52 +01:00
* FEATURE: [vmauth](https://docs.victoriametrics.com/vmauth.html): expose `vmauth_user_request_backend_errors_total` and `vmauth_unauthorized_user_request_backend_errors_total` [metrics](https://docs.victoriametrics.com/vmauth.html#monitoring), which track the number of failed requests because of backend errors. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5565).
* FEATURE: [vmauth](https://docs.victoriametrics.com/vmauth.html): add an ability to specify additional labels for [per-user metrics](https://docs.victoriametrics.com/vmauth.html#monitoring) via `metric_labels` section. See [this feature request](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5565).
app/vmselect: abort streaming connections for vmselect (#5650) * app/vmselect: abort streaming connections for vmselect due to streaming nature of export APIs, curl and simmilr tools cannot detect errors that happened after http.Header with status 200 was written to it. This PR tracks if body write was already started and closes connection. It allows client to detect not expected chunk sequence and return error to the caller. Mostly it affects vmselect at cluster version https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5645 * wip Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5645 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5650 --------- Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-01-21 01:12:51 +01:00
* FEATURE: all VictoriaMetrics components: break HTTP client connection if an error occurs after the server at `-httpListenAddr` already sent response status code. Previously such an error couldn't be detected at client side. Now the client will get an error about invalid chunked response. The error message is simultaneously written to the server log and in the last line of the response. This should help detecting errors when migrating data between VictoriaMetrics instances by [vmctl](https://docs.victoriametrics.com/vmctl.html). See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5645).
lib/pushmetrics: add -pushmetrics.header and -pushmetrics.disableCompression command-line flags
2023-12-17 18:56:46 +01:00
* FEATURE: all VictoriaMetrics components: add ability to specify arbitrary HTTP headers to send with every request to `-pushmetrics.url`. See [`push metrics` docs](https://docs.victoriametrics.com/#push-metrics).
all: add -metrics.exposeMetadata command-line flag, which can be used for adding TYPE and HELP metadata for metrics exposed at /metrics page This may be needed for systems, which require this metadata such as Google Cloud Managed Prometheus. See https://cloud.google.com/stackdriver/docs/managed-prometheus/troubleshooting#missing-metric-type
2023-12-19 02:19:42 +01:00
* FEATURE: all VictoriaMetrics components: add `-metrics.exposeMetadata` command-line flag, which allows displaying `TYPE` and `HELP` metadata at `/metrics` page exposed at `-httpListenAddr`. This may be needed when the `/metrics` page is scraped by collector, which requires the `TYPE` and `HELP` metadata such as [Google Cloud Managed Prometheus](https://cloud.google.com/stackdriver/docs/managed-prometheus/troubleshooting#missing-metric-type).
all: allow dynamically reading *AuthKey flag values from files and urls Examples: 1) -metricsAuthKey=file:///abs/path/to/file - reads flag value from the given absolute filepath 2) -metricsAuthKey=file://./relative/path/to/file - reads flag value from the given relative filepath 3) -metricsAuthKey=http://some-host/some/path?query_arg=abc - reads flag value from the given url The flag value is automatically updated when the file contents changes.
2024-01-21 20:58:26 +01:00
* FEATURE: all VictoriaMetrics components: add ability to dynamically re-read auth keys and passwords from files and urls when using `file:///path/to/file` or `http://host/path` syntax for the following command-line flags: `-configAuthKey`, `-deleteAuthKey`, `-flagsAuthKey`, `-forceMergeAuthKey`, `-forceFlushAuthKey`, `-httpAuth.password`, `-metricsAuthKey`, `-pprofAuthKey`, `-reloadAuthKey`, `-search.resetCacheAuthKey`, `-snapshotAuthKey`. For example, `-httpAuth.password=file:///path/to/password`. See [these docs](https://docs.victoriametrics.com/#security) for details.
docs/CHANGELOG.md: add missing links to the corresponding dashboards
2024-02-05 09:55:30 +01:00
* FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): add panels for detailed visualization of traffic usage between vmstorage, vminsert, vmselect components and their clients. New panels are available in the rows dedicated to specific components.
* FEATURE: [dashboards/cluster](https://grafana.com/grafana/dashboards/11176): update "Slow Queries" panel to show percentage of the slow queries to the total number of read queries served by vmselect. The percentage value should make it more clear for users whether there is a service degradation.
* FEATURE: [dashboards/single](https://grafana.com/grafana/dashboards/10229): change dashboard title from `VictoriaMetrics` to `VictoriaMetrics - single-node`. The new title should provide better understanding of this dashboard purpose.
app/vmselect: abort streaming connections for vmselect (#5650) * app/vmselect: abort streaming connections for vmselect due to streaming nature of export APIs, curl and simmilr tools cannot detect errors that happened after http.Header with status 200 was written to it. This PR tracks if body write was already started and closes connection. It allows client to detect not expected chunk sequence and return error to the caller. Mostly it affects vmselect at cluster version https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5645 * wip Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5645 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5650 --------- Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-01-21 01:12:51 +01:00
* FEATURE: [vmctl](https://docs.victoriametrics.com/vmctl.html): rename cmd-line flag `vm-native-disable-retries` to `vm-native-disable-per-metric-migration` to better reflect its meaning.
* FEATURE: [vmctl](https://docs.victoriametrics.com/vmctl.html): add `-vm-native-src-insecure-skip-verify` and `-vm-native-dst-insecure-skip-verify` command-line flags for native protocol. It can be used for skipping TLS certificate verification when connecting to the source or destination addresses.
deployment/alerts: add `job` label to `DiskRunsOutOfSpace` alerting rule So it is easier to understand to which installation the triggered instance belongs. Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-01-16 09:49:39 +01:00
* FEATURE: [Alerting rules for VictoriaMetrics](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/master/deployment/docker#alerts): add `job` label to `DiskRunsOutOfSpace` alerting rule, so it is easier to understand to which installation the triggered instance belongs.
lib/storage: print tenant ID in log when discarding or truncating labels (#5658) Previously, it was not possible to determine which tenant sends metrics with excessive amount of labels of label values. Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-01-23 01:27:59 +01:00
* FEATURE: `vmstorage`: add tenant identifier for log messages regarding dropping excessive labels due to limits defined by `-maxLabelsPerTimeseries` or `-maxLabelValueLen` command-line flags. Previously, it was hard to understand to which tenant the dropped labels belong.
vmui: query report (#5497) * vmui: add query analyzer page * vmui: fix tabs for query analyzer * vmui: add help to export query * vmui: add time params to query analyzer * docs/vmui: add query analyzer * vmui: fix validation JSON form --------- Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-01-23 03:23:26 +01:00
* FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): add the ability to export and import query reports:
- add a `Query Analyzer` page that allows you to build graphs from `JSON` data containing the results of executing a query request.
- add an `Export query` button to the graph that saves the result of executing the query in `JSON`. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5497).
vmui: add flag for default timezone setting (#5611) * vmui: add flag for default timezone setting #5375 * vmui: validate timezone before client return * Update app/vmselect/vmui.go --------- Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-01-23 03:11:19 +01:00
* FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): add `-vmui.defaultTimezone` flag to set a default timezone. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5375) and [these docs](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/master/app/vmui#timezone-configuration).
* FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): include UTC in the timezone selection dropdown for standardized time referencing. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5375).
vmui: add the ability to expand all tracing entries (#5677) (#5726)
2024-01-30 20:10:10 +01:00
* FEATURE: [vmui](https://docs.victoriametrics.com/#vmui): add the ability to expand/collapse all tracing entries and download tracing data in .json format. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5677).
deployment/docker: add grafana datasource to the docker-compose files (#5363) https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3920 https://github.com/VictoriaMetrics/grafana-datasource/issues/113
2024-01-22 15:45:31 +01:00
* FEATURE: add [VictoriaMetrics datasource](https://github.com/VictoriaMetrics/grafana-datasource) to docker compose environment. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5363).
docs/CHANGELOG.md: cut v1.96.0 release
2023-12-12 23:42:56 +01:00
lib/storage: do not check the limit for -search.maxUniqueTimeseries when performing /api/v1/labels and /api/v1/label/.../values requests This limit has little sense for these APIs, since: - Thses APIs frequently result in scanning of all the time series on the given time range. For example, if extra_filters={datacenter="some_dc"} . - Users expect these APIs shouldn't hit the -search.maxUniqueTimeseries limit, which is intended for limiting resource usage at /api/v1/query and /api/v1/query_range requests. Also limit the concurrency for /api/v1/labels, /api/v1/label/.../values and /api/v1/series requests in order to limit the maximum memory usage and CPU usage for these API. This limit shouldn't affect typical use cases for these APIs: - Grafana dashboard load when dashboard labels should be loaded - Auto-suggestion list load when editing the query in Grafana or vmui Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5055
2024-01-29 15:50:15 +01:00
* BUGFIX: properly return the list of matching label names and label values from [`/api/v1/labels`](https://docs.victoriametrics.com/url-examples.html#apiv1labels) and [`/api/v1/label/.../values`](https://docs.victoriametrics.com/url-examples.html#apiv1labelvalues) when the database contains more than `-search.maxUniqueTimeseries` unique [time series](https://docs.victoriametrics.com/keyConcepts.html#time-series) on the selected time range. Previously VictoriaMetrics could return `the number of matching timeseries exceeds ...` error in this case. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5055).
app/vmselect/netstorage (#5649) * app/vmselect/netstorage correctly handle errGlobal set * wip Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5649 --------- Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-01-21 01:47:29 +01:00
* BUGFIX: properly return errors from [export APIs](https://docs.victoriametrics.com/#how-to-export-time-series). Previously these errors were silently suppressed. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5649).
app/vmselect/netstorage: make sure that at least a single result is collected from every storage group before deciding whether it is OK to skip results from the remaining storage nodes
2023-12-20 18:53:46 +01:00
* BUGFIX: [VictoriaMetrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html): properly return full results when `-search.skipSlowReplicas` command-line flag is passed to `vmselect` and when [vmstorage groups](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#vmstorage-groups-at-vmselect) are in use. Previously partial results could be returned in this case.
lib/protoparser/opentelemetry: allow ingesting metrics without resource labels Some clients may ingest samples via OpenTelemetry protocol without Resource labels. Previously VictoriaMetrics was silently dropping such samples. The commit 317834f876747843f38ee770af352cd83e67e047 added vm_protoparser_rows_dropped_total{type="opentelemetry",reason="resource_not_set"} counter for tracking of such dropped samples. See https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5459 It is better from usability PoV to accept such samples instead of dropping them and incrementing the corresponding counter.
2023-12-17 18:05:22 +01:00
* BUGFIX: `vminsert`: properly accept samples via [OpenTelemetry data ingestion protocol](https://docs.victoriametrics.com/#sending-data-via-opentelemetry) when these samples have no [resource attributes](https://opentelemetry.io/docs/instrumentation/go/resources/). Previously such samples were silently skipped.
app/vmstorage: addd missing -inmemoryDataFlushInterval command-line flag Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3337
2023-12-14 19:47:45 +01:00
* BUGFIX: `vmstorage`: added missing `-inmemoryDataFlushInterval` command-line flag, which was missing in [VictoriaMetrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html) after implementing [this feature](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3337) in [v1.85.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.85.0).
lib/storage: follow-up for 4b8088e377d1d7c09f9914edd9121962c65e2e84 - Clarify the bugfix description at docs/CHANGELOG.md - Simplify the code by accessing prefetchedMetricIDs struct under the lock instead of using lockless access to immutable struct. This shouldn't worsen code scalability too much on busy systems with many CPU cores, since the code executed under the lock is quite small and fast. This allows removing cloning of prefetchedMetricIDs struct every time new metric names are pre-fetched. This should reduce load on Go GC, since the cloning of uin64set.Set struct allocates many new objects.
2024-01-16 14:26:08 +01:00
* BUGFIX: `vmstorage`: properly expire `storage/prefetchedMetricIDs` cache. Previously this cache was never expired, so it could grow big under [high churn rate](https://docs.victoriametrics.com/FAQ.html#what-is-high-churn-rate). This could result in increasing CPU load over time.
docs/CHANGELOG.md: move the description of the bugfix from 9253c24dd651e8f2e55f07e9c22412aa34a17c49 into correct place The description of the bugfix was incorrectly placed in already released v1.96.0, while it should be placed in tip. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5450
2023-12-17 17:58:39 +01:00
* BUGFIX: [vmalert](https://docs.victoriametrics.com/vmalert.html): check `-external.url` schema when starting vmalert, must be `http` or `https`. Before, alertmanager could reject alert notifications if `-external.url` contained no or wrong schema.
vmalert: automatically add `exported_` prefix for original evaluation… (#5398) automatically add `exported_` prefix for original evaluation result label if it's conflicted with external or reserved one, previously it was overridden. https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5161 Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 1f477aba419e4287b829318f14c45063cd5d0c94)
2023-12-22 16:07:47 +01:00
* BUGFIX: [vmalert](https://docs.victoriametrics.com/vmalert.html): automatically add `exported_` prefix for original evaluation result label if it's conflicted with external or reserved one, previously it was overridden. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5161).
app/vmalert: fix data race during hot-config reload (#5698) * app/vmalert: fix data race during hot-config reload During hot-reload, the logic evokes the group update and rules evaluation interruption simultaneously. Falsely assuming that interruption happens before the update. However, it could happen that group will be updated first and only after the rules evaluation will be cancelled. Which will result in permanent interruption for all rules within the group. The fix caches the cancel context function into local variable first. And only after performs the group update. With cached cancel function we can safely call it without worrying that we cancel the evaluation for already updated group. Signed-off-by: hagen1778 <roman@victoriametrics.com> * Revert "app/vmalert: fix data race during hot-config reload" This reverts commit a4bb7e8932c998ca0f3c7bd2da1a6d4da10fe1a1. * app/vmalert: fix data race during hot-config reload During hot-reload, the logic evokes the group update and rules evaluation interruption simultaneously. Falsely assuming that interruption happens before the update. However, it could happen that group will be updated first and only after the rules evaluation will be cancelled. Which will result in permanent interruption for all rules within the group. The fix cancels the evaulation context before applying the update, making sure that the context will be cancelled for old group always. Signed-off-by: hagen1778 <roman@victoriametrics.com> * wip Signed-off-by: hagen1778 <roman@victoriametrics.com> --------- Signed-off-by: hagen1778 <roman@victoriametrics.com>
2024-01-26 22:42:21 +01:00
* BUGFIX: [vmalert](https://docs.victoriametrics.com/vmalert.html): autogenerate `ALERTS_FOR_STATE` time series for alerting rules with `for: 0`. Previously, `ALERTS_FOR_STATE` was generated only for alerts with `for > 0`. The change aligns with Prometheus behavior. See more details in [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5648).
* BUGFIX: [vmalert](https://docs.victoriametrics.com/vmalert.html): fix data race during hot-config reload. The result of the race could cause all rules from updated group to fail with `context cancelled` error.
app/vmselect/promql: consistently sort results of `a or b` query Previously the order of results returned from `a or b` query could change with each request because the sorting for such query has been disabled in order to satisfy https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4763 . This commit executes `a or b` query as `sortByMetricName(a) or sortByMetricName(b)`. This makes the order of returned time series consistent across requests, while maintaining the requirement from https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4763 , e.g. `b` results are consistently put after `a` results. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5393
2024-01-16 00:30:07 +01:00
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): consistently sort results for `q1 or q2` query, so they do not change colors with each refresh in Grafana. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5393).
app/vmselect/promql: follow-up for ce4f26db02d487cfc8d1605b472f8968e41bc8b3 - Document the bugfix at docs/CHANGELOG.md - Filter out NaN values before sorting as suggested at https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5509#discussion_r1447369218 - Revert unrelated changes in lib/filestream and lib/fs - Use simpler test at app/vmselect/promql/exec_test.go Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5509 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5506
2024-01-16 01:55:06 +01:00
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly return results from [bottomk](https://docs.victoriametrics.com/MetricsQL.html#bottomk) and `bottomk_*()` functions when some of these results contain NaN values. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5506). Thanks to @xiaozongyang for [the fix](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5509).
docs/CHANGELOG.md: typo fix: use proper backtick closing quote instead of single quote
2023-12-17 18:28:15 +01:00
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly handle queries, which wrap [rollup functions](https://docs.victoriametrics.com/MetricsQL.html#rollup-functions) with multiple arguments without explicitly specified lookbehind window in square brackets into [aggregate functions](https://docs.victoriametrics.com/MetricsQL.html#aggregate-functions). For example, `sum(quantile_over_time(0.5, process_resident_memory_bytes))` was resulting to `expecting at least 2 args to ...; got 1 args` error. Thanks to @atykhyy for [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5414).
* BUGFIX: [vmctl](https://docs.victoriametrics.com/vmctl.html): retry on import errors in `vm-native` mode. Before, retries happened only on writes into a network connection between source and destination. But errors returned by server after all the data was transmitted were logged, but not retried.
lib/awsapi: properly assume role with webIdentity token (#5495) * lib/awsapi: properly assume role with webIdentity token introduce new irsaRoleArn param for config. It's only needed for authorization with webIdentity token. First credentials obtained with irsa role and the next sts assume call for an actual roleArn made with those credentials. Common use case for it - cross AWS accounts authorization https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3822 * wip --------- Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2023-12-20 18:05:39 +01:00
* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): properly assume role with [AWS IRSA authorization](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html). Previously role chaining was not supported. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3822) for details.
exit vmagent if there is config syntax error in `scrape_config_files` when `-promscrape.config.strictParse=true` (#5560)
2024-01-16 10:30:02 +01:00
* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): exit if there is config syntax error in [`scrape_config_files`](https://docs.victoriametrics.com/vmagent.html#loading-scrape-configs-from-multiple-files) when `-promscrape.config.strictParse=true`. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5508).
lib/promscrape/discovery/kubernetes: fix watcher start order for roles endpoints and endpointslice (#5557) * lib/promscrape/discovery/kubernetes: fix watcher start order for roles endpoints and endpointslice Previously the groupWatcher could be mistakenly stopped when requests for pod or services resources take too long. * remove mislead comment * docs/sd_configs.md: mention -promscrape.kubernetes.attachNodeMetadataAll flag in the description for attach_metadata section Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4640 * wip * lib/promscrape/kubernetes: prevent from stopping groupWatcher when there are in-flight apiWatcher.mustStart() calls groupWatcher is stopped if it has zero registered apiWatchers during 14 seconds. But such a groupWatcher can be still in use if apiWatcher for `role: endpoints` or `role: endpointslice` is being registered and the discovery of the associated `pod` and/or `service` objects takes longer than 14 seconds - see the beginning of groupWatcher.startWatchersForRole() function for details. Track the number of in-flight calls to apiWatcher.mustStart() and prevent from stopping the associated groupWatcher if the number of in-flight calls is non-zero. P.S. postponing the discovery of `pod` and/or `service` objects associated with `endpoints` or `endpointslice` roles isn't the best solution, since it slows down initial discovery of `endpoints` and `endpointslice` targets. * typo fix --------- Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-01-21 22:13:15 +01:00
* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): properly discover targets for `role: endpoints` and `role: endpointslice` in [kubernetes_sd_configs](https://docs.victoriametrics.com/sd_configs.html#kubernetes_sd_configs). Previously some `endpoints` and `endpointslice` targets could be left undiscovered or some targets could have missing `__meta_*` labels when performing service discovery in busy Kubernetes clusters with large number of pods. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5557).
lib/promscrape: respect `0` value for `series_limit` param (#5663) * lib/promscrape: respect `0` value for `series_limit` param Respect `0` value for `series_limit` param in `scrape_config` even if global limit was set via `-promscrape.seriesLimitPerTarget`. Previously, `0` value will be ignored in favor of `-promscrape.seriesLimitPerTarget`. This behavior aligns with possibility to override `series_limit` value via relabeling with `__series_limit__` label. Signed-off-by: hagen1778 <roman@victoriametrics.com> * Update docs/CHANGELOG.md --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-01-23 12:09:14 +01:00
* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): respect explicitly set `series_limit: 0` in [scrape_config](https://docs.victoriametrics.com/sd_configs.html#scrape_configs). This allows removing [`series_limit` restriction](https://docs.victoriametrics.com/vmagent.html#cardinality-limiter) on a per-`scrape_config` basis when global limit is set via `-promscrape.seriesLimitPerTarget`. Previously, `0` value was ignored in favor of `-promscrape.seriesLimitPerTarget`.
lib/promscrape/discovery/kubernetes: do not generate targets for already terminated pods and containers Already terminated pods and containers cannot be scraped and will never resurrect, so there is zero sense in creating scrape targets for them.
2024-01-24 13:52:12 +01:00
* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): do not discover scrape targets for already terminated pods and containers in [`kubernetes_sd_configs`](https://docs.victoriametrics.com/sd_configs.html#kubernetes_sd_configs). Such pods and containers cannot be scraped and cannot resurrect, so there is no sense in generating scrape targets for them.
docs/CHANGELOG.md: refer to the related pull request for the bugfix for https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1945
2024-01-30 19:21:44 +01:00
* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): properly follow redirects to another hostnames when `follow_redirects: true` option is set in [`scrape_configs`](https://docs.victoriametrics.com/sd_configs/#http-api-client-options) while [stream parsing mode](https://docs.victoriametrics.com/vmagent/#stream-parsing-mode) is disabled. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1945) and [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/4931).
app/vmui: fix broken link for the statistic inaccuracy explanation (#5568) (cherry picked from commit 105c6b2eb7ca10ee750e633247aca549db735104)
2024-01-08 20:13:45 +01:00
* BUGFIX: [vmui](https://docs.victoriametrics.com/#vmui): fix a link for the statistic inaccuracy explanation in the cardinality explorer tool. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5460).
vmui: fix cache autocomplete (#5591) * vmui: fix the logic of closing the popper #5470 * vmui: fix the logic of caching autocomplete results #5472 --------- Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-01-23 03:06:14 +01:00
* BUGFIX: [vmui](https://docs.victoriametrics.com/#vmui): fix the display of autocomplete results and cache the results. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5472) and [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5470).
app/vmselect/promql: properly handle possible negative results caused… (#5608) * app/vmselect/promql: properly handle possible negative results caused by float operations precision error in rollup functions like rate() or increase() * fix test
2024-01-21 01:53:29 +01:00
* BUGFIX: [vmui](https://docs.victoriametrics.com/#vmui): send `step` param for instant queries. The change reverts [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3896) due to reasons explained in [this comment](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3896#issuecomment-1896704401).
vmui: fix `Enter` key in query field (#5667) (#5681)
2024-01-26 22:38:32 +01:00
* BUGFIX: [vmui](https://docs.victoriametrics.com/#vmui): fix the `Enter` key press issue in the `Query` field when using autocomplete. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5667).
lib/pushmetrics: wait until the background goroutines, which push metrics, are stopped at pushmetrics.Stop() Previously the was a race condition when the background goroutine still could try collecting metrics from already stopped resources after returning from pushmetrics.Stop(). Now the pushmetrics.Stop() waits until the background goroutine is stopped before returning. This is a follow-up for https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5549 and the commit fe2d9f6646a49c347b1ee03a0285971eaf681ed6 . Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5548
2024-01-15 12:37:02 +01:00
* BUGFIX: all: fix potential panic during components shutdown when [metrics push](https://docs.victoriametrics.com/#push-metrics) is configured. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5548). Thanks to @zhdd99 for the [pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5549).
app/vmselect: handle negative time range start in a generic manner inside NewSearchQuery() This is a follow-up for cf03e11d89f86e981432fa654f6d8f7b45b8bb43 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5553 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5630
2024-01-21 22:41:11 +01:00
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly process queries with too big lookbehind window such as `foo[100y]`. Previously, such queries could return empty responses even if `foo` is present in database. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5553).
app/vmselect/promql: properly handle possible negative results caused… (#5608) * app/vmselect/promql: properly handle possible negative results caused by float operations precision error in rollup functions like rate() or increase() * fix test
2024-01-21 01:53:29 +01:00
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly handle possible negative results caused by float operations precision error in rollup functions like rate() or increase(). See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5571).
vmsingle/vmselect returns http status 429 (TooManyRequests) instead of 503 (ServiceUnavailable) when max concurrent requests limit is reached. (#5682)
2024-01-24 17:55:06 +01:00
* BUGFIX: `vmselect`: vmsingle/vmselect returns http status 429 (TooManyRequests) instead of 503 (ServiceUnavailable) when max concurrent requests limit is reached.
app/vmselect: set proper timestamp for cached instant responses (#5723) * app/vmselect: set proper timestamp for cached instant responses The change updates `getSumInstantValues` to prefer timestamp from the most recent results. Before, timestamp from cached series was used. The old behavior had negative impact on recording rules as they were getting responses with shifted timestamps in past. Subsequent recording or alerting rules fetching results of these recording rules could get no result due to staleness interval. https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5659 Signed-off-by: hagen1778 <roman@victoriametrics.com> * wip --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2024-01-30 21:03:34 +01:00
* BUGFIX: `vmselect`: set proper timestamps in [instant query](https://docs.victoriametrics.com/keyconcepts/#instant-query) results if the query contains [rollup functions](https://docs.victoriametrics.com/metricsql/#rollup-functions) with lookbehind windows in square brackets exceeding 3 hours. For example, `sum(avg_over_time(up[24h]))`. This bug has been introduced in [v1.95.0](https://docs.victoriametrics.com/changelog_2023/#v1950). See [this](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5659) and [this](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5730) issues.
docs/CHANGELOG.md: document the bugfix at 66c76a4d4d0f93563235b2b4cd5f006bbc7d8020 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5414
2023-12-14 11:48:35 +01:00
docs/CHANGELOG.md: cut v1.96.0 release
2023-12-12 23:42:56 +01:00
## [v1.96.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.96.0)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1960)
app/vmselect/promql: add day_of_year() function (#5368) Co-authored-by: dingxiaoqiang <dingxiaoqiang@bytedance.com> Co-authored-by: Roman Khavronenko <roman@victoriametrics.com> (cherry picked from commit d7897e0d70756e5a0d19d04c85f0fdd6e6ef3754)
2023-11-28 11:54:00 +01:00
docs/CHANGELOG.md: cut v1.95.1
2023-11-16 20:31:59 +01:00
## [v1.95.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.95.1)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1951)
app/vmselect/promql: properly handle duplicate series when merging cached results with the results obtained from the database evalRollupFuncNoCache() may return time series with identical labels (aka duplicate series) when performing queries satisfying all the following conditions: - It must select time series with multiple metric names. For example, {__name__=~"foo|bar"} - The series selector must be wrapped into rollup function, which drops metric names. For example, rate({__name__=~"foo|bar"}) - The rollup function must be wrapped into aggregate function, which has no streaming optimization. For example, quantile(0.9, rate({__name__=~"foo|bar"}) In this case VictoriaMetrics shouldn't return `cannot merge series: duplicate series found` error. Instead, it should fall back to query execution with disabled cache. Also properly store the merged results. Previously they were incorrectly stored because of a typo introduced in the commit 41a0fdaf39ea99708cf1c899332910965d62dcfc Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5332 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5337
2023-11-16 15:52:38 +01:00
docs/CHANGELOG.md: cut v1.95.0 release
2023-11-15 17:45:46 +01:00
## [v1.95.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.95.0)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1950)
lib/backup: add `-deleteAllObjectVersions` command-line flag (#5147) New flag enforces removal of all versions of the object in remote object storage. See: - https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5121 - https://docs.victoriametrics.com/vmbackup.html#permanent-deletion-of-objects-in-s3-compatible-storages (cherry picked from commit 2fc7e9f47e4e30dbb55860a4eb622de35887bea1)
2023-10-10 14:13:23 +02:00
docs/CHANGELOG.md: cut v1.94.0
2023-10-02 22:33:35 +02:00
## [v1.94.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.94.0)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1940)
docs/CHANGELOG.md: document v1.93.6 LTS release See https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.6
2023-10-17 00:53:17 +02:00
docs/CHANGELOG.md: document v1.93.12 LTS release
2024-02-14 19:17:44 +01:00
## [v1.93.12](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.12)
Released at 2024-02-14
**v1.93.x is a line of LTS releases (e.g. long-time support). It contains important up-to-date bugfixes.
The v1.93.x line will be supported for at least 12 months since [v1.93.0](https://docs.victoriametrics.com/CHANGELOG.html#v1930) release**
* SECURITY: upgrade Go builder from Go1.21.6 to Go1.22.0. See [the list of issues addressed in Go1.21.7](https://github.com/golang/go/issues?q=milestone%3AGo1.21.7+label%3ACherryPickApproved), plus [the changelog for Go1.22.0](https://go.dev/doc/go1.22).
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly propagate [label filters](https://docs.victoriametrics.com/keyconcepts/#filtering) from multiple arguments passed to [aggregate functions](https://docs.victoriametrics.com/metricsql/#aggregate-functions). For example, `sum({job="foo"}, {job="bar"}) by (job) + a` was improperly optimized to `sum({job="foo"}, {job="bar"}) by (job) + a{job="foo"}` before being executed. This could lead to unexpected results. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5604).
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly handle precision errors when calculating [changes](https://docs.victoriametrics.com/metricsql/#changes), [changes_prometheus](https://docs.victoriametrics.com/metricsql/#changes_prometheus), [increases_over_time](https://docs.victoriametrics.com/metricsql/#increases_over_time) and [resets](https://docs.victoriametrics.com/metricsql/#resets) functions. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/767).
* BUGFIX: properly store [staleness markers](https://docs.victoriametrics.com/vmagent/#prometheus-staleness-markers) for [self-scraped metrics](https://docs.victoriametrics.com/#monitoring) on single-node VictoriaMetrics shutdown. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/943).
* BUGFIX: prevent from possible `too big indexBlockSize` panic when samples with too long label values (~64Kb) are ingested into VictoriaMetrics.
docs/CHANGELOG.md: document v1.93.11 LTS release
2024-02-01 17:21:28 +01:00
## [v1.93.11](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.11)
Released at 2024-02-01
**v1.93.x is a line of LTS releases (e.g. long-time support). It contains important up-to-date bugfixes.
The v1.93.x line will be supported for at least 12 months since [v1.93.0](https://docs.victoriametrics.com/CHANGELOG.html#v1930) release**
* SECURITY: upgrade base docker image (Alpine) from 3.19.0 to 3.19.1. See [alpine 3.19.1 release notes](https://www.alpinelinux.org/posts/Alpine-3.19.1-released.html).
* BUGFIX: properly return errors from [export APIs](https://docs.victoriametrics.com/#how-to-export-time-series). Previously these errors were silently suppressed. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5649).
* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): properly discover targets for `role: endpoints` and `role: endpointslice` in [kubernetes_sd_configs](https://docs.victoriametrics.com/sd_configs.html#kubernetes_sd_configs). Previously some `endpoints` and `endpointslice` targets could be left undiscovered or some targets could have missing `__meta_*` labels when performing service discovery in busy Kubernetes clusters with large number of pods. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5557).
* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): respect explicitly set `series_limit: 0` in [scrape_config](https://docs.victoriametrics.com/sd_configs.html#scrape_configs). This allows removing [`series_limit` restriction](https://docs.victoriametrics.com/vmagent.html#cardinality-limiter) on a per-`scrape_config` basis when global limit is set via `-promscrape.seriesLimitPerTarget`. Previously, `0` value was ignored in favor of `-promscrape.seriesLimitPerTarget`.
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly process queries with too big lookbehind window such as `foo[100y]`. Previously, such queries could return empty responses even if `foo` is present in database. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5553).
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly handle possible negative results caused by float operations precision error in rollup functions like rate() or increase(). See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5571).
docs/CHANGELOG.md: document v1.93.10 LTS release See https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.10
2024-01-17 00:45:00 +01:00
## [v1.93.10](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.10)
Released at 2024-01-17
**v1.93.x is a line of LTS releases (e.g. long-time support). It contains important up-to-date bugfixes.
The v1.93.x line will be supported for at least 12 months since [v1.93.0](https://docs.victoriametrics.com/CHANGELOG.html#v1930) release**
* SECURITY: upgrade Go builder from Go1.21.5 to Go1.21.6. See [the list of issues addressed in Go1.21.6](https://github.com/golang/go/issues?q=milestone%3AGo1.21.6+label%3ACherryPickApproved).
* BUGFIX: `vminsert`: properly accept samples via [OpenTelemetry data ingestion protocol](https://docs.victoriametrics.com/#sending-data-via-opentelemetry) when these samples have no [resource attributes](https://opentelemetry.io/docs/instrumentation/go/resources/). Previously such samples were silently skipped.
* BUGFIX: `vmstorage`: added missing `-inmemoryDataFlushInterval` command-line flag, which was missing in [VictoriaMetrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html) after implementing [this feature](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3337) in [v1.85.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.85.0).
* BUGFIX: `vmstorage`: properly expire `storage/prefetchedMetricIDs` cache. Previously this cache was never expired, so it could grow big under [high churn rate](https://docs.victoriametrics.com/FAQ.html#what-is-high-churn-rate). This could result in increasing CPU load over time.
* BUGFIX: [vmalert](https://docs.victoriametrics.com/vmalert.html): check `-external.url` schema when starting vmalert, must be `http` or `https`. Before, alertmanager could reject alert notifications if `-external.url` contained no or wrong schema.
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly return results from [bottomk](https://docs.victoriametrics.com/MetricsQL.html#bottomk) and `bottomk_*()` functions when some of these results contain NaN values. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5506). Thanks to @xiaozongyang for [the fix](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5509).
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly handle queries, which wrap [rollup functions](https://docs.victoriametrics.com/MetricsQL.html#rollup-functions) with multiple arguments without explicitly specified lookbehind window in square brackets into [aggregate functions](https://docs.victoriametrics.com/MetricsQL.html#aggregate-functions). For example, `sum(quantile_over_time(0.5, process_resident_memory_bytes))` was resulting to `expecting at least 2 args to ...; got 1 args` error. Thanks to @atykhyy for [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5414).
* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): properly assume role with [AWS IRSA authorization](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html). Previously role chaining was not supported. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3822) for details.
* BUGFIX: all: fix potential panic during components shutdown when [metrics push](https://docs.victoriametrics.com/#push-metrics) is configured. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5548). Thanks to @zhdd99 for the [pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5549).
* 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 @wozz for the [pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5446).
* BUGFIX: [vmctl](https://docs.victoriametrics.com/vmctl.html): retry on import errors in `vm-native` mode. Before, retries happened only on writes into a network connection between source and destination. But errors returned by server after all the data was transmitted were logged, but not retried.
docs/CHANGELOG.md: document v1.93.9 LTS release
2023-12-11 09:39:28 +01:00
## [v1.93.9](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.9)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1939)
docs/CHANGELOG.md: document v1.93.9 LTS release
2023-12-11 09:39:28 +01:00
docs/CHANGELOG.md: document v1.93.8 LTS release
2023-11-15 17:12:44 +01:00
## [v1.93.8](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.8)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1938)
docs/CHANGELOG.md: document v1.93.8 LTS release
2023-11-15 17:12:44 +01:00
docs/CHANGELOG.md: document v1.93.7 LTS release
2023-11-02 08:21:00 +01:00
## [v1.93.7](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.7)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1937)
docs/CHANGELOG.md: document v1.93.7 LTS release
2023-11-02 08:21:00 +01:00
docs/CHANGELOG.md: document v1.93.6 LTS release See https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.6
2023-10-17 00:53:17 +02:00
## [v1.93.6](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.6)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1936)
docs/CHANGELOG.md: publish changes for v1.93.5
2023-09-19 10:50:25 +02:00
## [v1.93.5](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.5)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1935)
docs/CHANGELOG.md: document v1.93.4
2023-09-10 19:47:38 +02:00
## [v1.93.4](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.4)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1934)
docs/CHANGELOG.md: document 1.93.3 release
2023-09-02 10:21:20 +02:00
## [v1.93.3](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.3)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1933)
docs/CHANGELOG.md: document v1.93.2
2023-09-01 17:33:01 +02:00
## [v1.93.2](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.2)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1932)
docs/CHANGELOG.md: move the bugfix line into correct place after ddf87b32ed0a402b8166c51793e23cac64bc7e4d
2023-08-28 09:58:01 +02:00
docs: release docs 1.93.1 (#4875) * docs: mention v1.93.1 release * deployment/docker: bumps image for v1.93.1 release (cherry picked from commit 6abd575cbe91416f470c9866e6c9d314498c9335)
2023-08-23 15:52:58 +02:00
## [v1.93.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.1)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1931)
lib/promrelabel: stop emitting DEBUG log lines when parsing `if` expressions These lines were accidentally left in the commit 62651570bb6142f94025266e9e65353f3d6c37e2 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4635
2023-08-14 15:10:00 +02:00
docs/CHANGELOG.md: cut v1.93.0
2023-08-12 15:01:10 +02:00
## [v1.93.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.93.0)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1930)
docs/CHANGELOG.md: move bugfix description to `tip` chapter, since it isnt released yet Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4697
2023-07-29 08:01:30 +02:00
docs/CHANGELOG.md: cut v1.92.1 (#4735) Signed-off-by: Zakhar Bessarab <z.bessarab@victoriametrics.com> (cherry picked from commit 8f257889cc8793ea223122bc7f1cac3ffbbb7d3b)
2023-07-28 11:07:15 +02:00
## [v1.92.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.92.1)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1921)
vmalert: revert unittest feature (#4734) * Revert "vmalert: unittest support stale datapoint (#4696)" This reverts commit 0b44df7ec8bd28c8fd55bb5a70b99e275109b280. * Revert "docs: specify min version and limitations for vmalert's unit tests" This reverts commit a24541bd Signed-off-by: hagen1778 <roman@victoriametrics.com> * Revert "vmalert: init unit test (#4596)" This reverts commit da60a68d Signed-off-by: hagen1778 <roman@victoriametrics.com> * docs: mention unittest revert in changelog Signed-off-by: hagen1778 <roman@victoriametrics.com> --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 9f1b9b86cc6ec1bd8e4e696d20b1d62a62a1f3bd) Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-07-28 10:42:02 +02:00
docs/CHANGELOG.md: cut v1.92.0
2023-07-27 23:55:46 +02:00
## [v1.92.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.92.0)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1920)
docs: adds v1.91.3 release docs (#4561)
2023-07-03 10:31:02 +02:00
## [v1.91.3](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.91.3)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1913)
docs: adds v1.91.3 release docs (#4561)
2023-07-03 10:31:02 +02:00
docs/CHANGELOG.md: cut v1.91.2 (#4393) Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit cc739e3f8d2c7bd50d589a55db1918f02e5eaa15)
2023-06-03 11:17:23 +02:00
## [v1.91.2](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.91.2)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1912)
vmalert: fix nil map assignment (#4392) * vmalert: fix nil map assignment The storage instance with nil map params was created for remote-read purposes. And before change https://github.com/VictoriaMetrics/VictoriaMetrics/pull/4341/commits/7a9ae9de0d2221cf7759e49ebcde0a06508b0f68 this map was ignored in ApplyParams. Now, it started to be used and vmalert panics in runtime. The fix properly inits map for at `NewVMStorage` and verifies it is not nil on assignment in `ApplyParams`. Signed-off-by: hagen1778 <roman@victoriametrics.com> * vmalert: add to changelog Signed-off-by: hagen1778 <roman@victoriametrics.com> * vmalert: properly clone Storage params Signed-off-by: hagen1778 <roman@victoriametrics.com> * vmalert: properly clone Storage params Signed-off-by: hagen1778 <roman@victoriametrics.com> * vmalert: properly clone Storage params Signed-off-by: hagen1778 <roman@victoriametrics.com> --------- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit de948120889529af03c1dbc644eb7305d46bae19)
2023-06-02 11:38:55 +02:00
docs/CHANGELOG.md: cut v1.91.1 (#4386) Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit b771152039d23b5ccd637a23ea748bc44a9511a7)
2023-06-02 07:50:24 +02:00
## [v1.91.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.91.1)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1911)
docs/CHANGELOG.md: cut v1.91.0
2023-05-18 21:37:12 +02:00
## [v1.91.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.91.0)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1910)
docs/CHANGELOG.md: run at least 4 background mergers on systems with less than 4 CPU cores This reduces the probability of sudden spike in the number of small parts when all the background mergers are busy with big merges.
2023-04-14 08:36:06 +02:00
docs/CHANGELOG.md: cut v1.90.0 release
2023-04-07 01:16:42 +02:00
## [v1.90.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.90.0)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1900)
app/vmbackupmanager: sync with enterprise-single-node branch after 41a54c775891c87e3d5ed59ff0769c869dd2fe71
2023-04-14 04:29:06 +02:00
docs/CHANGELOG.md: cut v1.89.1
2023-03-13 03:14:19 +01:00
## [v1.89.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.89.1)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1891)
app/vmselect/promql: prevent from `cannot unmarshal timeseries from rollupResultCache` panic after the upgrade to v1.89.0
2023-03-13 03:09:02 +01:00
docs/CHANGELOG.md: cut v1.89.0
2023-03-13 01:29:44 +01:00
## [v1.89.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.89.0)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1890)
lib{mergset,storage}: prevent possible race condition with logging st… (#3900) (#3917) lib{mergset,storage}: prevent possible race condition with logging stats for merges Previously partwrapper could be release by background process and reference for part may be invalid during logging stats. It will lead to panic at vmstorage https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3897
2023-03-06 11:11:08 +01:00
docs/CHANGELOG.md: cut v1.88.1
2023-02-28 00:28:18 +01:00
## [v1.88.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.88.1)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1881)
app/vmagent: use the provided auth options when checking whether the remote storage supports VictoriaMetrics remote write protocol Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3847 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1225
2023-02-26 21:07:30 +01:00
docs/CHANGELOG.md: cut v1.88.0
2023-02-25 02:54:21 +01:00
## [v1.88.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.88.0)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1880)
docs/CHANGELOG.md: document v1.87.2 release
2023-02-25 01:14:23 +01:00
docs/CHANGELOG.md: document v1.87.14 LTS release
2024-02-01 16:08:56 +01:00
## [v1.87.14](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.14)
Released at 2024-02-01
**v1.87.x is a line of LTS releases (e.g. long-time support). It contains important up-to-date bugfixes.
The v1.87.x line will be supported for at least 12 months since [v1.87.0](https://docs.victoriametrics.com/CHANGELOG.html#v1870) release**
* SECURITY: upgrade base docker image (Alpine) from 3.19.0 to 3.19.1. See [alpine 3.19.1 release notes](https://www.alpinelinux.org/posts/Alpine-3.19.1-released.html).
* BUGFIX: properly return errors from [export APIs](https://docs.victoriametrics.com/#how-to-export-time-series). Previously these errors were silently suppressed. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5649).
* BUGFIX: [vmagent](https://docs.victoriametrics.com/vmagent.html): respect explicitly set `series_limit: 0` in [scrape_config](https://docs.victoriametrics.com/sd_configs.html#scrape_configs). This allows removing [`series_limit` restriction](https://docs.victoriametrics.com/vmagent.html#cardinality-limiter) on a per-`scrape_config` basis when global limit is set via `-promscrape.seriesLimitPerTarget`. Previously, `0` value was ignored in favor of `-promscrape.seriesLimitPerTarget`.
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly process queries with too big lookbehind window such as `foo[100y]`. Previously, such queries could return empty responses even if `foo` is present in database. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5553).
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly handle possible negative results caused by float operations precision error in rollup functions like rate() or increase(). See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5571).
docs/CHANGELOG.md: document v1.87.13 LTS release See https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.13
2024-01-17 00:04:01 +01:00
## [v1.87.13](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.13)
Released at 2024-01-17
**v1.87.x is a line of LTS releases (e.g. long-time support). It contains important up-to-date bugfixes.
The v1.87.x line will be supported for at least 12 months since [v1.87.0](https://docs.victoriametrics.com/CHANGELOG.html#v1870) release**
* SECURITY: upgrade Go builder from Go1.21.5 to Go1.21.6. See [the list of issues addressed in Go1.21.6](https://github.com/golang/go/issues?q=milestone%3AGo1.21.6+label%3ACherryPickApproved).
* BUGFIX: `vmstorage`: added missing `-inmemoryDataFlushInterval` command-line flag, which was missing in [VictoriaMetrics cluster](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html) after implementing [this feature](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3337) in [v1.85.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.85.0).
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly handle queries, which wrap [rollup functions](https://docs.victoriametrics.com/MetricsQL.html#rollup-functions) with multiple arguments without explicitly specified lookbehind window in square brackets into [aggregate functions](https://docs.victoriametrics.com/MetricsQL.html#aggregate-functions). For example, `sum(quantile_over_time(0.5, process_resident_memory_bytes))` was resulting to `expecting at least 2 args to ...; got 1 args` error. Thanks to @atykhyy for [the pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5414).
* BUGFIX: `vmstorage`: properly expire `storage/prefetchedMetricIDs` cache. Previously this cache was never expired, so it could grow big under [high churn rate](https://docs.victoriametrics.com/FAQ.html#what-is-high-churn-rate). This could result in increasing CPU load over time.
* BUGFIX: [MetricsQL](https://docs.victoriametrics.com/MetricsQL.html): properly return results from [bottomk](https://docs.victoriametrics.com/MetricsQL.html#bottomk) and `bottomk_...` functions when some of these results contain NaN values. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5506). Thanks to @xiaozongyang for [the fix](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5509).
* BUGFIX: all: fix potential panic during components shutdown when [metrics push](https://docs.victoriametrics.com/#push-metrics) is configured. See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/5548). Thanks to @zhdd99 for the [pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5549).
docs/CHANGELOG.md: document v1.87.12
2023-12-10 13:30:22 +01:00
# [v1.87.12](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.12)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v18712)
docs/CHANGELOG.md: document v1.87.12
2023-12-10 13:30:22 +01:00
docs/CHANGELOG.md: document v1.87.11 LTS release
2023-11-15 15:37:40 +01:00
## [v1.87.11](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.11)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v18711)
docs/CHANGELOG.md: document v1.87.11 LTS release
2023-11-15 15:37:40 +01:00
docs/CHANGELOG.md: document v1.87.10 release See https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.10
2023-10-16 23:25:32 +02:00
## [v1.87.10](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.10)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v18710)
docs/CHANGELOG.md: document v1.87.10 release See https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.10
2023-10-16 23:25:32 +02:00
docs/CHANGELOG.md: document v1.87.9
2023-09-10 21:41:23 +02:00
## [v1.87.9](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.9)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1879)
docs/CHANGELOG.md: document v1.87.9
2023-09-10 21:41:23 +02:00
docs/CHANGELOG.md: document v1.87.8
2023-09-02 01:54:07 +02:00
## [v1.87.8](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.8)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1878)
docs/CHANGELOG.md: document v1.87.8
2023-09-02 01:54:07 +02:00
docs/CHANGELOG.md: document changes in the v1.87.7 LTS release
2023-08-12 23:49:08 +02:00
## [v1.87.7](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.7)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1877)
docs/CHANGELOG.md: document changes in the v1.87.7 LTS release
2023-08-12 23:49:08 +02:00
docs/CHANGELOG.md: document v1.87.6 LTS release
2023-05-19 02:50:12 +02:00
## [v1.87.6](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.6)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1876)
docs/CHANGELOG.md: document v1.87.6 LTS release
2023-05-19 02:50:12 +02:00
docs/CHANGELOG.md: document v1.87.5
2023-04-06 09:43:54 +02:00
## [v1.87.5](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.5)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1875)
docs/CHANGELOG.md: document v1.87.5
2023-04-06 09:43:54 +02:00
lib/streamaggr: follow-up for ff72ca14b9d51323e8014f07f424eb9f72d50eb2 - Make sure that the last successfully loaded config is used on hot-reload failure - Properly cleanup resources occupied by already initialized aggregators when the current aggregator fails to be initialized - Expose distinct vmagent_streamaggr_config_reload* metrics per each -remoteWrite.streamAggr.config This should simplify monitoring and debugging failed reloads - Remove race condition at app/vminsert/common.MustStopStreamAggr when calling sa.MustStop() while sa could be in use at realoadSaConfig() - Remove lib/streamaggr.aggregator.hasState global variable, since it may negatively impact scalability on system with big number of CPU cores at hasState.Store(true) call inside aggregator.Push(). - Remove fine-grained aggregator reload - reload all the aggregators on config change instead. This simplifies the code a bit. The fine-grained aggregator reload may be returned back if there will be demand from real users for it. - Check -relabelConfig and -streamAggr.config files when single-node VictoriaMetrics runs with -dryRun flag - Return back accidentally removed changelog for v1.87.4 at docs/CHANGELOG.md Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3639
2023-04-01 06:27:45 +02:00
## [v1.87.4](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.4)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1874)
lib/streamaggr: follow-up for ff72ca14b9d51323e8014f07f424eb9f72d50eb2 - Make sure that the last successfully loaded config is used on hot-reload failure - Properly cleanup resources occupied by already initialized aggregators when the current aggregator fails to be initialized - Expose distinct vmagent_streamaggr_config_reload* metrics per each -remoteWrite.streamAggr.config This should simplify monitoring and debugging failed reloads - Remove race condition at app/vminsert/common.MustStopStreamAggr when calling sa.MustStop() while sa could be in use at realoadSaConfig() - Remove lib/streamaggr.aggregator.hasState global variable, since it may negatively impact scalability on system with big number of CPU cores at hasState.Store(true) call inside aggregator.Push(). - Remove fine-grained aggregator reload - reload all the aggregators on config change instead. This simplifies the code a bit. The fine-grained aggregator reload may be returned back if there will be demand from real users for it. - Check -relabelConfig and -streamAggr.config files when single-node VictoriaMetrics runs with -dryRun flag - Return back accidentally removed changelog for v1.87.4 at docs/CHANGELOG.md Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3639
2023-04-01 06:27:45 +02:00
docs/CHANGELOG.md: document v1.87.3
2023-03-13 08:20:51 +01:00
## [v1.87.3](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.3)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1873)
docs/CHANGELOG.md: document v1.87.3
2023-03-13 08:20:51 +01:00
docs/CHANGELOG.md: document v1.87.2 release
2023-02-25 01:14:23 +01:00
## [v1.87.2](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.2)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1872)
lib/{mergeset,storage}: allow at least 3 concurrent flushes during background merges on systems with 1 or 2 CPU cores This should prevent from data ingestion slowdown and query performance degradation on systems with small number of CPU cores (1 or 2), when big merge is performed. This should help https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3790 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3337
2023-02-11 21:06:18 +01:00
docs/CHANGELOG.md: cut v1.87.1 and mark 1.87.x as LTS release
2023-02-09 20:20:57 +01:00
## [v1.87.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.1)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1871)
docs: follow-up after 2e4bfcce6399e1f18ff104af8550e68018827ec4 (#3785) https://github.com/VictoriaMetrics/VictoriaMetrics/pull/3784/commits/2e4bfcce6399e1f18ff104af8550e68018827ec4 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2023-02-08 09:48:05 +01:00
docs/CHANGELOG.md: cut v1.87.0
2023-02-01 22:03:11 +01:00
## [v1.87.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.87.0)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1870)
docs/CHANGELOG.md: cut v1.86.2
2023-01-18 21:01:07 +01:00
## [v1.86.2](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.86.2)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1862)
docs/CHANGELOG.md: cut v1.86.0
2023-01-11 01:22:26 +01:00
docs/CHANGELOG.md: cut v1.86.1
2023-01-11 10:26:43 +01:00
## [v1.86.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.86.1)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1861)
app/vmselect/promql: make a copy of per-series timestamps before their modification The per-series timestamps are usually shared among series, so it is unsafe modifying them. The issue has been appeared after the optimization at 2f3ddd4884ed9935d2a358c1ab289cd7cabe7a3b
2023-01-11 09:11:07 +01:00
docs/CHANGELOG.md: cut v1.86.0
2023-01-11 01:22:26 +01:00
## [v1.86.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.86.0)
docs/CHANGELOG*: move changes for 2023 year to docs/CHANGELOG_2023.md
2024-01-17 12:09:39 +01:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2023.html#v1860)
docs/CHANGELOG.md: cut v1.85.3
2022-12-20 23:51:23 +01:00
## [v1.85.3](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.85.3)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1853)
docs/CHANGELOG.md: cut v1.85.2
2022-12-19 22:09:29 +01:00
## [v1.85.2](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.85.2)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1852)
docs/CHANGELOG.md: cut v1.85.2
2022-12-19 22:09:29 +01:00
docs/CHANGELOG.md: cut v1.85.1
2022-12-14 20:57:49 +01:00
## [v1.85.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.85.1)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1851)
docs/CHANGELOG.md: cut v1.85.0
2022-12-11 11:01:11 +01:00
## [v1.85.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.85.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1850)
vmalert: properly pass headers during the restore procedure (#3420) See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3418 Signed-off-by: hagen1778 <roman@victoriametrics.com>
2022-12-01 09:27:39 +01:00
docs/CHANGELOG.md: cut v1.84.0
2022-11-26 04:53:29 +01:00
## [v1.84.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.84.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1840)
docs/CHANGELOG.md: cut v1.83.1
2022-11-10 13:06:57 +01:00
## [v1.83.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.83.1)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1831)
docs/CHANGELOG.md: cut v1.83.0
2022-10-29 01:54:54 +02:00
## [v1.83.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.83.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1830)
docs/CHANGELOG.md: release v1.82.1
2022-10-14 10:33:25 +02:00
## [v1.82.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.82.1)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1821)
docs/CHANGELOG.md: release v1.82.1
2022-10-14 10:33:25 +02:00
docs/CHANGELOG.md: cut v1.82.0
2022-10-07 02:15:23 +02:00
## [v1.82.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.82.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1820)
app/vmselect/promql: consistently calculate `rate_over_sum(m[d])` as `sum_over_time(m[d])/d` Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3045
2022-09-02 22:18:01 +02:00
app/vmselect/netstorage: fix a typo, which leads to incorrect query results in VictoriaMetrics cluster The typo has been introduced in the commit 1a254ea20c561561093d60f91815d775189ff93b Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3067
2022-09-08 12:46:37 +02:00
## [v1.81.2](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.81.2)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1812)
docs/CHANGELOG.md: cut v1.81.1
2022-09-02 20:58:28 +02:00
## [v1.81.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.81.1)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1811)
app/vmselect/netstorage: fix potential panic under high load The panic may trigger during data blocks' processing received from vmstorage nodes when some of vmstorage nodes return an error or when `-replicationFactor` is set to values higher than 2 at `vmselect`. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3058
2022-09-02 20:34:00 +02:00
docs/CHANGELOG.md: cut v1.81.0
2022-08-31 01:33:23 +02:00
## [v1.81.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.81.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1810)
docs/CHANGELOG.md: cut v1.80.0
2022-08-08 18:58:50 +02:00
## [v1.80.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.80.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1800)
docs/CHANGELOG.md: add changes for v1.79.2
2022-08-08 17:00:00 +02:00
docs/CHANGELOG.md: document LTS release v1.79.14 See https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.14
2023-08-12 21:28:08 +02:00
## [v1.79.14](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.14)
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v17914)
docs/CHANGELOG.md: document v1.79.13 LTS release
2023-05-19 04:56:24 +02:00
## [v1.79.13](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.13)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v17913)
docs/CHANGELOG.md: document v1.79.13 LTS release
2023-05-19 04:56:24 +02:00
docs/CHANGELOG.md: document v1.79.12
2023-04-06 12:10:01 +02:00
## [v1.79.12](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.12)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v17912)
docs/CHANGELOG.md: document v1.79.12
2023-04-06 12:10:01 +02:00
docs/CHANGELOG.md: document v1.79.11 LTS release
2023-03-13 07:22:53 +01:00
## [v1.79.11](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.11)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v17911)
docs/CHANGELOG.md: document v1.79.11 LTS release
2023-03-13 07:22:53 +01:00
docs/CHANGELOG.md: document v1.79.10 release
2023-02-28 02:35:48 +01:00
## [v1.79.10](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.10)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v17910)
docs/CHANGELOG.md: document v1.79.10 release
2023-02-28 02:35:48 +01:00
docs/CHANGELOG.md: document v1.79.9 release
2023-02-25 00:10:48 +01:00
## [v1.79.9](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.9)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1799)
docs/CHANGELOG.md: document v1.79.9 release
2023-02-25 00:10:48 +01:00
docs/CHANGELOG.md: document changes at v1.79.8 LTS release
2023-02-09 08:38:46 +01:00
## [v1.79.8](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.8)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1798)
docs/CHANGELOG.md: document changes at v1.79.8 LTS release
2023-02-09 08:38:46 +01:00
docs/CHANGELOG.md: document v1.79.7 LTS release
2023-01-11 06:24:28 +01:00
## [v1.79.7](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.7)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1797)
docs/CHANGELOG.md: document v1.79.7 LTS release
2023-01-11 06:24:28 +01:00
docs/CHANGELOG.md: document changes at v1.79.6
2022-12-11 10:51:36 +01:00
## [v1.79.6](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.6)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1796)
docs/CHANGELOG.md: document changes at v1.79.6
2022-12-11 10:51:36 +01:00
docs/CHANGELOG.md: document changes in v1.79.5 release
2022-11-11 00:27:45 +01:00
## [v1.79.5](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.5)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1795)
docs/CHANGELOG.md: document changes in v1.79.5 release
2022-11-11 00:27:45 +01:00
docs/CHANGELOG.md: add a changelog for v1.79.4 LTS release (copied from lts-1.79 branch)
2022-10-07 01:50:52 +02:00
## [v1.79.4](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.4)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1794)
docs/CHANGELOG.md: add a changelog for v1.79.4 LTS release (copied from lts-1.79 branch)
2022-10-07 01:50:52 +02:00
docs/CHANGELOG.md: document v1.79.3 LTS release
2022-08-30 23:15:04 +02:00
## [v1.79.3](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.3)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1793)
docs/CHANGELOG.md: add changes for v1.79.2
2022-08-08 17:00:00 +02:00
## [v1.79.2](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.2)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1792)
app/vmauth: allow duplicate usernames (#2888) Usernames could be duplicate if it has uniq password. vmauth makes routing based on auth token and username + password combination must be unique for this case.
2022-07-19 18:33:17 +02:00
docs/CHANGELOG.md: document v1.79.1 security fix
2022-08-02 12:30:50 +02:00
## [v1.79.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.1)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1791)
docs/CHANGELOG.md: document v1.79.1 security fix
2022-08-02 12:30:50 +02:00
docs/CHANGELOG.md: cut v1.79.0
2022-07-14 15:15:24 +02:00
## [v1.79.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.79.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1790)
app/{vmagent,vminsert}: follow-up after d19e46de554224203c14e57a6d1e164bb33de86a Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/2839
2022-07-07 00:30:56 +02:00
docs/CHANGELOG.md: cut v1.78.1
2022-07-08 00:00:53 +02:00
## [v1.78.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.78.1)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1781)
lib/promscrape: always send stale markers with the real scrape timestamp This guarantees that query won't return data just after the series is disappeared.
2022-06-23 09:55:14 +02:00
docs/CHANGELOG.md: cut v1.78.0
2022-06-20 17:10:38 +02:00
## [v1.78.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.78.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1780)
docs/CHANGELOG.md: document 9e343faa41b9603c8c6b43f71d0df026c03edc0a
2022-05-25 14:03:46 +02:00
docs/CHANGELOG.md: cut v1.77.2
2022-05-21 01:26:15 +02:00
## [v1.77.2](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.77.2)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1772)
docs/CHANGELOG.md: document 8f4f5f1d68b8d6f366f98dc17bd16fc513285c00
2022-05-09 16:32:51 +02:00
docs/CHANGELOG.md: cut v1.77.1
2022-05-07 00:46:27 +02:00
## [v1.77.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.77.1)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1771)
docs/CHANGELOG.md: cut v1.77.0
2022-05-04 23:16:16 +02:00
## [v1.77.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.77.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1770)
docs/CHANGELOG.md: cut v1.76.1
2022-04-12 15:20:55 +02:00
## [v1.76.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.76.1)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1761)
docs/CHANGELOG.md: document the bugfix in hitCount function
2022-04-08 10:31:52 +02:00
docs/CHANGELOG.md: cut v1.76.0
2022-04-07 14:33:55 +02:00
## [v1.76.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.76.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1760)
docs/CHANGELOG.md: cut v1.75.0
2022-03-18 18:53:45 +01:00
docs/CHANGELOG.md: cut v1.75.1
2022-03-28 11:24:00 +02:00
## [v1.75.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.75.1)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1751)
docs/CHANGELOG.md: cut v1.75.1
2022-03-28 11:24:00 +02:00
docs/CHANGELOG.md: cut v1.75.0
2022-03-18 18:53:45 +01:00
## [v1.75.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.75.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1750)
docs/CHANGELOG.md: document c1d07e7c52f0a2ab892921b0639cd42677aa33a8
2022-03-16 13:25:12 +01:00
docs/CHANGELOG.md: cut v1.74.0
2022-03-03 18:30:41 +01:00
## [v1.74.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.74.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1740)
fixes jwt token parse with correct base64Url decoding (#281) * fixes jwt token parse with correct base64Url decoding it must be applied according to jwt RFC that requires token to be URL safe added slow path for decoding tokens with std base64 decoding adds error logging for vmgateway * docs/CHANGELOG.md: document the bugfix Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>
2022-02-23 12:52:03 +01:00
docs/CHANGELOG.md: cut v1.73.1
2022-02-22 20:11:42 +01:00
## [v1.73.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.73.1)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1731)
docs/CHANGELOG.md: document ad6bdd78d0510ae05d8244006c4b93ecc814c424
2022-02-15 11:47:55 +01:00
docs/CHANGELOG.md: cut v1.73.0
2022-02-14 16:54:32 +01:00
## [v1.73.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.73.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1730)
docs/CHANGELOG.md: document the bugfix for highestMax() function is Graphite render API
2022-01-20 11:14:24 +01:00
docs/CHANGELOG.md: cut v1.72.0
2022-01-18 21:43:18 +01:00
## [v1.72.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.72.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2022.html#v1720)
lib/promscrape: scrape replicated targets at different offsets in vmagent replicated clustering mode This guarantees that the deduplication consistently leaves samples from the same vmagent replica. See https://docs.victoriametrics.com/vmagent.html#scraping-big-number-of-targets
2021-12-22 23:20:34 +01:00
docs/CHANGELOG.md: cut v1.71.0
2021-12-20 18:10:24 +01:00
## [v1.71.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.71.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1710)
lib/workingsetcache: fix `unaligned 64-bit atomic operation` panic on 32-bit architectures The panic has been introduced in 7275ebf91a0c847a388c7d21656097d99a16414b
2021-12-03 00:20:04 +01:00
docs/CHANGELOG.md: cut v1.70.0
2021-12-02 14:01:25 +01:00
## [v1.70.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.70.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1700)
app/vmauth: initialize reverse proxy only after flag.Parse() is called This should properly take into accoun the `-maxIdleConnsPerBackend` command-line flag value. Previously it was hardcoded to 100. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1300
2021-11-09 18:18:27 +01:00
docs/CHANGELOG.md: cut v1.69.0
2021-11-08 14:47:36 +01:00
## [v1.69.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.69.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1690)
lib/promscrape: properly show `proxy_url` option value at `/config` page Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1755
2021-10-26 20:21:08 +02:00
docs/CHANGELOG.md: cut v1.68.0
2021-10-22 18:37:43 +02:00
## [v1.68.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.68.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1680)
lib/storage: fix unaligned access on 32-bit architectures. The bug has been introduced at a171916ef5664690c9b596fe73b095aa75fa5d5c
2021-10-08 18:34:38 +02:00
docs/CHANGELOG.md: cut v1.67.0
2021-10-08 15:00:33 +02:00
## [v1.67.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.67.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1670)
app/vmselect/promql: align the behavior of `or`, `and` and `unless` operators with `on (labels)` modifier to Prometheus Previously VictoriaMetrics could return unexpected result of the right-hand side operand had multiple time series with the given set of labels mentioned in `on(labels)`. See https://github.com/VictoriaMetrics/VictoriaMetrics/pull/1643
2021-09-23 23:46:22 +02:00
docs/CHANGELOG.md: cut v1.66.2
2021-09-23 21:53:27 +02:00
## [v1.66.2](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.66.2)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1662)
docs/CHANGELOG.md: document 0e35fc9538727f8c2ea4ae88cda9ab2223435010 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1641
2021-09-23 19:46:21 +02:00
docs/CHANGELOG.md: cut v1.66.1
2021-09-22 00:47:05 +02:00
## [v1.66.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.66.1)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1661)
app/vmselect: fix accessing `/graphite/*` endpoints
2021-09-21 12:28:12 +02:00
docs/CHANGELOG.md: cut v1.66.0
2021-09-20 14:20:25 +02:00
## [v1.66.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.66.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1660)
docs/CHANGELOG.md: document 42e07cfaeae842a773933ed0cbabf3cc17c96ce7
2021-09-07 21:32:01 +02:00
docs/CHANGELOG.md: cut v1.65.0
2021-09-01 16:12:32 +02:00
## [v1.65.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.65.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1650)
app/vmselect/promql: rename `sign()` function to `sgn()` in order to be consistent with Prometheus See https://github.com/prometheus/prometheus/pull/8457 for details.
2021-08-22 21:27:56 +02:00
docs/CHANGELOG.md: cut v1.64.1 This is mostly bugfix release, which includes fixes for staleness handling and a security update for Alpine base image
2021-08-18 21:06:03 +02:00
## [v1.64.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.64.1)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1641)
lib/promscrape: stop scrapers for the removed targets before starting scrapers for the added targets This should prevent from possible time series overlap when old target is substituted by new target (for example, during Kubernetes deployments). Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1526 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1530 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/748 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1509
2021-08-16 23:52:42 +02:00
docs/CHANGELOG.md: cut v1.64.0
2021-08-15 22:52:03 +02:00
## [v1.64.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.64.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1640)
app/vmselect/promql: properly handle `(a op b) default N` if `(a op b)` returns NaN series The result should be a series with `N` values and `a op b` labels. Previously such series has been removed from the result.
2021-07-16 00:43:01 +02:00
docs/CHANGELOG.md: cut v1.63.0
2021-07-15 13:02:13 +02:00
## [v1.63.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.63.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1630)
lib/promscrape: typo fix in `/targets` output The typo has been introduced in fb72a2133f1d14a4c106bf426ae80e038404f341 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1408
2021-06-28 20:23:29 +02:00
docs/CHANGELOG.md: cut v1.62.0
2021-06-25 12:29:38 +02:00
## [v1.62.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.62.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1620)
lib/storage: move deletedMetricIDs set from indexDB to Storage This makes consitent the list of deleted metricIDs when it is used from both the current indexDB and the previous indexDB (aka extDB). This should fix the issue, which could lead to storing new samples under deleted metricIDs after indexDB rotation. See more details at https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1347#issuecomment-861232136 . Thanks to @tangqipengleoo for the initial analysis and the pull request - https://github.com/VictoriaMetrics/VictoriaMetrics/pull/1383 . This commit resolves the issue in more generic way compared to https://github.com/VictoriaMetrics/VictoriaMetrics/pull/1383 . The downside of the commit is the deletedMetricIDs set isn't cleaned from the metricIDs outside the retention. It needs app restart. This should be OK in most cases.
2021-06-15 13:56:51 +02:00
docs/CHANGELOG.md: cut v1.61.1
2021-06-11 12:01:31 +02:00
## [v1.61.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.61.1)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1611)
docs/CHANGELOG.md: document the bugfix from 7adfe878e1135c0ff637864b5ed4d1c0be01303f
2021-06-11 10:28:10 +02:00
docs/CHANGELOG.md: cut v1.61.0
2021-06-09 18:04:44 +02:00
## [v1.61.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.61.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1610)
docs/CHANGELOG.md: document changes from 2233d6ed8aa2ec478e07f9b3ea5d59f324c98141 and d210958fd08f97e8ef7ce645ec3853d1c681459d
2021-05-26 11:23:22 +02:00
docs/CHANGELOG.md: cut v1.60.0
2021-05-24 14:54:49 +02:00
## [v1.60.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.60.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1600)
docs/CHANGELOG.md: document the bugfix for proper removal of stale parts (477369b62f94632b762209d0d874c3649b26e241)
2021-05-03 10:38:09 +02:00
docs/CHANGELOG.md: cut v1.59.0
2021-05-01 08:39:48 +02:00
## [v1.59.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.59.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1590)
lib/{storage,mergeset}: remove empty directories on startup. Such directories can be left after unclean shutdown on NFS storage Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1142
2021-04-22 11:58:53 +02:00
docs/CHANGELOG.md: cut v1.58.0
2021-04-07 23:48:16 +02:00
## [v1.58.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.58.0)
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1580)
app/vmagent/remotewrite: reduce memory usage when `-remoteWrite.queues` is set to a big value See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1167
2021-03-31 15:16:26 +02:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.57.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.57.1)
docs/CHANGELOG.md: cut v1.57.1
2021-03-30 14:40:06 +02:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1571)
app/vmselect: prevent from possible incomplete query results after timed out query Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/711
2021-03-30 12:22:21 +02:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.57.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.57.0)
docs/CHANGELOG.md: cut v1.57.0
2021-03-29 18:14:49 +02:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1570)
lib/storage: prevent from infinite loop if `{__graphite__="..."}` filter matches a metric name with `*`, `[` or `{` chars The idea has been borrowed from https://github.com/VictoriaMetrics/VictoriaMetrics/pull/1137
2021-03-18 13:52:49 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.56.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.56.0)
docs/CHANGELOG.md: cut v1.56.0
2021-03-17 01:04:55 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1560)
lib/promscrape/discovery/kubernetes: reduce memory usage when Kubernetes service discovery is configured on a big number of scrape jobs Previously vmagent was creating a separate Kubernetes object cache per each scrape job. This could result in increased memory usage when monitoring a Kubernetes cluster with big number of objects (pods / nodes / services, etc.) as seen at https://github.com/VictoriaMetrics/VictoriaMetrics/issues/1113 Now it uses a shared map of scrape objects across multiple scrape jobs.
2021-03-05 16:29:54 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.55.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.55.1)
docs/CHANGELOG.md: cut v1.55.1 release
2021-03-03 10:49:10 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1551)
docs/CHANGELOG.md: cut v1.55.0
2021-03-02 20:31:54 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.55.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.55.0)
docs/CHANGELOG.md: cut v1.55.0
2021-03-02 20:31:54 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1550)
app/vmselect/promql: reduce the probability of `duplicate time series` errors when querying Kubernetes metrics
2021-02-18 21:07:29 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.54.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.54.1)
docs/CHANGELOG.md: cut v1.54.1
2021-02-18 18:09:59 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1541)
lib/storage: properly handle queries containing a filter on metric name plus any number of negative filters and zero non-negative filters Example: `node_cpu_seconds_total{mode!="idle"}`
2021-02-18 17:32:33 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.54.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.54.0)
docs/CHANGELOG.md: cut v1.54.0
2021-02-18 13:52:38 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1540)
docs/CHANGELOG.md: cut v1.53.1
2021-02-03 21:50:52 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.53.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.53.1)
docs/CHANGELOG.md: cut v1.53.1
2021-02-03 21:50:52 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1531)
lib/storage: fix a bug, which breaks searching by Graphite wildcard filters
2021-02-03 17:45:42 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.53.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.53.0)
docs/CHANGELOG.md: cut v1.53.0
2021-02-03 02:42:31 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1530)
docs/CHANGELOG.md: mention about the fix with too big HTTP reconnection rate to targets This has been fixed in 0a45220b0a902aeea0b9186fd3a85b24e534a642
2021-01-22 11:09:03 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.52.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.52.0)
docs/CHANGELOG.md: cut v1.52.0
2021-01-13 11:58:51 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2021.html#v1520)
docs/CHANGELOG.md: cut v1.51.0
2020-12-27 13:21:29 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.51.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.51.0)
docs/CHANGELOG.md: cut v1.51.0
2020-12-27 13:21:29 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2020.html#v1510)
docs/CHANGELOG.md: cut v1.50.2
2020-12-19 14:32:34 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.50.2](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.50.2)
docs/CHANGELOG.md: cut v1.50.2
2020-12-19 14:32:34 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2020.html#v1502)
docs/CHANGELOG.md: cut v1.50.1 release
2020-12-15 20:11:39 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.50.1](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.50.1)
docs/CHANGELOG.md: cut v1.50.1 release
2020-12-15 20:11:39 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2020.html#v1501)
docs/CHANGELOG.md: mention about bugfix, which properly removes unregistered targets from `/targets` page See bugfix at a4c7fcb5e16d56fc72c5c821f839d7aabcc2c743
2020-12-15 20:06:01 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.50.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.50.0)
docs/CHANGELOG.md: cut v1.50.0 release
2020-12-15 13:44:42 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2020.html#v1500)
docs/CHANGELOG.md: cut v1.49.0
2020-12-05 12:49:04 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.49.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.49.0)
docs/CHANGELOG.md: cut v1.49.0
2020-12-05 12:49:04 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2020.html#v1490)
lib/protoparser/prometheus: properly parse OpenMetrics timestamps OpenMetrics timestamps are floating-point numbers, that represent Unix timestamp in seconds. This differs from Prometheus exposition format, where timestamps are integer numbers representing Unix timestamp in milliseconds.
2020-11-27 13:53:27 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.48.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.48.0)
docs/CHANGELOG.md: cut v1.48.0 release
2020-11-26 01:05:50 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2020.html#v1480)
docs/CHANGELOG.md: cut v1.47.0 release
2020-11-16 19:59:57 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.47.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.47.0)
docs/CHANGELOG.md: cut v1.47.0 release
2020-11-16 19:59:57 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2020.html#v1470)
CHANGELOG.md: cut v1.46.0
2020-11-07 16:52:45 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.46.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.46.0)
CHANGELOG.md: cut v1.46.0
2020-11-07 16:52:45 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2020.html#v1460)
docs: add CHANGELOG.md
2020-11-05 13:58:22 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.45.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.45.0)
docs: add CHANGELOG.md
2020-11-05 13:58:22 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2020.html#v1450)
docs: add CHANGELOG.md
2020-11-05 13:58:22 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.44.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.44.0)
docs: add CHANGELOG.md
2020-11-05 13:58:22 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2020.html#v1440)
docs: add CHANGELOG.md
2020-11-05 13:58:22 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.43.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.43.0)
docs: add CHANGELOG.md
2020-11-05 13:58:22 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2020.html#v1430)
docs: add CHANGELOG.md
2020-11-05 13:58:22 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## [v1.42.0](https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.42.0)
docs: add CHANGELOG.md
2020-11-05 13:58:22 +01:00
docs/CHANGELOG.md: split changelog into per-year pages in order to keep the size of CHANGELOG pages under control Make sure that links to particular releases - https://docs.victoriametrics.com/CHANGELOG.html#vXXYY - continue working.
2023-08-12 14:48:21 +02:00
See changes [here](https://docs.victoriametrics.com/CHANGELOG_2020.html#v1420)
docs: add CHANGELOG.md
2020-11-05 13:58:22 +01:00
docs: update docs ordering and formatting (#1192) The major change is adding `sort` directive to docs. For those docs which are copied from internal packages `sort` is added via makefile command. For the rest it is added manually since they're updated manually as well. The rest of changes is connected with markdown formatting. For example, changing headers in some files (`##` => `#`) makes navigation on .github.io to look better. This especially useful for `changelog` docs. Table of contents for `vmctl` is dropped, since we already have it autogenerated on .github.io. No link changes expected. The corresponding PR to `cluster` branch will be made in follow-up PR.
2021-04-07 12:39:16 +02:00
## Previous releases
docs: add CHANGELOG.md
2020-11-05 13:58:22 +01:00
See [releases page](https://github.com/VictoriaMetrics/VictoriaMetrics/releases).
Reference in New Issue Copy Permalink