The profile page would be more use if the listing included the username so you could work out which application was making the queries.

on MongoAtlas metrics dashboard, I can organize graphically different metrics as I want to display first "insert" metric for example, then "cpu" metric, etc ...
If I change this actual order, then I go to another screen (for example "network access") and finally I come back to this metric dashboard, my new metrics added (insert, cpu, ...) in first position are not in wanted first position (at the top of metrics list), but at the end of this metrics list.

It would be great to keep metrics context (displayed metrics and ordering) on Metrics dashboard.

Currently, features to give insight to slow/optimisable queries are only supported on non-shared instances (i.e. M10+). Would like to see this for shared instances too.

On a side note, this was possible in the cheaper mlab.com setup, which was forced into Atlas.

Recently, Atlas introduced a feature that shows a cluster will have its MongoDB server version upgraded to the next dot version. This is displayed on the cluster card in the UI. However, this information is not surfaced in the Activity Feed or through any maintenance endpoints in the API. We would like to be able to identify when maintenance includes a MongoDB server version upgrade and do so programmatically.

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.

add more IP ranges for VPC peering on Google GCP network in Google Cloud environment. https://cloud.google.com/vpc/docs/vpc#valid-ranges is supported. Docs only show RFC1918 IPs. https://docs.atlas.mongodb.com/security-vpc-peering/#in-configure-your-network-peering-connection-2

It would be ideal if the alert notifications for Query Targeting ratio alerts included a reference to the query shape that caused the alert to fire. This would assist customers in locating the exact query/queries with poor targeting ratios so that they can be optimized in a more expeditious manner.

It is really helpful to get use of indexes in numbers in last 24 hours to eastimate the use of particular index.

can you make it so that you can connect from mongodb like you would in mongoose

Having the ability to extract/export the Performance Advisor report. This would allow users to share a file with others who may not have access to Mongo Atlas.

In the API documentation you mention a regions parameter usable when creating a network container with a network smaller than /18. In terraform there is no such parameter. I would like to see that supported (for creating networks smaller than /18 on GCP).

See: https://docs.atlas.mongodb.com/reference/api/vpc-create-container/#request-body-parameters

When adding IP addresses on a cluster/project (Network Access), it would be great to be able to provide a comma-delimited list of IP addresses instead of having to enter them one-by-one.

When filling in the password field in Atlas user, sometimes I click show then start typing a new password, or Home/end to highlight it. Somehow half the time it dismisses the dialog and I have to start over.

I suspect it is the dialog losing focus. Stop dismissing the dialog when I click off of the box. Other dialogs do the same thing. A lot of web apps do that now and it seems really dumb -- save one specific Cancel click to aggravate me many more times when the dialog I have worked on for 5 minutes disappears.

At the moment, Project Timezone setting can only be done via Atlas UI. We are automating project and cluster creation and setup for our application. We need an API to update Project Timezone setting just like other project settings. This feature is important for our organization to keep all the project with the same settings without a manual intervention.

Currently there is no way to test how applications behave during maintenance apart from waiting for maintenance, the ability to force a rolling cluster restart as happens during maintenance would be great. The failover is a different process and affects primary mainly.

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.