The ability to Test Failover was added to Atlas https://docs.atlas.mongodb.com/tutorial/test-failover.

Please add this functionality to Ops Manager in order to facilitate failover testing. This is especially useful in multi-tenant Ops Manager setups.

Why doesn't MongoDB provide a tool (integrated or standalone) to operate document migration across on-prem (sharded) clusters? Suggestion might be to officially support tools like "mongo push", which may cover situations of hardware changes, production servers migration, re-sharding.

Allow the possibility of performing a snapshot on-demand.

Usually the snapshot time ends too far away in time after configuration changes of the backup job (i.e: changing the block size). For testing purposes it would make sense to allow performing a snapshot on-demand to get it generated and proceed with further testing/tuning if required.

SAML is available as an authentication mechanism and we're currently using it with keycloack (centralized identity provider).

It works well with Ops Manager but there seems to be no support whatsoever in Ops Manager 4.4 API to programmatically add / update / delete SAML groups on Organizations or Projects.

The official API documentation doesn't even recognize that SAML is available.

Mongo support has confirmed that and it's a target feature in their internal backlog.
This idea will hopefully speed up things.

If you are using local key file encryption and backing up your MongoDB deployment using Ops Manager, backups won't work correctly if you upgrade to MongoDB 4.2. The correct solution is to switch your encryption to KMIP. But if you try doing that, automation will get stuck!

Atlas -> please make buffers, cached, and MEM shared available under system memory metrics on Atlas for end users so we can calculate the criteria for auto scaling .

Currently only Mongodb support can see these three metrics

It would be useful to have a "Test Alert" button for each configured alert in order to integrate and test alerts with third-party systems. Otherwise, it is difficult if not impossible to determine what the alert will look like until it is triggered.

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

Right now if you want to change the credentials for the monitoring agent or the backup agent, you've got to make separate API calls. Why not make it so that you can specify everything at once in the same automationConfig API PUT?

We should expand the Ops Manager API to provide mms0.log downloads the same way we allow mongod deployment log downloads. This will help users with diagnostics when they deploy many Ops Manager instances via the kubernetes operator but do not yet have centralized logging.

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.

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.

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

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

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.

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.