When reviewing changes in automation, warn if deploying changes will require a rolling restart.

As an example, look at the documentation for server parameters: https://docs.mongodb.com/manual/reference/parameters/

Many parameters include the description "You can only set THIS during start-up", but a warning that setting this parameter implies restarting MongoDB is missing from Ops Manager (or Cloud Manager).

Currently our Ops Mgrs keep re-downloading EOL releases of mongodb, e.g. mongodb-linux-x8664-2.6.12, mongodb-linux-x8664-3.0.15, etc. Ops Manager should automatically exclude EOL releases - they are taking up unnecessary disk space.

In order to better troubleshoot snapshot performance issues, or maintain an understanding of how snapshots are performing and whether one is approaching a threshold where they wont be able to keep up, its a good idea to expose how long a snapshot took in the View All Snapshots page. This would also aid in quickly identifying which snapshots are full vs incremental.

Hello,

I have an idea about the Keyfile rotation. So actually you can rotate the Keyfile only through the ops manager manually. But I would recommend to do this automatically with an API. This would help us alot since we have alot of mongoDB instances and this would save alot of time.

By default, when enabling backups and configuring a Blockstore for an Ops Manager custom object, the specified Blockstore will be set as "Assignment enabled" in the UI.

It would be helpful to expose the enable/disable button for the blockstore through the CRD since disabling it through the UI, results in the parameter being reverted every time the operator consolidates. This is useful for the case when more than a single store is configured and as a user you would like to disable the blockstore to make it unavailable for new backup jobs.

Currently, there is no way to enable LDAP Auth for the Ops Manager Users via an API call.

This essentially means that one would not be able to use LDAP and ci/cd simultaneously with Ops Manager.

Mongodb enterprise support has confirmed that in the event of disaster recovery or a deployment of a new cluster, manual steps must be done to enable LDAP during a ci/cd deployment.

It should not be expected to sign in and manually do anything in a web gui in an enterprise solution. It is simply not scalable.

The login page for Ops Manager 4.4+ shows "Email Address" and "Password". While using other login methods such as LDAP, an email address may not be used.

It would be more accurate to say username here.

Since Ops Manager APIs seem to be very similar (if not, the same) as Atlas API, and since Atlas Terraform modules seem to run based on Atlas API, it would be very nice to have Terraform modules for Ops Manager.

Add third-party service integration for Microsoft Teams, as we do for Slack.
Most likely the following can be leveraged to achieve the integration: https://docs.microsoft.com/en-us/graph/teams-proactive-messaging

We would like to have an option in the Ops Manager UI to select certain MongoDB versions to be automatically downloaded by Automation in order to avoid downloading all major binaries.

It is not good to have several MongoDB binaries using disk space and not being used.

With Ops Manager Local Mode on Kubernetes, the version manifest is required to be updated manually via UI or API.

It would be the best practice to support updating version manifest using a command to the Operator or OM Pods.

Having a dark theme switch in the Ops Manager account personalization settings would be nice!

Hi all

We would like to enable auditing for activities in Ops Manger itself, getting the information directly using the default audit logging options (filesystem / syslog).

Currently we are getting the detailed information in OpsManager, we get some information in the audit.log log when config changes are made via Ops Manager, but not in detail what exactly had been modified in the log files.

To establish a holistic, company wide auditing spanning over all levels (OS / DB / Application) taking use of standard auditing tools this would be highly beneficial.

Regards, Roger

The lab task currently can be solved without paying attention to the difference between the $lt vs $lte and $gt vs $gte operators:

MongoDB Enterprise atlas-7ooiae-shard-0:PRIMARY> db.zips.find({"pop" : { $gte: 5000,$lte: 1000000}}).count()
11193
MongoDB Enterprise atlas-7ooiae-shard-0:PRIMARY> db.zips.find({"pop" : { $gt: 5000,$lt: 1000000}}).count()
11193

Adding two more documents (one with 5000 and the other one with 1000000 "pop" value) would draw attention to this difference

Allow changing SNMP port from default (162) for customers who run SNMP on non-standard ports.

Currently the port number of the SNMP trap receiver is hardcoded to 162.

Document list of Alert conditions that post to the Activty Feed but not Alerts page
It seems like some "non-actionable" alert/event conditions (example: Host has Restarted) post to the Activity Feed but not the Alerts Page.
Notifications are sent.
I cannot find a list of these that post only to the Activity Feed so it would be nice to have them documented.

Supported Ansible modules for MongoDB. Maybe a module for self managed and Atlas.

This feature request is for a new Group/Project API call for the management of the host mappings created in Ops Manager from monitoring information. Whether it be an endpoint for "Reset Duplicates" or full featured create/delete of individual host mappings, both will alleviate issues where overlapping mappings affect monitoring in Ops Manager.

Note: The issue of overlapping mappings may occur when a mongod process has moved/changed IP addresses multiple times. With enough cycling (as seen in Kubernetes clusters with frequent pod restarts), eventually a previously mapped IP address may now be associated with a different mongod process.

As a DBA using Ops Manager, I want to get an alert when a collection is a certain size or near no storage so that I can do an investigation to see if there is abnormal data growth. As of right now, I can only monitor cluster data size.