mudhorn/prometheus
1
0
Fork 0
mirror of https://github.com/prometheus/prometheus.git synced 2024-11-14 17:44:06 -08:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

Update migration.md for TSDB storage upgrade

Browse source 
Signed-off-by: Bartlomiej Plotka <bwplotka@gmail.com>
This commit is contained in:
Bartlomiej Plotka 2024-11-11 19:32:48 +00:00 committed by GitHub
parent f701f4e236
commit 99cbdc113c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 10 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
docs/migration.md
View file

@ -104,19 +104,25 @@ may now fail if this fallback protocol is not specified.
## Miscellaneous ## Miscellaneous
### TSDB format and downgrade ### TSDB format and downgrade
The TSDB format has been changed in Prometheus v2.55 in preparation for changes
The TSDB format has been changed slightly in Prometheus v2.55 in preparation for changes
to the index format. Consequently, a Prometheus v3 TSDB can only be read by a to the index format. Consequently, a Prometheus v3 TSDB can only be read by a
Prometheus v2.55 or newer. Prometheus v2.55 or newer. Keep that in mind when upgrading to v3 -- you will be only
Before upgrading to Prometheus v3 please upgrade to v2.55 first and confirm able to downgrade to v2.55, not lower, without loosing your TSDB persitent data.
Prometheus works as expected. Only then continue with the upgrade to v3.
As an extra safety measure, you could optionally consider upgrading to v2.55 first and
confirm Prometheus works as expected, before upgrading to v3.
### TSDB storage contract ### TSDB storage contract
TSDB compatible storage is now expected to return results matching the specified TSDB compatible storage is now expected to return results matching the specified
selectors. This might impact some third party implementations, most likely selectors. This might impact some third party implementations, most likely
implementing `remote_read`. implementing `remote_read`.
This contract is not explicitly enforced, but can cause undefined behavior. This contract is not explicitly enforced, but can cause undefined behavior.
### UTF-8 names ### UTF-8 names
Prometheus v3 supports UTF-8 in metric and label names. This means metric and Prometheus v3 supports UTF-8 in metric and label names. This means metric and
label names can change after upgrading according to what is exposed by label names can change after upgrading according to what is exposed by
endpoints. Furthermore, metric and label names that would have previously been endpoints. Furthermore, metric and label names that would have previously been