Whenever we want to make changes, eg. set a new parameter or add new parameter in configuration (advance configuration options), after we save changes, review and deploy, automation immediately starts applying that change and does a rolling restart.
We need flexibility in restart, means one should have an option to perform immediate rolling restart or defer it to later time. We may apply multiple changes at different times and set one preferred window to restart instance instead of doing multiple restarts.

OpsManager currently supports the S3 implementations of AWS, IBM Cloud and Dell EMC Elastic Cloud Storage. We would like to use our existing Cloudian S3 storage. We've used it for a while now and it works, but we suggest making this an "officially supported" flavor, too.

Under a project, Now if a user id created, it gets created in all deployments in the projects. Can we have provision to choose which deployment the user gets created.

For example, for project A, we have three deployments rs1, rs2 & rs3. Now under security tab, if we add a users, this user get access to all deployment. can we have a choice which all deployment the user exist.

when you press link "delete daemon" on Admin->Backup->Daemons page it "deletes" daemon from this page, but after mongodb-mms.service gets restarted, this daemon comes up again. this link does not delete daemon - it actually deactivate backup daemon. another part for deactivation of daemon is to modify settings for service mongodb-mms to start only mms application without daemon.

Currently records in mms0-startup.log and daemon-startup.log only have time stamp in the format: hour:min:sec,milliseconds.
eg. 08:28:09,558 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]

It would be useful to include the full date/time stamps to each record as currently we can't say to which day do the records refer to.

At the moment only one webhook URL can be configured for one Ops Manager project.
It would be nice if multiple URLs could be used to send the alert to different endpoints by using f.e. a delimiter character inside the config.
Thanks and regards

To be able to set up Archiving in Ops Manager so you would be able to keep a certain amount of data in Prod and move the rest of to an Archiving replica set.

In the sharded cluster monitoring overview it would be useful to also have the option to display the Process CPU usage to quickly identify shards which have a higher CPU load. Other hardware metrics might be useful as well.

Capability to use JWT or SSL certs would be great.

Allow MongoDBUser CRD to interact with a MongoDB resource in a separate namespace in k8s.

The goal is to have different teams deploy their resources (including applications, configmaps, secrets, PVCs, MongoDBUser CRDs etc) into their seperate namespaces, but have all of them share a single MongoDB replicaset in a common namespace such as mongodb

When Ops Manager is under heavy load from many active database services, f.e. to handle backup snapshots, the recommendation from the case support portal is to use a loadbalancer in front of Ops Manager.
It would be great, if Ops Manager could have this as an integrated functionality to forward connections from agents to additional Ops Manager instances.
Background: Our nTSE did confirm, that we could set a different Ops Manager URL in the agent config, but the transferred data from this agent is still sent to the initially configured Ops Manager instance.

Before MongoDB version upgrades we should verify all drivers compatibility for the new version.

It is sometimes difficult to track all of the drivers used connecting to the deployments. Currently it requires parsing of multiple mongos/mongod logs for client connections or internal code investigations.

Suggestion

It may be beneficial to collect and present clients statistics (version, type, IP) data on Ops Manager.

Maybe this could be a feature that can be toggled on demand.

Currently it is required to enable automation on a cluster in order to monitor system level statistics such as CPU.

As automation is sometimes not desired for a cluster, please add the ability to gather system level metrics when a cluster is monitored only.

Ops Manager to support Credentials Cache to connect to APP DB
Its related to case opened : Case: 00881812

Also change alerting ( Email Subject )

Currently we get alert with email subject as below even if issue is resolved
System Alert - Backing Database Connection is Unhealthy

We Should change alert email subject to Say "Healthy " instead of "Unhealthy " when issue is resolved.

Our LDAP server is quite slow, so we sometimes get technical errors when trying to log in our Ops Manager instance.

We would need add an option to set LDAP server response timeout on Ops Manager side. It could be mms.ldap.timeoutMs.

(I'm refering to Ops Manager authentication, not to MongoDB deployement authentication)

In secure environments, it is required that webhook endpoints are secured with basic authentication at a minimum. Currently, Webhook alerts only provides an HMAC-SHA-1 signature.