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

In the Atlas UI, allow to add a description in the IP's allowed to use an API key. This may improve security and ease management as it allows to easily maintain this list up to date.

Would be nice to export the database access history and/or sort by a column.

When I log on, the sms for the second authent factor is not sent, I have to require one to get it

I work with hundreds of collections, and I have two issues with the UI that make a not optimal UX:
- my collection names are large, and the collection list is not resizable.
Alternatively to resizing, a popping up tooltip could show the full name of the collection being hovered with the pointer

• the list of collection scrolls with the rest of the page. when I want to search a collection at the bottom of the page I have to scroll down to select it, and then scroll up again to see the results.

Currently we can only restore full cluster from backup like snap using GUI interface. If we want to restore one or more specific db, it needs manual dump and restore from backup. if we have an option to restore specific db to cluster through GUI interface, it will be very useful.

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.

In the old interface we can truncate collections without using additional software, just using WEB GUI to keep small database size.
It would be nice to have the ability to delete older documents. This option is usable for IOT or medical implementations (Nightscout).

our event-driven applications need to publish events to Kafka triggered by Change Stream feature. It works perfect in replicaset MongoDB cluster.

However, after migrating to Global Cluster in Atlas, the Change Stream cannot keep low latency because of ordering reason among shards.
The latency may go up to 20 seconds when for a single change event.

It would be nice if application can receive Change Stream from the single shard only (not care about ordering among shards) to prevent latency.

The idea is to pass "location" options when starting the Change Stream cursor.

hourly backup retention. Why minimum a day, so 24 backups stored? For big databases, this is an amount of data and money

Atlas clusters don't support the setParameter command and, as a result, users aren't able to configure log levels. I understand the reasoning behind not exposing permissions to run setParameter to DB users so, in lieu of that, it would really helpful if Atlas users were able to configure log levels through the Atlas UI, preferably at the Node or Cluster level.

Thanks!

Atlas exposes a few hardware metrics including Util% (presumably obtained from iostat or similar). However this metric is not very significant in the age of SSDs - a volume could be 100% utilized and still have spare capacity. A more useful storage-level metric is Average queue length - this is easier to interpret (high queue length = storage contention).

Would it be possible to add this metric to Atlas monitoring?

My cluster operations is at 100 and i don't know what's causing that. I would appreciate having a console to see what are those operations

It would be great if we could organize the projects and not have them all at the same level of organization.
We could use this hierarchy to put rights, consult costs ...
A bit like the idea of Azure's management group or GCP's "Folder".

We would like to be able to use Terraform to configure LDAP authentication/authorization on projects.

The functionality is available via the API:
https://docs.atlas.mongodb.com/reference/api/ldaps-configuration/

However, go-client-mongodb-atlas does not have these endpoints implemented, so that would need to be done before this functionality is included in the provider.