Shubham Mer6411 can you paste `docker

[acoustic shard]

it did not come through

[acoustic shard]

the directory being mixed into the volume name is unexpected and trying to understand why. what does docker volume inspect harvest_prometheus_data show?

[acoustic shard]

checking another machine

[junior zealot]

okay i have the same issue in the prod and in my lab as well prod is ubuntu and lab is centos

[acoustic shard]

thanks for bringing this up @junior zealot. I think you're right, the docker-compose is prepending the basename to named volumes. What you mentioned earlier should work fine and we'll better document how to upgrade on GitHub

[junior zealot]

so the method i am using should work right it will not affect the containers/harvest functionality anyway for future releases as well

[acoustic shard]

in addition to copying the grafana folder you will want to copy the conf folder since it has template updates. In terms of future releases, we'll document how to move from older versions to newer preserving your Prometheus data

[junior zealot]

ahmm cool thanks for the info

[acoustic shard]

you bet. Thanks for raising this

[acoustic shard]

hi @junior zealot we updated the upgrade documentation here https://github.com/NetApp/harvest/tree/main/docker#upgrade-harvest and created a new docs on migrating historical Prometheus data https://github.com/NetApp/harvest/blob/main/docs/MigratePrometheusDocker.md If you get the time/interest and try it, let us know if you hit any problems or need clarifications

[junior zealot]

Thanks @acoustic shard I tried the same method we discussed yesterday on the production instance and it worked well.

just a thing to check even in 22.08 if i setup a new stack i still see the volume been created with an appended directory name,isnt the new release was supposed to have standard volume names like harvest_prometheus_data

[mint shard]

@junior zealot New release 22.11 will have that change where volume name will remain same during upgrades.