The Users view in the Access Manager really needs a way to either sort or filter by role, so I can see a single screen with just the users who are Owners, for example.

When performing a forensic analysis for the purposes of a restore, in order to determine the appropriate point in time when our data was last "sane", it would be awesome if we could start with a point-in-time restoration, and play the journal forward, e.g. performing a bisect on the data.

We have a lot of cursor not found errors and currently there isn't an easy way to locate them at the Atlas integrated monitoring.
It would be nice to have this feature.

Allow to create a backup when we want, on every type of cluster (like we could do with mLab plans)

Whenever the database is about to scale, give an alert via slack to the team.It will be instant and currently, alerts are over email if you could provide it over slack the tech team responsible for particular will be notified.

Integration Alerts with google chat like done with SLack

Getting onto Mongo and learning it the first step in getting to use it for projects and in production.

I am finding that there are many roadblocks to installing and connecting to Mongo.

Getting a standalone mode would make it super intuitive to connect with it and begin using it.

When inviting new Atlas Users to organizations via the API, the invite email says that the invite was sent by the API public key that performed the API call. This makes the invitation emails read like this:

"You have been invited by tfqzvwrs to join the Example - Atlas organization on MongoDB Atlas."

The ability to customize this (e.g. using an additional field in the request body) would be ideal since the random string being shown as the sender of the invite could make the email look suspect.

When receiving tens of emails regarding a dangerous condition on a node it would be helpful to know which node instead of having to click in the email to get to the portal to know if the issue affects our primary node or a secondary node.

Thanks

Right now I am running the MongoDB cluster on 3.6. Now I want to upgrade this cluster to 4.0. But when I want again to revert back to 3.6 I have no option to downgrade.

Use case :

Right now our production is running on 3.6, when we upgrade this to 4.0 and if we face any major issues on prod, then we have no option to get back to old version 3.6.

Without this option we cannot move our production to 4.0.

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 would like to provide users an access to database from our VPN to browse the data with some database tools - this access should be read only. As for now if somebody connected via VPN and uses production credentials he will be able to write to the database. To be able to configure it I think Atlas should provide a IP whitelist/blacklist during the user creation becaouse global Access Lists are not enough.

Since we want to automate the user (de)provisioning for organizations and projects, we would like to see the following API enhancements:

Please enhance the Mongo Atlas API for the following functionalities:
- invite (existing mongo) user to organization (currently not possible)
- remove user from organization
- get invitation status from user
- cancel invitation for user

Thank you

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

Hello,

We absolutely need a more modern authentication method than using LDAPS to authenticate users against the MongoDB databases that we deploy with Atlas. When will we see a modern authentication service at this level? Ideally, we want cloud functionality equivalent to AWS IAM but on Azure.

It would be great to have a feature that schedule live migration from a replica set of a PROD cluster to a DEV cluster directly in ATLAS.

The plus of this solution are :
- I dont need a dedicated server to do this job on my side (deploy it, configure it, script it, open network/port, etc ..)
- I will not have to dump the whole databases from the cloud then uploading it afterwards (can be long)
- Gain from outbound price in the cloud (more for you this one)

The speed at which usable monitoring metrics data (1m, 5m) is purged and reduced to 1hr is way too quick.

After 1hr, the ability to analyze these metrics that are crucial to investigating a performance issue were lost and hindered the root cause analysis.

I would suggest that 1m or at least 5m resolution metrics be retained for at least a week before being purged.

Hi,

It would be great to have support for yearly backup, including via terraform:
https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cloudprovidersnapshotbackuppolicy.

Thanks

Hi MongoDB Atlas Team,

Some of enterprise customers are left out with improper monitoring via Webhook to ServiceNow (an ITSM tool). Can you please improve on it so right set of fields can be included like "Priority", "Service", "Assignment Group" etc. other details which can be filled up via dropdown or entered manually so alerts to generate incidents via ServiceNow.

Regards,
Varun
Toyota Europe Database Team