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.

It would be nice to get quick access to the name of the replica set from the cluster overview page.

The Disk IOPS graph shows 2 colored lines. (read/write). It would be great to add a third line which is the SUM of the 2 lines. Or... a toggle switch so we can see the sum line instead of the 2 components. Thanks!

Mongorestore allows for the number of concurrent insertion workers per collection to be increased using the [--numInsertionWorkersPerCollection](https://docs.mongodb.com/database-tools/mongorestore/#std-option-mongorestore.--numInsertionWorkersPerCollection) option.

However, this is not available for mongomirror -- while you can increase the number of collections copied in parallel ([--numParallelCollections](https://docs.atlas.mongodb.com/reference/mongomirror/#std-option-mongomirror.--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.

What is the problem that needs to be solved? As a user (MongoDB Driver) you'd like to check revocation status of X.509 certificate via TLS Certificate Status Request extension (also known as OCSP stapling) instead of doing outgoing HTTP connection to OCSP endpoint from a user (MongoDB Driver) side.

Why is it a problem? (the pain) [MongoDB Server v. 4.4.X introduces OCSP stapling functionality](https://docs.mongodb.com/manual/release-notes/4.4/index.html#ocsp), however OCSP stapling is not enabled on Atlas Clusters with MongoDB Server v. 4.4.X.

It is currently not possible to create empty teams of remove all users from teams.
We would like to arrange our access management through teams. For our production environment we want a 'read only' and an 'admin' team. The admin team should be empty at all times, except in the case of incidents where we want to add specific users to the admin team to be able to solve the incident.

Add Test Failover permissions to the Project Cluster Manager role.
Use Case:
We'd like to have folks with this permission without also allowing them to modify Project membership and all the other permissions that come with being an Owner.

Currently there is no way of managing an online archive besides nuking the entire collection. This means that the collection can only grow, so costs will continue to climb.

The TTL index can already be used to automatically delete documents from your database. If this could be expanded to also delete files which have been archived, there is an easy and built-in way of maintaining an archive in size.

Hi
Presently, we can only create permanent database users via Terraform Modules. The creation of temporary DB users is only allowed through the UI or by consuming MongoDb Atlas's APIs. In addition, the "deleteAfterDate" property is only applicable for a temporary user already existent. The point is to avoid using "null_resource" and "local-exec" in our Terraform Modules.

We have a need to rename our databases as we sync them over to Atlas. However, mongomirror doesn't support that. So that leaves us with mongodump and mongorestore but our databases are large enough that we can't take the outage window necessary to go down that path. When will mongomirror support renaming databases during the import process?

since as documented there are limitation on network traffic in M0/M2/M5 instances, it is mandatory to have a metrics/alerts (also for free ones) to monitor this value in a 7d sliding window

The "Host has index suggestions" alert notification does not contain any reference to the host/deployment that triggered it making it hard to figure out where it came from. A hostname reference would be very helpful.

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 nice and convenient if lower-tier users could have the cloud backup option available (I believe m5 is the smallest but it's $9/month). I use m0 for one of my projects and I know mongodump is an option but I would much rather pay $1/month extra for backup capabilities. This project is quite small and I don't need much resources, but I would like the ability to scedule daily backups for a small fee.

There is no good monitoring or alert functionality for dealing with potential invalid login attempts.

I suggest an alert setup to handle events when known users fail more than 3 times to login (either in Atlas or via driverlogin to db).

We have had an external audit done and this is something they have found as a shortage in the MongoDB Atlas environment.

Log files are good but not to monitor potential security issues

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