From 5dcc21887bbfa576138903a22d9f32b3ee1692e5 Mon Sep 17 00:00:00 2001 From: showuon <43372967+showuon@users.noreply.github.com> Date: Tue, 25 Aug 2020 17:04:05 +0800 Subject: [PATCH] update the migrating doc for less confusion (#7845) Signed-off-by: Luke Chen --- docs/migration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/migration.md b/docs/migration.md index c81ca5ae9..1fa2e6b13 100644 --- a/docs/migration.md +++ b/docs/migration.md @@ -7,7 +7,7 @@ sort_rank: 8 In line with our [stability promise](https://prometheus.io/blog/2016/07/18/prometheus-1-0-released/#fine-print), the Prometheus 2.0 release contains a number of backwards incompatible changes. -This document offers guidance on migrating from Prometheus 1.8 to Prometheus 2.0. +This document offers guidance on migrating from Prometheus 1.8 to Prometheus 2.0 and newer versions. ## Flags @@ -125,7 +125,7 @@ Note that you will need to use promtool from 2.0, not 1.8. ## Storage 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 +compatible with 1.8 and older versions. 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.