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 ..

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.

I access Mongo Cloud / Atlas very frequently. However, almost every day I need to re-login using my Google account. It doesn't seem to "remember" my session.
I would love if I can extend the default, and let me (and other members) stay logged in for a longer period of time.

When indexes are built from an application or a mongorestore there's no way to see if it's ongoing in the UI.

There should be an indication in the "Real-time" tab saying that an index on collection X is in progress. This would explain why performance is currently impacted.

It would be good to see index start and end marked on the "Metrics" visualizations so we can see the impact of index builds on IOPS, CPU, memory etc. This could help understand if we need to upscale the cluster.

Atlas Monitoring UI is great, but to ease centralization of alerts and dashboards..., it would be nice to have all atlas metrics in Cloud Monitoring too.

Ability to add indexes after new clusters are created using Terraform and data has been loaded. It will help in more automation and auto recovery.

MongoDB will email Atlas customer when the prepaid Atlas credit is estimated to be exhausted within 30 days.

However, it would be good to have an alert for this in Atlas, e.g.

Alert if the remaining prepaid amount is lower than ... <an amount>

Please include the human-friendly cluster/host names in Monitoring Alert Notifications (e.g. email, PagerDuty, etc) in addition to, or instead of, the less clear internal cluster/hostnames (i.e. atlas-abcdef-shard-0).

The Legacy Backups have a feature to allow connecting (tunnelling) to a snapshot to query it. This allows querying a database snapshot which is great for quickly inspecting data in the past for troubleshooting. This would be handy to have for the Cloud Backups. With Cloud Backups instead I now have to download a snapshot, load it temporarily on a cluster and remove it when done.

We would like to consume your status RSS feed to help us programmatically warn our internal groups when you have issues in a given region. One problem that we see with this is that the messages that we have seen posted are pretty inconsistent with how they specify regions. Examples: Oregon (us-west-2), AWS EU-WEST-2, AWS Sao Paulo. It would be very helpful to us, and probably your other customers as well, if the messages were more consistent in how they reference AWS regions.

While creating indexes using MDB atlas, there is no option to select from a list the fields that we want to add for indexing. For ease of use, this functionality must be added to Atlas GUI.

It would be ideal if there was some native way to send Realm application logs to Splunk (and other third-party log aggregation services), instead of having to build an application in a separate environment to poll this API endpoint (https://docs.mongodb.com/realm/admin/api/v3/#logging-apis) and push logs to Splunk from there.

What is the problem that needs to be solved? Customers are willing to troubleshoot / analyze Atlas BI Connector logs by themselves (they would like to investigate schema sampling timings, SQL/MongoDB query optimizations, connectivity issues, etc.).

Why is it a problem? (the pain) Currently available Download Logs option on Atlas Clusters does not include Atlas BI Connector process logs.

We have databases with many collections. The problem with that is that in order to select certain collection, I have to scroll the results part of the page. So I'm going up and down all the time I select another collection and make some query.

In sum, please add scroll in the collection explorer UI.

Regards

I really need to delete my account as this is not what I am looking for.

It would be nice to have the killOp() action exposed when creating a custom role in Atlas.

I also think it would make sense to grant this action to the atlasAdmin role, but at a minimum I feel that Project Owners should be able to create a custom role that is allowed to kill ops that were initiated by other database users.

Currently is not possible to enforce any kind of password policy via Atlas UI.
Would be nice to let user define an expiration time and password policy that user should meet.