Skip to content

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

471 results found

  1. Atlas dedicated tier is not actually dedicated

    MongoDB Atlas, despite the documentation and Atlas UI reflecting M10+ as dedicated tier, is not actually dedicating all resources. While CPU and Memory can be considered dedicated, storage is not dedicated until M300+. After working with MongoDB Support, and support working with AWS support, our performance issues were identified by a noisy neighbor who was choking our disk IOPS even though we are running M40_NVME clusters which are supposed to be high performance.

    MongoDB should at a minimum highlight this as a consideration for latency sensitive deployments.

    A new Atlas alert should be created to identify issues where slow query…

    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  ·  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. Unblock users in Russia and Belarus

    Currently MongoDB blocks access to MongoDB Atlas for users who are located on the territory of Russian Federation, Belarus (and other countries).

    MongoDB Support team confirmed this is the case and stated that the reason is US regulations and sanctions, referring only to the blog post published on their website (https://www.mongodb.com/blog/post/mongodb-assistance-ukraine-shut-down-work-russia). The blog post does not mention that the access to users is blocked.

    To our best understanding not many other tech companies have implemented such strict measures.

    We've also taken the time to delve into the sanctions topic and have reviewed every public release of sanctions on…

    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  ·  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. Altas CIDR ranges for network containers are too restrictive

    Background:
    For each MongoDB Altas project, the clusters built in that project are built using a "network container", which tells MongoDB Atlas which pool of IPs it can select from given a CIDR range for its underlying infrastructure.

    AWS minimum imposed CIDR value/subnet size: /28
    MongoDB minimum imposed CIDR value for clusters deployed to AWS: /24

    Azure minimum imposed CIDR value/subnet size: /29
    MongoDB minimum imposed CIDR value for clusters deployed to Azure: /21

    For customers who elect connecting to MongoDB Atlas via VPC peering, they know that IP space is a scarce resource. Reserving /24 or /21 IP space…

    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

    0 comments  ·  Other  ·  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. Authority Root/Intermediate Certificate from Let's Encrypt update

    Need to be notified when Authority Root/Intermediate Certificate from Let's Encrypt will be upgraded. It can be a alert/rss flow/notification/email to inform the customer company.
    From documentation https://www.mongodb.com/docs/atlas/reference/faq/security/#hard-coded-certificate-authority (Which certificate authority signs MongoDB Atlas TLS certificates?)

    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  ·  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. Control Over how to upgrade minor versions or rollback if required

    Hello Team,

    We recently faced an issue with the automatic minor version upgrade that rolled our clusters from 6.0.16 to 6.0.17 through Atlas. Since 6.0.17 has some problems, can we request the following features:

    1. Disable automatic upgrades of minor versions.

    2. Allow manual rollback to previous minor versions when necessary.

    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  ·  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. Mongodb Atlas Malaysia AWS regions

    Malaysia region is poised to be the largest AWS region and it is pertinent that Atlas can support it for south east asia. Writing in to petition of this region's support.

    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  ·  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. Support for Push-Based Logging to Azure and GCP

    Asking on behalf of customer, please add Support for Push-Based Logging to Azure and GCP instead of just to AWS S3 buckets: https://www.mongodb.com/docs/atlas/push-logs/

    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

    0 comments  ·  Other  ·  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. Ability to schedule "Hedged read" Turn on/off

    Customer experienced read latency during maintenance after sharding.
    Our guidance is to turn on "Hedged read" option.
    So the customer need to turn on/off "Hedged read" before/after maintenance, because turning on "hedged read" increase CPU usage that means server cost increasing.

    Currently "hedged read" on/off can be done by technical support from MongoDB but this feature is needed for operational efficiency and reducing human error.

    8 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  ·  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. The oplog configuration is a bit confusing

    The oplog configuration is a bit confusing. I think it's not clear that if we set the oplog window, we don't need to set the maximum oplog size. I believe this configuration should be more specific.

    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  ·  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. cloud.mongodb.com,Since this week, it often cannot be opened

    cloud.mongodb.com,Since this week, it often cannot be opened

    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  ·  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. Atlas - Queue cluster pause request to perform it when it's possible

    It is impossible to pause a cluster that was recently resume.

    The documentation indicates it is a voluntary feature (https://www.mongodb.com/developer/products/atlas/pause-resume-atlas-clusters/) to allow the Atlas service to apply any pending changes or fixes to the cluster that may have accumulated while it was paused.

    I agree with this, but it cause a problem for automation (for example sometimes we launch a platform exclusively for testing purpose and then shut it down, it is complicated to add a delay for pausing the Atlas cluster) and even manually for example at the end of the day of work this requires either…

    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

    0 comments  ·  Other  ·  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. All Clusters permission for ORG level roles

    Today, for you to be able to use All Clusters you need to have permissions on each project, your user needs to be included in each project.

    When we use a federation, we generally don't grant permission for each project to a team of administrators. We grant ORGOWNER, for example. By doing this, we lose access to All Clusters. The idea was to include the permission to use All Clusters for project-level permissions that have permissions to read project resources, for example ORGOWNER or ORGREADONLY.

    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  ·  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. Migrate users and roles with between Atlas Projects

    It would be great to be able to transfer/copy users with their credentials and permissions from one Project to another.

    In a longer time, from one Org to another.

    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  ·  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. Live Migration with granular permissions

    Today, to carry out migrations you need to be the Project Owner of the project, however we have very restricted permissions regarding Mongo projects so that people can use the company's stack, which would be via terraform. The dba's have readonly permissions on the projects so as not to modify items in the projects using the console.
    The idea is to create an intermediate permission so that dba's can carry out cluster migrations without necessarily needing to have a project owner. Is there a way to do this without breaking permissions, is it possible to request this feature?

    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  ·  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. Ability to create granular auditing

    I want to be able to create granular auditing for a specific cluster inside a project. Right now, the audit is applied to every cluster inside a project. Some clusters need more auditing than others, and their performance should be affected by other cluster configuration.

    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  ·  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. IP address, Mongo Network Issue

    Why is it that we always have to provide our ip address in the Netwoek Access section and that's not even the issue the fact that we have to add 3,4 ip addresses everytime we open atlas is the main issue. Every time I login I delete ip's adn add them again or logout and add them again it's a repeating process until I get my connection going please resolve this issue now it's going on for a while.

    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  ·  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. Allow custom GCP VPC peering CIDR allocation

    With GCP VPC peering, Atlas is assigned a large CIDR block which is then further subdivided as GCP resources are deployed across different regions. At this time that allocation is not visible to users, and cannot be directed or known before resources are deployed.

    This makes it near impossible to apply any firewall rules, and requires you to allow the entire CIDR block instead of limiting it on a per region basis. We would like to be able to determine the subnet that is assigned to a region before resources are deployed, and to be able to see the CIDR…

    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  ·  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. Better streamlined logs in GCP

    Running Application and MongoDB in the same public cloud provider. Want to have logs in one place so that in case of any issues, I can debug any production issues properly. For example, in our Development or local environment, we have everything running on Docker Desktop and MongoDB on local Windows laptop. Using Docker tilt - Dev team can see UI, Service tier and backend(MongoDB) logs one after the other in one place. If the request is timing out, we can see that it's a collection scan that is happening not index scan so we need to either create the…

    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  ·  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. Add usability to tags

    Atlas has the option to set tags to clusters. But - now what? They are just pieces of text floating around, but are completely useless.
    How about enabling to filter clusters in a project or even organization based on those tags? Split costs based on them? Query them with API calls? I have no use of those tags when they are just texts in the main page of Atlas...

    7 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  ·  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. SimplifiedJson format

    Kafka source connector has an output format option of SimplifiedJson which is easier to parse by the downstream applications. Mongo utilities or any of the Atlas features do not support this as an output format as of now.

    Mongo does have canonical format output for mongo export which can be matched with kafka extended json format but it requires additional translation by the 3rd party applications.

    Is there a feature in place already to have atlas $out or mongo export or dump utilities to output data in Simplified json format? If not can this be looked into?

    9 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 23 24
  • Don't see your idea?

Feedback and Knowledge Base