Skip to content

Atlas

← MongoDB Feedback Engine
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

How can we improve the platform?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

1390 results found

  1. Allow db.killOp() and manual restarts on secondaries

    Please allow us to kill user threads on Mongo secondaries. Sometimes we have long running queries on secondaries and need to kill those threads but can't do anything about it since we don't have admin privileges to kill threads.
    Also please add the ability to manually restart secondaries, not just failover the primary.

    Thanks.

    11 votes
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

  2. Allow option to configure default project_owner when creating projects through API key

    We're currently using the Atlas Service Broker (https://github.com/mongodb/atlas-osb) which is built using the native Atlas REST APIs.

    In the project creation, it creates the project using the POST /api/atlas/v1.0/groups endpoint via an API key. As a result, we have an unexpected user added as the project_owner of the project.

    THis is due to:
    IMPORTANT

    To create a project using API Key credentials, you must specify an orgId. When you do, Atlas automatically selects the Owner of the specified organization with the earliest account creation date and time as the Project Owner for the newly created project.

    The API…

    11 votes
    3 comments  ·  Admin →
    How important is this to you?

  3. Graph connections per user (or per database)

    Show a graph of connections per user.

    It would be very useful to see how many connections each user has (or also, each db) over time.

    It would allow us to see more clearly and faster which service uses how many connections.

    11 votes
    0 comments  ·  Monitoring and Metrics  ·  Admin →
    How important is this to you?

  4. Have the ability to downgrade

    Currently Atlas doesn't support the ability to downgrade major version. I know with Ops Manager on-prem you can do that, which is helpful if you find issues during an upgrade. Would it be possible to get the ability to downgrade one major version on the roadmap?

    As of today, if we have issues with an upgrade, we have to build a new cluster with the older version, export and import into the new cluster. That's a much more painful process including the fact that you have to change the connection strings of your applications to point to the new cluster…

    11 votes
    2 comments  ·  Other  ·  Admin →
    How important is this to you?

  5. Via API call invite existing atlas user & assigne them to project & teams

    in are organization we want user to have a self serve service that allow them to create project, cluster ,etc ...

    for now we can only automate half of the process, because we need the web UI to invite user & wait that they approve the invitation before assigning them to project.

    It would be great than we could, via API call, invite user & assign them to project or team without having to use manual process & wait for user to acknowledge the invitation

    thanks

    11 votes
    started  ·  0 comments  ·  IAM  ·  Admin →
    How important is this to you?

  6. Log browser and log search capability across replicaset nodes.

    Currently to search through logs we have to download them and search through each log. It would be helpful to have a log browser capability that would allow us to look through and search all logs from the Atlas portal interface.

    11 votes
    1 comment  ·  Other  ·  Admin →
    How important is this to you?

  7. Using Online Archive with Customer Encryption Keys

    I'd like to use Online Archive but I need to use Encryption Keys that my company manages, not ones provided by MongoDB.

    11 votes
    0 comments  ·  Online Archive  ·  Admin →
    How important is this to you?

  8. Profiler should only watch queries from certain users

    It would be useful to provide the profiler an "allowlist" and "denylist" of users to watch queries from. Essentially, it is only useful to receive alerts and profiler reports for queries made by actual applications. It is not useful to have alerts show up for one-off queries made by a DB admin using a DB explorer.

    11 votes
    2 comments  ·  Monitoring and Metrics  ·  Admin →
    How important is this to you?

  9. Being able to change the cluster name

    a cluster has been in development for awhile .. but as new cluster are created within the project.. we'd like to change the cluster name ..

    11 votes
    3 comments  ·  Other  ·  Admin →
    How important is this to you?

  10. Improve 2FA and auth management

    Right now, there is no way to require Google auth or to require 2FA. The only way to enforce 2FA for a team is to check the team mangagement page. However, since some users may have only used Google auth to login, they will show up in this view as not having 2FA, creating auditing headaches. Please
    - indicate if a user does not have 2fa because they do not have a password vs just not having 2fa
    - ideally, add the ability to require 2fa and/or Google auth for all team members

    11 votes
    6 comments  ·  IAM  ·  Admin →
    How important is this to you?

  11. Rename Hardware Metric "Util %"

    Under hardware metrics for a given replica set, there is a metric for "Util %". It is unclear on what this represents. After careful digging through the documentation, it appears to be a metric for Disk Bandwidth Utilization. I believe the metric name should be updated to reflect at least "Disk Util %", if not something more specific.

    11 votes
    0 comments  ·  Monitoring and Metrics  ·  Admin →
    How important is this to you?

  12. Show a graph of BANKED iops (AWS)

    Atlas monitoring is great... but it would be super helpful to see a graph of banked iops. (or an approximation of this)

    Suppose my iops limit is 100... and during the night my bank gets fully charged to 5.4MM.
    During the heavy loads on my server, let's say my iops jump to a steady 500. This means that I am drawing 400 units from my bank. I can do this for 3.75 hours until my bank is exhausted.

    It would be so helpful to see an iops bank balance drawing down during peak, recharging during off-peak... and thus getting insight…

    11 votes
    1 comment  ·  Monitoring and Metrics  ·  Admin →
    How important is this to you?

  13. Enable Terraform export of HCL for existing Atlas configurations

    Allow for a standardized export tool that outputs Terraform HCL from existing, manually provisioned Atlas resources (e.g., projects, clusters, users, role mappings, et cetera). This would be similar to GCP's Terraformer or Azure's Export for Terraform.

    10 votes
    0 comments  ·  Administration API  ·  Admin →
    How important is this to you?

  14. Allow customization of where $merge creates the temp collection used when rehydrating data from Online Archive --> Atlas

    When you restore data from the Online Archive back into your Atlas cluster (aka "rehydrate") you need to use $merge within an aggregation pipeline. What isn't documented is that $merge will create a temporary collection in the same database you're rehydrating to, which requires that you have readWrite@<dbName> privileges so that the new collection can be created.

    For customers that operate on the "principle of least privilege," where you only grant literally exactly what is needed to accomplish database CRUD operations, the user would the more narrowly scoped "readWrite@<dbName>.<collName>" privilege granted to the user to scope the actions to only…

    10 votes
    0 comments  ·  Online Archive  ·  Admin →
    How important is this to you?

  15. 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
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

  16. Serverless instances on AWS South American region

    It will be nice to have serverless instances on AWS South America. This model is great for this region and I strongly believe that it can have a lot of demand.

    10 votes
    4 comments  ·  Serverless Instances  ·  Admin →
    How important is this to you?

  17. change streams serverless

    Hi. I need the "change streams" feature implemented for serverless deployments.

    At this time it's unclear when will it be implemented, hence it's difficult to plan ahead.

    Why is that important?
    My nodejs app relies on change streams. Without it - the app simply cannot start because basic functionality is missing.

    Our devteam maintains a few complete vertical qa/testing stacks. Developers/QA/Product people load their change into these stacks and share with others. They are then used for product UI validation, sanity/automated testing etc.

    Because the app depends on change streams, those stacks are restricted to use only production Atlas clusters.

    …

    10 votes
    1 comment  ·  Serverless Instances  ·  Admin →
    How important is this to you?

  18. Implement AWS transit gateway support

    VPC peering and Private Endpoints have limitations that make them unusable in some environments. Implementing native transit gateway support would allow admins with hybrid infrastructures and strict security requirements to control routing and security at a lower level then is currently supported.

    VPC peers do not support pass through routing, so organizations that use transit gateways to attach IPSEC tunnels or other external networks to AWS are unable to access atlas servers via these peer connections.

    Private Endpoints do allow connectivity in these cases, but cause an additional layer of expense, complexity, and reduced security. First, the "user" side still…

    10 votes
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

  19. Support Slack in Third Party Integration

    Slack is supported via UI or API, but not via the Terraform Provider (v1.3.1).

    10 votes
    3 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  20. serverless

    Can we have a way to stop going over a certain amount RPU/WPUs, i know we can have alerts but we should be able to say dont go above a certain amount or somehow limit usage.

    10 votes
    1 comment  ·  Serverless Instances  ·  Admin →
    How important is this to you?
1 2 … 7 9 11 … 69 70
  • Don't see your idea?

Atlas

Categories

Feedback and Knowledge Base

(thinking…)