# All PMM MongoDB monitoring services are not working!

**URL:** <https://forums.percona.com/t/all-pmm-mongodb-monitoring-services-are-not-working/15449>\
**Category:** PMM 2.x\
**Tags:** pmm, mongodb\
**Created:** [April 28, 2022, 12:55am UTC](https://forums.percona.com/t/all-pmm-mongodb-monitoring-services-are-not-working/15449 "2022-04-28T00:55:19Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![webstock\_zt](https://avatars.discourse-cdn.com/v4/letter/w/8797f3/32.png) [@webstock\_zt](https://forums.percona.com/u/webstock_zt)\
**Post date:** [April 28, 2022, 12:55am UTC](https://forums.percona.com/t/all-pmm-mongodb-monitoring-services-are-not-working/15449/1 "2022-04-28T00:55:19Z")

</div>

Hi team!  
My mongodb sharded cluster has a total of 11 nodes, and both shards are P-S-S architectures. There are a total of 9 machines, deployed in two computer rooms, 6 machines in machine room A use the centos system, and 3 machines in machine room B use the ubuntu system.  
pmm server version: 2.27.0  
pmm client version: 2.27.0  
When I added the 8th machines, the number of MongoDB services displayed by the pmm console suddenly decreased to 1, and the displayed monitoring data were all wrong.

---

<div class="post-metadata">

**Author:** ![webstock\_zt](https://avatars.discourse-cdn.com/v4/letter/w/8797f3/32.png) [@webstock\_zt](https://forums.percona.com/u/webstock_zt)\
**Post date:** [April 28, 2022, 1:00am UTC](https://forums.percona.com/t/all-pmm-mongodb-monitoring-services-are-not-working/15449/2 "2022-04-28T01:00:23Z")

</div>

![微信截图_20220428085425](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/0/0c9fa91a349fcf88972462d8d7cfe1949569a646.png)

---

<div class="post-metadata">

**Author:** ![webstock\_zt](https://avatars.discourse-cdn.com/v4/letter/w/8797f3/32.png) [@webstock\_zt](https://forums.percona.com/u/webstock_zt)\
**Post date:** [April 28, 2022, 1:12am UTC](https://forums.percona.com/t/all-pmm-mongodb-monitoring-services-are-not-working/15449/3 "2022-04-28T01:12:28Z")

</div>

I tried to rebuild the pmm service several times, but the addition failed when the total number of exporters was around 18. Is there a limit to the maximum number of monitoring services that pmm2 supports?It looks like the resources on the server side are not exhausted.

---

<div class="post-metadata">

**Author:** ![Puneet](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/puneet/32/1331_2.png) [@Puneet](https://forums.percona.com/u/Puneet)\
**Post date:** [April 28, 2022, 6:12am UTC](https://forums.percona.com/t/all-pmm-mongodb-monitoring-services-are-not-working/15449/4 "2022-04-28T06:12:21Z")

</div>

hey @webstock_zt thanks a lot for your question, we don’t have any maximum number limit in terms of mongodb services you can add for monitoring, as long as you have enough resources,

 ![image](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/2/2f65b74193a03b8017149d2c755c0b19ffce8566.png)

This is from one of our test servers, could you possibly check for logs and exporter status and share some more information, probably it could be some other issue.

Could you also check the value for `count(mongodb_up)` using the explore the functionality and share it.

---

<div class="post-metadata">

**Author:** ![webstock\_zt](https://avatars.discourse-cdn.com/v4/letter/w/8797f3/32.png) [@webstock\_zt](https://forums.percona.com/u/webstock_zt)\
**Post date:** [April 28, 2022, 6:46am UTC](https://forums.percona.com/t/all-pmm-mongodb-monitoring-services-are-not-working/15449/5 "2022-04-28T06:46:32Z")

</div>

Here is the count(mongodb\_up):

 ![count](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/2X/f/faabd1eb9210955c1ae2532c0ed67f41a891cc0c.png)

---

<div class="post-metadata">

**Author:** ![webstock\_zt](https://avatars.discourse-cdn.com/v4/letter/w/8797f3/32.png) [@webstock\_zt](https://forums.percona.com/u/webstock_zt)\
**Post date:** [April 28, 2022, 6:50am UTC](https://forums.percona.com/t/all-pmm-mongodb-monitoring-services-are-not-working/15449/6 "2022-04-28T06:50:41Z")

</div>

Here is my server logs.It was a .zip file.I changed the extension name.  
[pmm-server\_2022-04-28\_06-43.zip.log](https://forums.percona.com/uploads/short-url/9pddFHy1pwZoFI8WR0VgPPV4FWi.log) (96.7 KB)

---

<div class="post-metadata">

**Author:** ![webstock\_zt](https://avatars.discourse-cdn.com/v4/letter/w/8797f3/32.png) [@webstock\_zt](https://forums.percona.com/u/webstock_zt)\
**Post date:** [April 28, 2022, 6:56am UTC](https://forums.percona.com/t/all-pmm-mongodb-monitoring-services-are-not-working/15449/7 "2022-04-28T06:56:57Z")

</div>

And this time I added 7 mongodb services at about 11:00 am. They worked well before 13:10.

---

<div class="post-metadata">

**Author:** ![webstock\_zt](https://avatars.discourse-cdn.com/v4/letter/w/8797f3/32.png) [@webstock\_zt](https://forums.percona.com/u/webstock_zt)\
**Post date:** [April 29, 2022, 12:51am UTC](https://forums.percona.com/t/all-pmm-mongodb-monitoring-services-are-not-working/15449/8 "2022-04-29T00:51:08Z")

</div>

Hi @Punnet. Is it possible that the problem is caused by monitoring both Ubuntu and Centos systems?

---

<div class="post-metadata">

**Author:** ![Puneet](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/puneet/32/1331_2.png) [@Puneet](https://forums.percona.com/u/Puneet)\
**Post date:** [April 29, 2022, 6:22am UTC](https://forums.percona.com/t/all-pmm-mongodb-monitoring-services-are-not-working/15449/9 "2022-04-29T06:22:35Z")

</div>

@webstock_zt No, I don’t think that should be a problem, I was looking at the logs and identified many errors related to failing agent connection, probably seems something related to that, I will log a bug about this and request a developer on the team to help investigate

---

<div class="post-metadata">

**Author:** ![webstock\_zt](https://avatars.discourse-cdn.com/v4/letter/w/8797f3/32.png) [@webstock\_zt](https://forums.percona.com/u/webstock_zt)\
**Post date:** [May 6, 2022, 1:06am UTC](https://forums.percona.com/t/all-pmm-mongodb-monitoring-services-are-not-working/15449/10 "2022-05-06T01:06:09Z")

</div>

Hi@Punnet, After testing the deployment, we have found that the problem occurs in the network bandwidth bottleneck. thanks for your help!
