Please release a dark mode MongoDB Atlas interface. Thank you.

It would be great if I could connect to and run commands against my cluster via the Atlas UI so I don't have to rely on downloading and running the shell locally.

I'd also be more confident I was running commands against the right cluster as I would have less reliance on managing connection strings and differentiating between them. This would be helpful if I'm not on my regular machine and need to do some ad-hoc querying or debugging.

Right now, there's a "test failover" option, which shuts down the primary and forces an election. However, the option is only available if the cluster is in a healthy state.

If, for whatever reason, the cluster is unhealthy, it's impossible to manually restart the primary. It should be possible to force an election in an unhealthy state. Often, this is all that is required to get back into a healthy state (e.g. if the primary is in a CPU burning loop that was caused by an unexpected write pattern that has stopped.)

There's no way to stream logs from MongoDB on Atlas right now. I should be able to stream logs, either to Datadog or Cloudwatch or something!

Mongomirror allows you to migrate particular databases or collections using the --includeDB and --includeNamespace parameters:

https://docs.atlas.mongodb.com/reference/mongomirror/#cmdoption-includedb
https://docs.atlas.mongodb.com/reference/mongomirror/#cmdoption-includenamespace

It would be helpful if Live Migrate allowed for use of these options as well to migrate subsets of data, instead of only migrating an entire cluster.

Alerts are often very cryptic & don't provide any useful information. For example, when alerting that queries are returning too many rows, without informing me the query or at least the collection, that's very useless. I'm looking at a replication oplog window alert right now and I have no idea what to do about it.

Hi.
We would like to have the possibility to administrate user rights also for the Billing area. In order to restrict all users seeing the invoices and to give this right only to particular people who are directly responsible for it. Please consider such feature for the next releases.

mLab had the option to create a single-node deployment, which was very nice for development environments where redundancy isn't important, but keeping costs down is.

Would be nice to see this in Atlas as well.

Allow the "SET GLOBAL mongodbmaxvarcharlength = n" to be permanent after a Mongosqld restart. Currently, the setting is ephmeral and must be set everytime the mongosqld daemon is restarted. Currently, our production environment mongosqld can restart without our knowledge at anytime. This results in the mongodbmaxvarharlength variable being reset to zero, which can lead to a production outage. Is there anyway this can be automated, maybe through database trigger?

To effectively use Workload Isolation, it is desirable to have different indexes on the operational cluster nodes than the indexes used to support analytics and reporting query patterns. It would be powerful for Atlas to enable different indexes on Analytics nodes.

Whenever Atlas wants to do maintenance, it is sending email alert about the timing of maintenance. In addition to that we are requesting information about the nature of maintenance also like Mongo patching , BI connector upgrade or increasing no of connections etc. This will give us the information about the work and we can broadcast the same to our counterparts so that they can also use the product efficiently.

The current "Test Failover" feature supports testing application/driver resiliency in case of elections. For additional testing, we want to be able to cause a node or nodes to be shut down and started up in a cluster. There should be selectivity allowing the entire node or just the mongod or mongos process to be shut down and started up.

An option to protect the "Pause" action on clusters with 2FA would help to reduce the chance of accidental pausing of production systems.

Provide Peering support for "Classic" (Hub and Spoke) VNet Peering topology, either directly or via a NAT

Alerts can be configured to send to specific Atlas Users, but not Atlas Teams, which diminishes the value of setting up a team of users.

I'm trying to get logs from MongoDB Atlas to Splunk, and there's currently no native interface to do it, so instead of streaming to Splunk directly, I'm having to execute https calls in intervals, unzip them and then ship them to Splunk. Many products have interfaces to stream to Splunk directly, and it would certainly be handy in this situation.

Since Atlas clusters now support different sets of hostnames, it would be good to explore the feasibility of allowing users to add their own hostnames to the cluster configuration and TLS certificates such that custom connection strings can be used.

One use case for this is being able to "wrap" Atlas connection strings, such that an application's connection string would never need to change despite underlying cluster changes (cluster being moved between projects, etc.)

This could also be useful if you wished to whitelabel your cluster.

Mongorestore allows for the number of concurrent insertion workers per collection to be increased using the --numInsertionWorkersPerCollection option.

However, this is not available for mongomirror -- while you can increase the number of collections copied in parallel (--numParallelCollections), there's no parameter surfaced to allow more inserts to be occurring at the same time over multiple threads within each collection.

|t would be helpful to have a parameter like this to use to increase parallelization in order to increase the speed of migrations of large collections.

If I already have Cloud Manager backups, or can take an EBS snapshot, I want to be able to quickly Live Migrate this replica set to minimize migration time and load on my existing infrastructure.