Create TTL index based on local timezone as opposed to UTC time

update the course videos the setting up video is completely different from the current atlas environment

For DR strategy, one need to have its backups outside Atlas.
This can be achieved in several ways. Some are:
- Provide APIs to download the current backups and let the customers automate this on their side
- Write backups in the customer provided cloud account (aws s3, azure blob stroage...) My favorite option

I found many ideas related to my needs, but they were too specific. This need is more general: just provide a way to have backups automatically outside of atlas.

As this is one of the most common request from Atlas customers to modify transactionLifetimeLimitSeconds it would be beneficial to grant the privilege so the Atlas customers are able change this parameter within a certain limit. Please add this functionality.

Allow API keys to have much more granular permissions (i.e: only the functions one may need to do a certain task).

Also, add a security category in the form to report possible improvements for Atlas.
And a UI/UX one.

I'd like to setup an alert on my cluster for specific database but currently I can only setup alerts for all databases on my cluster. for example, send alerts when "Document Metrics: Deleted above 1" on zyz database

Hello,

this is a request to support Private Service Access for Atlas deployments on GCP. Today, our options with Atlas are IP access lists or VPC Peering. However, these options create downstream limitations for our organizations. Additionally, only one peering connection can be made per Atlas project, which also limits us.

Thanks

Add an alert category for cluster scale events such as creation, modification and deletion

There should be an option to stop once the restoration is given. Or there should be an option to revert a backup restore. This is required because we can restore an old production back up to Production only. If by mistake we do that we should be able to revert back.

I would like to have the ability to generate an Excel file for clusters in the Organization.
https://cloud.mongodb.com/v2#/clusters

Like we can do in Cloud Manager Continuous Backup, We can query a snapshot. This download an .EXE file that will create a tunnel directly to the Backup Storage and allow us to retreive the document that we need (using localhost:27017), without restoring the whole backup, or having a 2nd database, giving access to the developer, ...

For managing Database Users, it would be nice to see when that user was last used to authenticate with the cluster - so that we can spot potentially unused accounts and to act as an extra layer of confirmation when deleting accounts that we think are not needed anymore.

There should be a capability to manage/assign contact details (such as email) at the Atlas level, to the created organizational 'Teams' (such as assigning a team distro email address), so that alerting can be streamlined, instead of sending out separate emails to each and every member of the team.

I would like to develop in new Global writes cluster for an existing data base model create easily and fast the "location" key in all documents from collections that Global writes requires.

on the laptop screen, we have't much space for querying the data filter portion. If we have an option to collapse the left side menu, it may get more working space.

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.