NOT able get the collection metrics and DBs in the PMM MongoDB collections overview dashboard

Hi

I am currently running PMM Server v3.7.0 as a Docker container on a separate server, and PMM Client v3.7.0 on the host machine for a MongoDB replica set. I am working on a secondary node.

I am able to view basic metrics such as latency, overview stats, CPU, and memory usage. However, I am not able to see complete collection-level metrics or database metrics only partial data is visible. eventhough if visible being so unstable

Additionally, the PMM client is consuming a large amount of RAM while pushing metrics through the MongoDB exporter, which is causing OOM kill issues and bringing down the MongoDB server.

I have connected the PMM client using pmm-admin, enabled profiling and tracing, and ensured proper permissions are in place. I also increased the collection stats limit from 200 to 5000. Despite this, I am still unable to see full metrics in the PMM dashboard.

Kinldy help me to sort this issue.

sudo pmm-admin add mongodb --username=pmm --password=<----> --environment=QAmm --cluster=mongo --replication-set=rs1 --tls --tls-ca-file=/key/ca_crt.pem --tls-skip-verify --host=drp.info --query-source=profiler --port=27017 --enable-all-collectors --max-collections-limit=5000 --query-source=“profiler”

How many collections does this mongodb server have?

the PMM client is consuming a large amount of RAM while pushing metrics through the MongoDB exporter, which is causing OOM kill issues and bringing down the MongoDB server

Please note this from the official docs about –max-collections-limit:

  • --max-collections-limit: Maximum number of collections to monitor. Set to -1 to let PMM decide (default), or 0 for unlimited. A very high value can impact CPU and memory usage.

Hi @jrivera i have tried with the –max-collections-limit:0 & -1 as well butnot able to get the collections in the database is there any other way that can we able get it on dashboard

I believe logs of pmm-agent and mongodb_exporter could help troubleshoot the issue (curl -ks –user admin:password https://127.0.0.1:8443/v1/server/logs.zip).

It’d be good to check on the Inventory UI if the exporter is running and it it’s connected to the database.