We are running PMM 1.17.0 built from AWS AMI, so running on an AWS EC2. Using PMM just for mongodb clusters. Installed PMM server and clients 02/2019, so everything is recent and at default values.
Since mongodb clusters tend to have a lot of nodes to monitor, I want to try and keep the CPU load on the PMM server to reasonable levels and hence keep the instance type cost down.
To do this I thought that reducing the frequency with which PMM collects metrics would help. Would welcome thoughts on that and other options.
In the past I was using PMM for mysql, with a docker install. That gave me the option of METRICS_RESOLUTION, but the AMI install of PMM doesn’t have that option.
I’ve looked at the prometheus datasource on the pmm web interface, and that has a scrape_interval setting. Is this all I need to set? I am kind of doubtful because it mentions in the help popup that this is driven or set from the yml config. Or do I need to alter settings within the /etc/prometheus.yml file and bounce prometheus.
I did search thru the forum and help and there was mention of advice to not edit the prometheus.yml because of instability.