# Recommendation configuration container Docker pmm-server

**URL:** <https://forums.percona.com/t/recommendation-configuration-container-docker-pmm-server/5173>\
**Category:** PMM 1.x\
**Created:** [October 27, 2016, 4:41am UTC](https://forums.percona.com/t/recommendation-configuration-container-docker-pmm-server/5173 "2016-10-27T04:41:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmons](https://avatars.discourse-cdn.com/v4/letter/c/ecb155/32.png) [@cmons](https://forums.percona.com/u/cmons)\
**Post date:** [October 27, 2016, 4:41am UTC](https://forums.percona.com/t/recommendation-configuration-container-docker-pmm-server/5173/1 "2016-10-27T04:41:55Z")

</div>

Hello,

Can you help me please on container configuration pmm-server ?  
In terms of storage and performance?

## We want to monitor approximately 50 servers databases (Percona XtraDB 5.5 - 3 nodes, Percona Server 5.5 - SLAVES server, Percona Server 5.6 - SLAVES server and MySQL 5.5 servers).

Do you have any recommendation please ?  
Pmm server stores the information on the QAN API and Prometheus will grow gradually ?  
Do we have the opportunity to clean the QAN API and Prometheus ?

Do you have recommendation for configuration “volume” for each parts ?  
docker create \ -v /opt/prometheus/data \ -v /opt/consul-data \ -v /var/lib/mysql \ -v /var/lib/grafana \ –name pmm-data \ percona/pmm-server:1.0.5 /bin/true Thank you for your help, Regards,

---

<div class="post-metadata">

**Author:** ![weber](https://avatars.discourse-cdn.com/v4/letter/w/da6949/32.png) [@weber](https://forums.percona.com/u/weber)\
**Post date:** [October 27, 2016, 6:03am UTC](https://forums.percona.com/t/recommendation-configuration-container-docker-pmm-server/5173/2 "2016-10-27T06:03:08Z")

</div>

Hello,

I would recommend splitting servers by environment or their purpose per PMM Server instance (server+data containers) if possible.

There is METRICS\_RETENTION option to configure metrics data retention (default 30 days). This works well.  
In 1.0.6 there will be QUERIES\_RETENTION option to configure Query Analytics retention (default 8 days).

As for managing volumes, I think it does not really matter whether this is a single container or separate.