Atlas

Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Force restart of unhealthy node

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

    48 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make BI Connector Settings Permanent

    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?

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  3. Dark mode

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

    304 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    20 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  4. Restrict specific users or client IPs to only Analytics node(s)

    There are use-cases where certain users or client IPs need to be given access restricted to only the Analytics node(s) . While it is possible to grant such users read-only permissions at the database/collection level, and have them use the ANALYTICS replica set tag in their connection string URI, it might still be possible for those users to connect to a Primary or a Secondary node (when not using the Analytics replica set tag) and run their query there.

    Therefore, a feature that will either restrict specific users access to only the Analytics node(s) or a functionality that will restrict…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  5. Security Key (FIDO2) MFA option

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

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  6. MongoDB Atlas Provider for AWS CDK

    We use AWS CDK to deploy our infrastructure. Currently there is only a Terraform provider available to automate the MongoDB Atlas deployment. We would like to have such a provider also for AWS CDK.

    In a first step this provider should support:
    - mongodbatlascluster create, edit and delete clusters
    - mongodbatlas
    databaseUser create and remove users

    Later full feature set like in Terraform should be supported.

    Currently we use a self written provider. But this has hundreds of lines of code and means a lot of maintenance effort. For our teams this additional effort can be a reason to…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  7. Configurable number of insertion workers per collection for mongomirror

    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.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  8. create API keys that support linked orgs

    It is possible to link multiple orgs to each other. It should therefore be possible to use a single API key to access all linked orgs.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  9. Live Migrate Individual Namespaces

    Mongomirror allows you to migrate particular databases or collections using the --includeDB and --includeNamespace parameters:

    https://docs.atlas.mongodb.com/reference/mongomirror/#cmdoption-includedb
    https://docs.atlas.mongodb.com/reference/mongomirror/#cmdoption-includenamespace

    It would be helpful if Live Migrate allowed for use of these options as well to migrate subsets of data, instead of only migrating an entire cluster.

    40 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support Private Endpoint TO customer's VPC/VNet

    This would allow a Private Endpoint to connect FROM an Atlas Project TO a customer's VPC/Vnet (using AWS PrivateLink or Azure Private Link), for accessing private services like a private webhook for alerting, LDAP, and/or KMS

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  11. Create distinct indexes for Analytics nodes

    To effectively use Workload Isolation, it is desirable to have different indexes on the operational cluster nodes than the indexes used to support analytics and reporting query patterns. It would be powerful for Atlas to enable different indexes on Analytics nodes.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  12. geospatial

    Could we please consider boosting MongoDB's geospatial capabilities by incorporating Turf.js into Atlas. I would hope this would be an integration similar to Lucene in that it exposes some functionality through the UI, and some through aggregation. It would allow us to gain a huge amount of functionality. https://turfjs.org/

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  13. Increase the notice period for changes

    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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  14. Provide local ssd instances in GCP

    In terms of throughput it would be great to be able to configure an Atlas cluster based on local ssd / nvme GCP VM instances.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  15. OCSP stapling support for Atlas Clusters

    What is the problem that needs to be solved? As a user (MongoDB Driver) you'd like to check revocation status of X.509 certificate via TLS Certificate Status Request extension (also known as OCSP stapling) instead of doing outgoing HTTP connection to OCSP endpoint from a user (MongoDB Driver) side.

    Why is it a problem? (the pain) [MongoDB Server v. 4.4.X introduces OCSP stapling functionality](https://docs.mongodb.com/manual/release-notes/4.4/index.html#ocsp), however OCSP stapling is not enabled on Atlas Clusters with MongoDB Server v. 4.4.X.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  16. Atlas UI to manage and spin up on-prem clusters

    CSM submitting on behalf of customer

    Spinning up new clusters for on-prem deployments through the Atlas UI would save time and efforts for DBAs managing MongoDB deployments

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  17. Seeing ports that Clusters listen to

    In your documentation and even through the atlas web api, there is no straightforward method to see what ports my clusters communicate on. This is highly frustrating as I am using the Mongodb Atlas Private endpoint and need to Allow Inbound/Outbound communications on certain ports for the endpoint to work.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  18. Improve Cluster Name Limits

    Cluster names currently impose the following limits:


    • Cluster names shorter than 23 characters can't end with hyphen or dash (-)


    • Cluster names 23 characters or longer can't use a hyphen or dash (-) as its 23rd character.


    Instead, we should either trim or replace the hyphen at the end of a 23 character name.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  19. Provide an interface that can stream logs directly to Splunk.

    I'm trying to get logs from MongoDB Atlas to Splunk, and there's currently no native interface to do it, so instead of streaming to Splunk directly, I'm having to execute https calls in intervals, unzip them and then ship them to Splunk. Many products have interfaces to stream to Splunk directly, and it would certainly be handy in this situation.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  20. migration should check actual disk space used by source MongoDB

    The easy migration system seems to check the total disk space used on the source machine, and does not discriminate between that disk space used for MongoDB (which will be needed on Atlas) and those used for other applications.

    Because the source system contains a lot of logs and a complete copy of our databases in different folders, we have had to configure Atlas to use >2x the actual disk space it'll need.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 12 13
  • Don't see your idea?

Feedback and Knowledge Base