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

483 results found

  1. 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)
  2. 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)
  3. 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)
  4. 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)
  5. 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)
  6. 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)
  7. 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 not 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)
  8. 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)
  9. 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)
  10. 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)
  11. 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)
  12. 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)
  13. Display a cluster tier size (e.g. M20) on the all Clusters page

    I am opening this new feature request on behalf of the customer. Would it be possible to display a cluster size (e.g. M20) on the main status page alongside other cluster information that's already on the page?

    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

    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. Atlas Console option to start the resynchronization of a primary node

    It would be great if during an automatic maintenance process, considering the restart of all nodes you were able to find a button in the Atlas Console to start the restart of the primary node, so that way you can select this process in a less operative window and avoid a severe business impact in your organization.

    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. 15 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  ·  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. Within Atlas, create service to allow project owners to schedule shutdown/start up times of cluster to reduce hosting costs

    Request to provide an enhancement to the Atlas service to allow project owners to schedule shutdown/start up times of clusters(or databases) and provide some notification of a successful shutdown and startup. This should be a feature with the Atlas UI and API.

    This will allow teams that have non-critical environments to effectively "turn off" and freeze the state of a cluster in order to reduce hosting cost during off hours. This can provide a better value proposition for existing customers and a selling point for new customers, without having to introduce a third party tool that requires additional configuration and/or…

    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)
  17. Push Logs to AWS S3 bucket: IAM role Max_Session expect 12hours

    With respect to the feature "Push Logs to AWS S3 bucket " Atlas expect max-session-duration for IAM cross account role is : 43200 (12HRS) by default.
    Some organizations like us have limitations on max-session. We reached out MongoDB Support, They said " The Atlas team has confirmed that currently, we do not support max session durations of less than 12 hours. However, there is an internal ticket for improvement, where session duration can be internally configurable via MongoDB's internal support UI. Case ref: 01276442

    This will provide a flexibility for the organizations to have max-session configured according to their internal…

    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)
  18. UI/UX: make site scaling for large screens

    UI/UX: make site scaling for large screens, now text fonts are too small

    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. Atlas DNS name more than 23 characters from the cluster name.

    Allow users to have longer DNS name from the cluster name. Currently, Atlas cuts the first 23 characters from the cluster name and the users can't check the cluster name inside the mongo shell.

    Example:

    Cluster name longer than 23 characters : xxxx-us-east-1-multi-use-1
    DNS name : xxxx-us-east-1-multi-us.xsj8t.mongodb.net

    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  ·  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. Allow multiple VPC CIDR ranges in Peering connection

    Allow multiple VPC CIDR for a single Peering connection from Atlas to AWS.

    Our AWS account has two CIDR ranges for a single VPC. Atlas peering connection only allows connection to a single CIDR range.
    Today, I need to create a separate private link connection to be able to connect to the second CIDR range.

    31 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

    6 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)
  • Don't see your idea?

Feedback and Knowledge Base