Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upUpgrade : Is there a way to convert Prometheus 1.8x timeseries to 2.x #3984
Comments
This comment has been minimized.
This comment has been minimized.
|
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided. |
brian-brazil
closed this
Mar 19, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
nightlynerd commentedMar 19, 2018
The Migration guide to 2.x states the following
"The data format in Prometheus 2.0 has completely changed and is not backwards compatible with 1.8. To retain access to your historic monitoring data we recommend you run a non-scraping Prometheus instance running at least version 1.8.1 in parallel with your Prometheus 2.0 instance, and have the new server read existing data from the old one via the remote read protocol."
The above ensures that I can upgrade to Prometheus 2.x without loss of data. However, I now have to run 2 instance of Prometheus. Which implies managing HA for each. Is there a way by which I could read the historical time-series in the non-scraping Prometheus 1.8x instance and convert it to a 2.x format. That way there is a bounded amount of time when I will have to run both versions. Eventually, all content gets converted to 2.x format and can be served by Prometheus 2.x