Achieve feature parity with AWS IAM cluster authentication support.

We would like the option to have our Atlas backups automatically copied to a 2nd region to support our DR initiative. I realize we could create a live database node in a 2nd region, but that is more costly and complex. Having the backup sync to another region that we can restore off of in case the primary region fails would be simpler and more cost effective.

Is this something that is on your roadmap, and if so, when will it be released?

Thanks!

Currently a project is created with a set of default alerts. We need to customize these but we can only add new alerts via terraform. It would be helpful if there was a boolean flag in the mongodbatlas_project resource to disable default alert creation

Right now, there's a "test failover" option, which shuts down the primary and forces an election. However, the option is only available if the cluster is in a healthy state.

If, for whatever reason, the cluster is unhealthy, it's impossible to manually restart the primary. It should be possible to force an election in an unhealthy state. Often, this is all that is required to get back into a healthy state (e.g. if the primary is in a CPU burning loop that was caused by an unexpected write pattern that has stopped.)

Allow the "SET GLOBAL mongodbmaxvarcharlength = n" to be permanent after a Mongosqld restart. Currently, the setting is ephmeral and must be set everytime the mongosqld daemon is restarted. Currently, our production environment mongosqld can restart without our knowledge at anytime. This results in the mongodbmaxvarharlength variable being reset to zero, which can lead to a production outage. Is there anyway this can be automated, maybe through database trigger?

Please release a dark mode MongoDB Atlas interface. Thank you.

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.

Similar to how AWS includes tags/labels in their billing dashboard, I'd like the ability for my cluster labels to be included as a column in my billing usage details (or even the exported CSV).

This will allow me to categorize my billing usage as granular as clusters in addition to the current method which is by project.

In Atlas, it would be ideal if you could specify a percentage of total memory as the threshold for the "System Memory: Available Is..." rather than a literal number value. If it was possible to set this as a percentage, then the alert could be applied to all hosts in a project, rather than having to set hostname conditions and create a separate alert for each cluster.

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)

Currently there is only a community supported Prometheus integration (exporter) available which polls db.serverStatus() and doesn't include as much metrics as the Atlas UI/API provides. A similar integration as with New Relic and Datadog would help many customers that are using Prometheus and Grafana for monitoring.

Please enable security key (e.g. https://www.yubico.com/gb/product/yubikey-5c-nfc/) option for MFA. Ideally using FIDO2 protocol

To help catch heavy disk workloads before they become problematic, it would be great to have alerts on:
- disk IOPS percentage utilization for disks without burstable IOPS
- burst credit utilization for disks with burstable IOPS
- CPU IOWAIT %

This is a request to support an integration with Dynatrace for monitoring MongoDB deployments in Atlas.

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.