# Can PMM be used with MongoDB Enterprise instances?

**URL:** <https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452>\
**Category:** PMM 3.x\
**Created:** [November 18, 2026, 9:26am UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452 "2026-11-18T09:26:42Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![afmf](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@afmf](https://forums.percona.com/u/afmf)\
**Post date:** [November 18, 2026, 9:26am UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452/1 "2026-11-18T09:26:42Z")

</div>

Good monrong,

I’ve hundreds of Percona MongoDB instances and we obtain the data correctly from them.

I’ve tried to add some MongoDB enterprise instances and a lot of them have Monitoring:OK but Status:Unknown.

Is there any restriction or pre-requisite I should apply to avoid this issue? Or should I just don’t use PMM for MongoDB Enterprise instances?

Regards,  
André Ferreira

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [November 18, 2026, 11:59am UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452/2 "2026-11-18T11:59:46Z")

</div>

Hi, Mongo Enterprise should work fine with PMM. Can you explain more about your setup? what versions are you using? Where exactly do you see this Status: unknown?

---

<div class="post-metadata">

**Author:** ![afmf](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@afmf](https://forums.percona.com/u/afmf)\
**Post date:** [November 18, 2026, 12:25pm UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452/3 "2026-11-18T12:25:37Z")

</div>

I’m using PMM 3.10.0.

I see the Status: Unknown under Inventory → Services.

For the MongoDB Enterprise I’ve versions 8.3.7 or 8.3.8.

The problem is that when I’ve with this status, we are not able to see the info of the instances under MongoDB section.

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [November 18, 2026, 12:32pm UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452/4 "2026-11-18T12:32:39Z")

</div>

This typically means metrics aren’t reaching PMM server. To narrow this down:

- In Explore, query up{node\_id=“your\_node\_name”}. Do you see anything?
- If nothing comes back, run pmm-admin status and pmm-admin list on the client. Check that node\_exporter is listed and running, and that vmagent is running.
- Look in the pmm-agent logs for vmagent remote-write errors, for example connection refused, 401, TLS errors, etc.

---

<div class="post-metadata">

**Author:** ![afmf](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@afmf](https://forums.percona.com/u/afmf)\
**Post date:** [November 18, 2026, 2:45pm UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452/5 "2026-11-18T14:45:34Z")

</div>

In Explore, I only have “PromQL builder” section.

I’ve seen for one of the cases, I see that node\_exported is listed and running for it.

In the logs I put AI analysing and got this:  
34 exporters fail ~100% of \_hr scrapes (894–902 logged failures each, error EOF or Client.Timeout exceeded while awaiting headers) — and these are exactly the replset-member exporters on the dedicated hosts. This is the same ethtool/diagnosticdata bug already diagnosed: pmm-agent.log has 16,356 panic lines / 5,453 giant\_hdr lines, still panicking as of 14:30 today. \_lr keeps delivering mongodb\_up for all of them, which is why the services still show connected but hr-only metrics are missing / UI shows Unknown.

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [November 18, 2026, 3:31pm UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452/6 "2026-11-18T15:31:09Z")

</div>

Looks like something is wrong with the agent connecting to mongo. Can you share the commands you used for pmm-admin add ? you can remove sensitive info like password.

---

<div class="post-metadata">

**Author:** ![lauraharris](https://avatars.discourse-cdn.com/v4/letter/l/e19adc/32.png) [@lauraharris](https://forums.percona.com/u/lauraharris)\
**Post date:** [November 20, 2026, 12:13am UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452/7 "2026-11-20T00:13:37Z")

</div>

Enterprise isn’t the blocker; the evidence points to the high-resolution MongoDB exporter failing while the low-resolution path still reports mongodb\_up. Check that the pmm-admin add mongodb command targets the replica-set member’s advertised host/port (not localhost or a load balancer), that the monitoring user has clusterMonitor on admin, and that TLS/auth options are identical for every member. EOF/timeouts often mean the exporter can’t complete the MongoDB handshake. Also capture pmm-agent version and panic logs; the giant\_hdr panic is an agent bug, not an Enterprise restriction.

---

<div class="post-metadata">

**Author:** ![afmf](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@afmf](https://forums.percona.com/u/afmf)\
**Post date:** [November 20, 2026, 10:24am UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452/8 "2026-11-20T10:24:13Z")

</div>

Position: Your operational checklist items are all ruled out — the evidence points to the exporter bug you (Percona) yourself flagged.

1. Address is correct — all 34 services registered against their own member host:port; no localhost/LB/VIP.
2. Privileges fine — root on admin (superset of clusterMonitor).
3. Handshake theory refuted — the same 34 exporters that fail high-res all report mongodb\_up=1 and serve the low-res fcv+pbm collectors fine (200 OK, 0.1s), which requires a fully authenticated connection. The failure is specific to the diagnosticdata collector: exporter panics server-side on mongodb\_sys\_ethtool\_ens192\_giant\_hdr and drops the connection (instant EOF, reproducible 34/34, timeout-independent — tested 120s vs 4.5s, same result).
4. Versions + panic logs delivered — pmm-agent 3.10.0 (378dbc37), mongodb\_exporter v0.45.0 (e2dd9bba), full giant\_hdr stack trace at exporter.go:213: mongodb\_sys\_ethtool\_\*\_giant\_hdr duplicate registration in the diagnosticdata collector

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [November 20, 2026, 10:43am UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452/9 "2026-11-20T10:43:16Z")

</div>

Hi, you can open a bug report at our JIRA. Please provide logs so the engineering team can take a look.

---

<div class="post-metadata">

**Author:** ![afmf](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@afmf](https://forums.percona.com/u/afmf)\
**Post date:** [November 20, 2026, 10:46am UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452/10 "2026-11-20T10:46:12Z")

</div>

Hello Ivan,

Can you give me the JIRA link?

Regards,  
André Ferreira

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [November 20, 2026, 10:54am UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452/11 "2026-11-20T10:54:44Z")

</div>

Sure, that would be [https://perconadev.atlassian.net/](https://perconadev.atlassian.net/)

---

<div class="post-metadata">

**Author:** ![afmf](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@afmf](https://forums.percona.com/u/afmf)\
**Post date:** [November 20, 2026, 3:21pm UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452/12 "2026-11-20T15:21:53Z")

</div>

Thank you Ivan, [https://perconadev.atlassian.net/browse/PMM-15951](https://perconadev.atlassian.net/browse/PMM-15951) created 🙂

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [November 20, 2026, 3:57pm UTC](https://forums.percona.com/t/can-pmm-be-used-with-mongodb-enterprise-instances/41452/13 "2026-11-20T15:57:03Z")

</div>

after talking to eng team what triggers the bug is the operating system and network card on the host, not the MongoDB Enterprise edition.

Workaround  
Re-add the affected services with pmm-admin add mongodb … --disable-collectors=diagnosticdata. This stops the panics and the log noise, but those services still won’t have diagnostic metrics until the fix for [https://perconadev.atlassian.net/browse/PMM-15249](https://perconadev.atlassian.net/browse/PMM-15249) ships
