I lose scrap data after pmm upgrade 2.0 to 2.4.
how to i do not lose data?
It’s not v1.
You should not lose any scrape data in the upgrade process so that’s something of a concern. Can you provide more details on how you performed the upgrade (pull down a new docker image or use the “upgrade now” link in the UI) and did you get any errors in the process that might shed some light?
I did like this.
1. make data container.
docker create -v /opt/prometheus/data -v /opt/consul-data -v /var/lib/mysql -v /var/lib/grafana --name tpmm2-data-gr1 \percona/pmm-server:2.3.0 /bin/true
2. make server container.
docker run -d <br>-p 80:80 -p 443:443 --volumes-from tpmm2-data-gr1 --name pmm2-svr-gr1 --restart always -e METRICS_RETENTION=4320h -e QUERIES_RETENTION=30 -e METRICS_MEMORY=16777216 \percona/pmm-server:2.4.0
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESa9ffa2d29218 percona/pmm-server:2.4.0 “/opt/entrypoint.sh” 2 weeks ago Up 2 weeks (healthy) 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp tpmm2-svr-gr173d5cc08be87 percona/pmm-server:2.3.0 “/bin/true” 2 weeks ago Created tpmm2-data-gr1
3. delete server container.docker stop tpmm2-svr-gr1 && docker rm tpmm2-svr-gr1
4. make new version server container.docker run -d -p 80:80 -p 443:443 --volumes-from tpmm2-data-gr1 --name tpmm2-svr-gr1 --restart always -e METRICS_RETENTION=4320h -e QUERIES_RETENTION=30 -e METRICS_MEMORY=16777216 \percona/pmm-server:2.5.0
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES1385ed5531d4 percona/pmm-server:2.5.0 “/opt/entrypoint.sh” 3 seconds ago Up 3 seconds (health: starting) 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp tpmm2-svr-gr173d5cc08be87 percona/pmm-server:2.3.0 “/bin/true” 2 weeks ago Created tpmm2-data-gr1