update CHANGELOG and migration guide

Signed-off-by: Jan Fajerski <jfajersk@redhat.com>
This commit is contained in:
Jan Fajerski 2024-11-11 17:45:12 +01:00 committed by bwplotka
parent f4a26f8d83
commit 3067d0bc2f
2 changed files with 13 additions and 0 deletions

View file

@ -2,7 +2,12 @@
## unreleased ## unreleased
## 3.0.0-rc.1 / 2024-11-11
* [CHANGE] Set the `GOMAXPROCS` variable automatically to match the Linux CPU quota. Use `-no-auto-gomaxprocs` to disable it. The `auto-gomaxprocs` feature flag was removed. #15376
* [CHANGE] Set the `GOMEMLIMIT` variable automatically to match the Linux container memory limit. Use `-no-auto-gomemlimit` to disable it. The `auto-gomemlimit` feature flag was removed. #15373
* [BUGFIX] Scraping: Don't log errors on empty scrapes. #15357 * [BUGFIX] Scraping: Don't log errors on empty scrapes. #15357
* [BUGFIX] UI: fix selector / series formatting for empty metric names. #15341
## 3.0.0-rc.0 / 2024-10-31 ## 3.0.0-rc.0 / 2024-10-31

View file

@ -31,6 +31,14 @@ This document offers guidance on migrating from Prometheus 2.x to Prometheus 3.0
`http://example.com/metrics:80` respectively, add them to your target URLs `http://example.com/metrics:80` respectively, add them to your target URLs
- `agent` - `agent`
Instead use the dedicated `--agent` CLI flag. Instead use the dedicated `--agent` CLI flag.
- `auto-gomemlimit`
Prometheus v3 will automatically set `GOMEMLIMIT` to match the Linux
container memory limit. If there is no container limit, or the process is
running outside of containers, the system memory total is used. To disable
this, `--no-auto-gomemlimit` is available.
- `auto-gomaxprocs`
Prometheus v3 will automatically set `GOMAXPROCS` to match the Linux
container CPU quota. To disable this, `--no-auto-gomaxprocs` is available.
Prometheus v3 will log a warning if you continue to pass these to Prometheus v3 will log a warning if you continue to pass these to
`--enable-feature`. `--enable-feature`.