It would be helpful to be able to view the resources used by the BI connector in Metrics, similar to how you can view resources used by Atlas Search (Search Disk Space Used, Search Normalized Process CPU, etc). This could help with identifying issues due to resource intensive queries submitted through the BI connector.

Currently it is only possible to guess that an issue could be related to the BI Connector by viewing system resource use.

If the user has 3 peering connections in a project, it's error prone terminating one, as you may end the connection with the wrong VPC and cause a disaster. Adding a description field allows to clearly see the purpose of the peering.

When a cluster update happens and things change such as the certificates, why wouldn't this show in the activity feed? The only thing noted in a recent issue we had was "cluster update". If we could see the details of the update we could have resolved our problem quickly without opening a case.

Given that I address certain kinds of queries to certain tagged nodes,
As a developer,
I would like to filter the "real time view" tab to show only activity for my tags
So that I can monitor how my application impacts its node

add an audit log even when any user within the organization creates a new project. Currently you can see when a collection is created, but nothing for new projects. This is helpful for auditing and accountability purposes.

We have a security reqirement that secrets must expire after 2 years.

Therefore it would be awesome if MongoDB Atlas API Keys would support an expiration date.

Somethig similar exists for the IP Whitelisting. Here we have the option to remove IP Whitelist entries after er certain time period. But for API Keys it would be better to have an expiration date and keep the API Key in the list even if its expired.

In addition it would be good to have a daily notification once the expiration date is ahead less than 30 day.

Support multi-cloud as available in the Atlas UI

This metric will show the available bytes for reuse. If it's too much and its graph is changed a little bit, we can decide to compact it for saving cost (from disk usage).
Currently, we have to run dbstat command to see the available bytes for reuse and can't know its trend.

Accept cryptocurrency payments for billing purposes as Paypal or Cards are very unreliable. Recommended cryptos - Bitcoin (BTC), Ethereum (ETH), Bitcoin Cash (BCH), Dash.

Commerce between users and mongoDB platform will greatly improve by allowing payment mechanisms that have instant transactions at a much lower fees.

We are running into misleading error messages that learners are complaining about. This error appears when a user tries to use a $limit stage and forgets to add a $ while connected to a Free Tier Atlas cluster:
"OperationFailure: limit is not allowed in this atlas tier, full error: {'ok': 0, 'errmsg': 'limit is not allowed in this atlas tier', 'code': 8000, 'codeName': 'AtlasError'}":
This has been confusing for users. Is there a way that we can catch this issue more precisely and issue a syntax error instead?

When retrieving the billing details through the API, we are missing some information for a perfect understanding (and automation) :

• Number of nodes of the cluster. Indeed, without this information, the field "quantity" is kind of complicated to interpret


• Group Name. Each entry is attached to a groupId, but sometimes when the project has been deleted, it is impossible to retrieve its name, so pretty complicated to interpret (in the UI, the group name is available, so I guess it can be in the API)

As described in https://docs.atlas.mongodb.com/reference/faq/security/ and a recent email announcement, the root certificate is changing. Changing the cert used is available in the UI, but not in the provider.

It would be useful to add support for certificate selection.

It would be great to have the option to save Atlas backup snapshots without indexes. When using TTL indexes, when the data is restored, it is automatically removed because it is expired. Being able to create snapshots without indexes would save a lot of time to the current workaround.

on behalf of the customer,
would be great if we could allow tags on Org/ project level for cost allocation reasons (similar to how AWS allows this). When creating a project we can eg. add the type of environment, cost centre, bearer etc - without it showing up in the name. Does not necessarily need to show up on the invoice but we must be able to create a view which includes this info.

Currently, the profiler search is for namespace.collection_name. If I would like to see how all collections for a given namespace or DB are behaving it's a very tedious task and not user friendly at all.

You need to increase the notice period that you provide to your customers for changes that could affect their ability to connect to their database.

A good example of this was the upcoming change announced yesterday "Prepare for MongoDB Atlas TLS certificate root change starting May 1, 2021". You provided 3 days notice which is woefully inadequate.

I work with a lot of large financial institutions and have contractual obligations to provide them with 20 business days advance notice for any planned maintenance. This is simply not possible with the notice periods that you provide.