Do you have a plan to keep the option in future releases to gather audit log from Ops manager? I don't see any option now

I wanted to manage the Ops manager apps db logs in more refined by way by enabling "Size per Log Type in MB" and "Total Number of Files" settings in mongod.conf.
How ever I don't see any options "Size per Log Type in MB" and "Total Number of Files" but same avaiable in ops manager UI for agent managed replica set. Do you have a plan to add these options in mongod.conf in future releases for apps DB?

Webhooks are available for Project and Global Alerts. However they are not available for System Alerts.

It would be ideal to be able to use Webhooks for all alerts.

Ops Manager should allow Data Explorer to be configured with a Read Preferences and maxTimeMS options. Not having these options allows this tool to potentially trigger un-optimized queries to only hit primary nodes, which for high load production environments may cause un-expected problems.

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.

MongoDB will abort if ulimit parameters are set too low. We should monitor parameters such as "open files" and add an alert for when the value approaches the ulimit configuration.

Add a filter for Global alert Configuration Page. It would be nice to have the ability to search for the specific alert to see if you have it configured and for which environments.

A filter similar to what is seen on the "Open Alert" view would be sufficient.

Since we are managing upwards of 50 deployments via Global Alerts this would be a useful feature.

You can set MongoDB log rotation for mongod process on project level in the Ops Manager through: Deployment -> More -> MongoDB Log Settings. However there is no option to set it via API.
It looks like there is option to set this parameters on process level (in the Automation Config), but Ops Manager is not accepting new value, like it does when setting values for Monitoring Log rotation and Backup Log rotation.
It would be great to have option to automate this when creating a new project via API and setting all other attributes with script.

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.

We need to ability to trigger replica set alerts when a secondary that is hidden goes down.

In this example an environment has 4 members, with one of them "hidden". We would like to be alerted even when the "hidden" secondary goes down.

Currently alerts are only working for non-hidden members.

The ops manager api documentation specifies endpoints for polling group alerts and global alerts but is missing system alerts. We should be able to poll for system alerts via the ops manager api as well.

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.

Some parameters for Datadog are not configurable in Ops Manager. For example, "tagging". Adding this functionality would make using Datadog easier.

For users running DBaaS MongoDB products powered by Ops Manager automation, it would be useful if the API provided a way to replicate the cluster import behavior where MongoDB users are automatically discovered. This would help in scenarios where an existing Ops Manager deployment fails, and hundreds of deployments need to be moved to a different Ops Manager without knowing what MongoDB credentials the end user of that deployment had created. Having this API would allow the DBaaS provider's own scripting/automation to orchestrate moving these deployments to a new Ops Manager stack with reduced downtime.

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.

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

Ops Manager UI (4.0 -4.4) does not allow downgrading of Feature Compatibility Version (FCV), once the FVC has been upgraded to a higher version. Ops Manager automatically
removes the lower version from the supported FCVs once upgrade completes. But the cluster deployment allows downgrading one level using shell commands. This limitation makes it difficult when planning an upgrade as regression process are more difficult.
We are in the process of upgrading the environment from 4.0 to 4.4 (which requires an intermediate upgrade to 4.2.). So the downgrade process is so difficult with Ops Manager UI.