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.

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.

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.

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!

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

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.

Upload good tutorials in YouTube about connecting mongodb atlas with available three options.

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.

I need an API that will allow access to the items under credits in the billing page.
This will allow me to pull this information daily into our master usage database to support our dashboards

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.

Azure VNet Peering is currently very limited as access is only possible from the VNet that is peered.
Could you please support access from onprem via private network (Express Route or S2S VPN) and Gateway Transit.
Maybe another way to achieve the same could be via "Private Endpoint".

Enable connectivity in Azure using private endpoints

Test environment are usually paused during the night and the weekends. Currently the only way to do that is to automatise a RestAPI call or call mongocli automatically (e.g. via crontab)
Would be nice to allow to define a time windows on which the cluster stays pause via UI

Would like the option to view collection pages by 10, 20, 50, 100. Along with ability to move to (<first) (last>). Similar to mLab

a cluster has been in development for awhile .. but as new cluster are created within the project.. we'd like to change the cluster name ..

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.