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. MongoDB Orphaned Docs Utility

    When we upgrade MongoDB there is the possibility that orphaned collections that need to be deleted can prevent the upgrade from completing.

    It would make sense for Atlas to include a proactive utility that searched a customers sharded cluster for orphaned docs and gave them the option to clean up the orphaned docs ahead of a major version upgrade.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. IO throttling

    Atlas should be able to throttle IO in a way that does not allow excessive IO to degrade a node or take a node offline. Current functionality has no defense against a high IO data job other than to allow a node to fail.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Governance rules at the organization level

    Hello team,

    Would it be possible to be able to set up governance rules at the organization level in order to control certain configuration elements.

    For example:
    Control authorized providers and regions for an organization to prevent creation of cluster in unauthorized regions. (We must keep the data in Canada for some of our databases)

    Check the allowed IP (IP Access List) addresses

    Disable the use of SCRAMS accounts for database access.

    Control the "Data Explorer" functionality at the organization level to prevent its activation at the project level.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Redirection of ATLAS activity feed to a MongoDB cluster that we own.

    Hello team,

    Would it be possible to have a feature to redirect activity logs from ATLAS to a MongoDB cluster.

    The idea is to be able to easily retrieve these logs with Kafka Connect and also to be able to easily query in these logs.

    One could configure the redirection of activities at the organization and projects level by providing the Atlas cluster to use and the access accounts.

    Example:
    Main organization
    - Project: "Activity Feed"
    - - Cluster: "Activity Feed Cluster"
    - - DB: "Atlas Activities by organization"
    - - - Collection: "Activities by project"

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Setup activity feed retention

    It could be very interresting to be able to setup the retention of the events by organisation, projets and clusters. Actually I understand that this value is 30 days. So it to short for us, so we need to download the activities logs and it difficult to seach in files after that.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. major version downgrade request (4.0 to 3.6)

    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.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Provide an option to block access for certain username and source IP

    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.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Billing Estimator

    The ability to estimate monthly price not just at the cluster, but also by editable storage, data transfer, cloud backup with sliders to change the values.

    Estimated forecast based upon last 3 months of usage/growth would be great too.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Merge All Of the MongoDB services Into 1

    I have multiple feedbacks/ideas:

    1) There is MongoDB Atlas, Realm, & Stitch. Why don't you merge all of it into one - MongoDB Atlas.

    2) Instead of creating Organizations -> Project -> Clusters, you can just create Organizations -> Clusters without the Project.

    There are a lot of platforms, which is very confusing for all of the developers to use. Instead, there can be only one platform in which, they can perform everything with simple integration of the programming languages.

    You could simplify your docs as well and like I said, have only one type of integration with all of…

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Add Cluster name to process list api

    Currently the processes API (https://docs.atlas.mongodb.com/reference/api/processes-get-all/) returns only the ReplicaSet name of the process not the cluster name, while the cluster API (https://docs.atlas.mongodb.com/reference/api/clusters-get-all/) returns the replicaset name only in the MongoDB URI.

    If you have multiple clusters in the same Atlas project and you list the processes is difficult to make an association between MongoDB processes and the Cluster (Atlas UI name)

    Would be nice to have also the cluster name in the processes api

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Dynamically switch primary between multi-region clusters based on client request locality

    Consider an application that uses a multi-region implementation in an active/passive configuration - we'll call the regions "A" and "B" and assume they're located on opposite ends of the continental US. This application also leverages a multi-region Atlas cluster with single nodes in region A and B. Both the application and Primary node of the Atlas cluster are operating out of region A.
    If something were to cause the application to fail-over from region A to B but that trigger did not include a complete regional outage, the Atlas cluster's primary would still be operating in region A. This is…

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Merge All Of It Into One

    There is MongoDB Atlas, Realm, & Stitch. Why don't you merge all of it into one - MongoDB Atlas.

    There are a lot of platforms, which is very confusing for all of the developers to use. Instead, there can be only one platform in which, they can perform everything with simple integration of the programming languages.

    You could simplify your docs as well and like I said, have only one type of integration with all of the programming languages.

    If you implement my idea, it will become very easy for developing and you can get more customers. Why should everything…

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Cluster/Database changes from Atlas portal does not show correct user in DB Audit log

    We have enabled Database audit for some projects, because we need to track who have done specific changes , like dropping an index.
    When someone using Atlas portal, the logged-in user does not show up in Audit record.
    Is not that possible to track ?
    Will attached some files..

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. apply Data mirroring technology

    once data create when we add to it , it will mirror whole data set as another database(e.g: when we create User as a DB and some Collections, it will store, mean while MongoDB store another replica of the same DB )
    Functions for the Replica DB when user API's call
    When user call the API's for any post get delete update, The replica DB allows only post(Store) request from the user it wont allow other functions like delete update
    and Owners can have all rights to that DB.
    All functionalities works only on original DB not in replica DB

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. M0 in eu-west-2 with API (terraform)

    I really love mongo. Not having M0 in eu-west-2 and terraform is a huge limitation. It prevents me making the business case for mongodb as our backend of choice, and we end up using AWS DocumentDB. Mongo is preferable for consistent hybrid cloud deployments.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Single node clusters

    Allow users to create a single node clusters for dev purposes.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Project migration should not require org-owner rights

    Before project migration from one org into another, we have been told to define the responsible users in both orgs with org-owner rights. There should be no need at all to permit org-owner rights on project migration. The org-owner-level should only be reserved to the very smallest group of people (admins) necessary. Project owner level should be enough for a migration of projects.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Add a grace period between a failure to obtain a certificate and the cluster shutting down.

    If you set up encryption at rest on Atlas using an external key provider, such as an Azure Key Vault, then a link is created between being able to access the key vault and the status of the MongoDb cluster.

    For example, on the 28th September, there was an issue at Azure (SM79-F88) and for over 2hrs around 19% of all authentication processes in Europe failed. This included accessing the KeyVault used by our MongoDb cluster. As Atlas checks the keys roughly every 15 minutes it failed to obtain the key at the beginning of this period and our cluster…

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Love The New Look

    Just wanted to say I love the new look!

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base