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. Set MongoDB Production Support Employee Access to Atlas Backend Infrastructure at Project Level

    The Restrict MongoDB Production Support Employee Access to Atlas Backend Infrastructure is currently set on the organizational level. This should also be possible at the project level. Secondly, add the possibility to grant access indefinitely until revoked.

    12 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. Feature Request: DNS record per zone for global cluster

    Today Atlas creates a single DNS record for the global cluster which has SRV records pointing to all servers in the cluster across all zones.

    This causes issues when a service hosted in US tries to use this DNS record as it now connects to every server in the SRV list of the DNS record. We ideally would want the US service to connect to its closest mongos router (US zone) and not all the mongos routers as it is unnecessary waste of resources. Our workaround today is to manually pick the servers and build the connection string in old…

    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

    2 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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?

    25 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 →
  4. Provide "Last Login Date" for Atlas users via Atlas API

    The Atlas API should include "Last Login Date" for the GET /orgs/{ORG-ID}/users endpoint.

    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

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  5. Dark mode

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

    461 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

    43 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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.)

    64 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 →
  7. Add Duo in the MFA provider

    Is it possible to add Duo in the MFA option list ?

    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

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  8. Improve handling of ROLLBACK state

    Recently we had a member of a replica set in a sharded cluster enter ROLLBACK state. We just happened to notice it in an automated email sent by Atlas about primary elections which showed one of the members in ROLLBACK state.

    Fortunately for us the writes which had been reverted were not critical and we were fine with that. However, this could have resulted in serious data loss which could have gone unnoticed until a customer reached out to us.

    The handling of a situation like this one should have been much better and more user friendly. We should have…

    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 →
  9. More granular permissions *for API keys*

    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.

    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 →
  10. killop

    I have read the other two suggestions on providing more killOp() and read Andrew's comment on the difficulties in the medium term.

    I just watched a situation where a primary became unresponsive and the queues piled up. The solution was to cause an election, but the dba wanted to kill operations by user (the application user) and couldn't.

    It would be nice to have something more than the real-time panel, which in this situation had become unresponsive as well so it was no use, such as a DBA console where an authorized dba could kill operations started by other users.

    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

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  11. Migrate to new cluster without auto upgrade (5.1.0)

    Hi,
    Our clusters are in auto upgraded feature of MongoDB versions right now.

    We want to stop the auto upgrade feature for now and migrate our clusters to new one with the MongoDB version 5.1.0.

    But, when we try to create a new cluster it's not showing the option for version 5.1.0.
    And we need 5.1.0, because we're going to restore the data from the current cluster which is versioned 5.1.0.

    Your help is much appreciated.

    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

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  12. Derisk cluster changes that cause restarts

    Problem statement:
    Some configuration changes cause rolling restarts of the cluster (e.g. audit filter, enabling x509 auth). It is not immediately obvious which changes will cause restarts and for a big cluster, this is a huge hit to performance due to cold caches.

    Ideas:
    1. Block planner changes which would cause restarts until maintenance window (maybe with an opt-in for this, + notification that the config change is blocked)
    2. Throttle replica set restarts, allowing time for the cache to be warmed on secondaries (would require mirrored reads in 4.4 to be effective)
    3. Properly document what changes will cause…

    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 →
  13. Improve OKTA Location Detection

    Hi,

    This is really a message for your security / authentication engineers.

    When you use Okta PUSH MFA, the popup on my mobile device reads "Did you just try to sign in? near Ashburn, Virginia, United States"

    I am not near Ashburn, that's your server location. We use Okta Push at our company and had the same issue. It's a simple fix, tell your engineers to add:

    'X-Forwarded-For': <users ip>,
    

    With the user IP address that is sent to Okta, and it should geolocate properly. This is a small, albeit actual security issue with MongoDB, as I cannot safely differentiate…

    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

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add Atlas users to existing teams even though the Atlas user is still pending invite

    Currently when we send invite emails for the organization we have to wait for the users to accept the invite before we are able to configure project level permissions. This often creates confusion and bad user experience; when users first sign in they are anticipating to see their projects but instead they see nothing until configuration is finalized.

    Please make it possible to add users to teams which are still pending invite acceptance so the user experience is more seamless and less confusing.

    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 →
  16. Document Atlas Cluster Tier Performance Expectations

    Document approximate Atlas cluster tier performance expectations that application development teams could reference when requesting an Atlas cluster (IOPS, max connections, network performance).

    This information is currently available in the Atlas UI.

    Other cloud providers such as CloudAMQP do this: https://www.cloudamqp.com/plans.html.

    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. Folders/Directories For Functions, Triggers, Etc

    Allow users to create directories and subdirectories for staying organized when creating many Realm triggers and functions.

    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

    2 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  18. Deletion Protection

    Customer suggested protection from Cluster deletion similar to AWS RDS

    https://www.amazonaws.cn/en/new/2018/amazon-rds-now-provides-database-deletion-protection/

    TL;DR - a notification when a user tries to delete a cluster, that "this cluster is protected, if you need to delete please visit the console to enable deletion"

    This would be a critical piece of functionality where roles/permissions are not sufficient.

    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

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  19. Atlas should allow deployments of non-voting members on region for tiebreaking purposes

    No allowing non-voting members criples the ability to combine regional failover, while keeping the application servers in just two regions, where the event of having a third region primary may imply high latencies, that impacts SLOs.

    This particular severe for architectures that rely on 2 main datacenters (regions) and use a 3rd for tiebreaking purposes only.

    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

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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.

    23 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 →
← Previous 1 3 4 5 16 17
  • Don't see your idea?

Feedback and Knowledge Base