Clearly users of Ops Manager use it because they have a requirement, keep MongoDB clusters within their own infrastructure.

Well, we have two solutions for that Ops Manager and also Cloud Manager. I personally think if we have automation in the product to move from the Ops Manager control plane to the Cloud Manager control plane it would make it easier for users to take advantage of MongoDB's backup infrastructure and keep updates coming without the hassle of managing it all by themselves.

Automatically restore user access rights after a major version upgrade through Ops Manager.

Is it possible to configure ops manager to allow “pre flight checks” to not fail with a single mongod configured as replica, but without any secondaries. i.e. only primary, which is allowed, because mongod runs anyway, even without P-S-S only P ?

Hello,

On a sharded instance, I try to identify the connected physical people.
It is not easy. I cannot identify my own connection. 😦

Can we have a command to find out who is connected to the platform (excluding host2host connections, backup process, ...)?

The closest command but not complete and friendly :
use config
DBQuery.shellBatchSize = 300
db.system.sessions.aggregate( [ { $listSessions: { allUsers: true } },
{ $project: { _id: 0, "user":"$user.name" } } ,
{ $group : { _id: {"user": "$user" }, count: { $sum: 1 } } },

])

Regards
Jerome

I am working on automation for creating organization using API. It allows to create multiple organization with same name. This should not be allowed.

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.

Replica Set horizons cannot be set through the UI currently. It is possible to set through the automationConfig via the API but this is complex.

This would be useful for 2 use cases:
1. When a cluster is self-managed and using technologies like AWS PrivateLink
2. When a cluster is network isolated and connections must go through a proxy device

1. Create report about Mongo OPS users (ability to filter by Admin roles, Last Login, Created, Status)
2. Create user report for All Mongo OPS Projects. Mongo DB Users (Filter by Organization, Project Name, MongoDB role, Auth database Synched/Not Synched)

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.

Capability to use JWT or SSL certs would be great.

In Ops Manager, it is not possible to obtain some data from each snapshot via api, it is only available in ops manager interface. It is a good a idea to obtain from each snapshot the information of the backup resource usage. The api could return this information: "Store Type, Store Id Live, Compressed Bytes Dead, Compressed Bytes Compression Ratio, Last Groom, Last Track"

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?

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.

Can we have add dashboard feature in ops mgr which can give consolidated metrics of all RS.

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.

Sometimes it would be great if we could move the conf, tmp, or logs directories to other filesystems and use symlinks so that Ops Manager doesn't have to worry about where the needed file physically are. Right now, Ops Manager refuses to start whenever this sort of redirection is done.