mongodb_monitor on Windows Server 2016?

[Olaf Pape]

Hi,

a newly deployed mongedb_monitor probe on a MongoDB-Node running Windows Server 2016 won't start.
There are no helpful messages in logfile except "Max. restart reached for probe". 

According to the Probe Support Matrix the mongodb_monitor probe is not compatible with Windows Server 2016, Windows Server 2012 is still supported.
What could be the cause that mongodb_monitor runs under 2012 but not under 2016. Is there a possibility to run the module under 2016 (like Compatibility Mode)?

Otherwise, I guess the only thing left to do is to open an idea that is voted for too few people.

[David Michel]

Looks like you have it correct:
The probe requires the following software environment:
MongoDB version 3.0, 3.2, 3.4, 3.6, or 4.0 running on Windows (2008 R2 or 2012 R2), or on Linux (RHEL 7.x or CentOS 7)

------------------------------
Support Engineer
Broadcom
------------------------------

[Olaf Pape]

Hi all,

almost a year has passed and there is no new information on the mongedb_monitoring probe. The current mongedb_monitoring version is from June 2019 and still does not support a actual Windows operating system. The supported Windows operating system (2012r2) has no longer been in mainstream support since 11.2018.
If the mongedb_monitoring probe is no longer being developed, then this should be clearly communicated so that the customer can look for an alternative.

Regards,

[Andrew Cooper]

Olaf

I am "lucky" that we have a very old implementation of mongodb which just fits into the support matrix however they are working on an update of the application which wll update both the OS and mongodb so that it will nolonger be in the current supported matrix (no current OS or monogo version is).  So like you I would like to know if  this monitor is still "developed"?

Regards, Andrew
​

------------------------------
Knows a little about UIM/DXim, AE, Automic
------------------------------

[Ravishu Arora]

Hi All,

We understand that this has been overdue, but the MongoDB Monitor probe is very much in development and under continued support.
We have just released the new v2.10 probe which is certified to work on Windows 2016.

Please refer to the details in this post.

------------------------------
Principal Product Manager
Enterprise Software Division (ESD) | Infrastructure Software Group (ISG)
Broadcom
------------------------------

[Olaf Pape]

Hi Ravishu Arora,

thanks for your reply. We will give it a try.

[Olaf Pape]

Hi @Ravishu Arora,

we tested monegdb v2.10 and ran into problems.

1. Our MongoDB user has the role readAnyDatabases. I think that is not enough for reading statistics a.s.o.
2. Due to the wrong user permission or to another error in the config the probe restarts without interruption and does not stop. With each restart, a dump file (approx. 500MByte) is created so that the disc quickly fills up. Depending of the disc size the server runs out of disc space within a few minutes.

a) Could you please provide the user role needed for mongodb_monitoring probe (and put this info also in the docs).

b) Build in an maximus restart count of three or five in the probe. 

Thanks and regards,

​

[Ravishu Arora]

Thanks for the feedback @Olaf Pape!

To create the proper role needed by the probe, please refer to the below KB article:
https://ca-broadcomcsm.wolkenservicedesk.com/wolken/esd/knowledgebase_search?articleId=102345

We are working on getting this updated in the documentation as well.

Let us know how it goes!

I shall meanwhile investigate the best way to avoid filling up the disk space with these dump files for a future enhancement.
​

------------------------------
Principal Product Manager
Enterprise Software Division (ESD) | Infrastructure Software Group (ISG)
Broadcom
------------------------------