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

1362 results found

  1. 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)
  2. Uniform approach to Dedicated and Tenant clusters in terraform mongodbatlas_advanced_cluster

    Our software development lifecycle has 5 environments. We also wish to spin up dedicated, short lived environments for individual Developers. As a result, we'd like to have two M40s, an M10 and two M5s for our SDLC and the ability to spin up M0s for the devs.

    The way you've implemented the terraform mongodbadvancedcluster resource makes it exceptionally difficult to use the same code across all environments. This isn't in keeping with best practice for terraform implementations, which is to use the same code and only change the variables. Might I suggest you add providertype and allow

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Handle Duplicate data in Timeseries collection

    It would be helpful by introducing the optional add on functionality of overwriting the document if it is already exists for an insert operation based on “_id” field for only timeseries collection in upcoming releases. Because if we have huge amount of sensors then data should be blindly written into timeseries collection without querying for duplicate check (Conditional inserts will definitely impact the performance).

    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  ·  Data API  ·  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. Set "Cluster Termination" ON as default for an Atlas organisation

    Have a button in the Atlas Org setting to toggle ON/OFF Custer Termination protection.

    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)
  5. Disable duplicate linked Organization names

    Currently, one can create multiple linked sub-organizations under a main billing organization, but having the exact same names. The below API command, run repeatedly, will create the same sub-org name with different orgId's. I believe this only serves to confuse administrators and makes management more difficult -- therefore, I'd rather have the API fail with "HTTP 4xx: Another organization already exists with the same name."

    curl -s -X POST --digest -u "$ATLASPUBLICKEY:$ATLASPRIVATEKEY" \
    --header "Content-Type: application/json" \
    --data '{ "name": "MYORG", "orgOwnerId": "MYORGOWNERID" }' "https://cloud.mongodb.com/api/atlas/v1.0/orgs" \
    | jq -r .organization.name

    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  ·  Billing  ·  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. mTLS for Atlas Alert Webhook Integration

    Atlas currently does not support mTLS on HTTPS traffic to Alert webhooks. Some customers whose alerting services are on-premises may require this per their security policy. We should support mTLS on webhook integrations to enable those customers to use their on-premises alerting systems.

    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  ·  Alerts  ·  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. Approval workflow for database deletion

    The current Termination Protection only prevents accidental deletion of a cluster. It helps to have a similar protection to databases inside the cluster.

    Even better if there is an approval workflow, in which several people must accept before a database/cluster is deleted.

    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. Add a button to retry to collect a payment on the billing - invoices tab

    Add a button to retry to collect the payment from a credit card on user request. This will help when there are problems with the credit card funds or credit limit.

    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  ·  Billing  ·  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. Create Atlas App Services and Link Them To Clusters with Terraform

    It would be great to create App Services (Realm Apps) and then create the service link to an Atlas Cluster with Terraform.

    This is so that Trigger resources can be created fully within Terraform, rather than having to hack together API calls, CLI commands or manual steps.

    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

    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 Teams to a Project

    Allow to add a team to a project and set roles.
    Split the creation of the project and the role assignment.
    Based on the API: https://www.mongodb.com/docs/atlas/reference/api/project-add-team/

    18 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Improved Metrics | Memory usage by collection

    The Profiler is a great tool, but it does have limitations. The metrics there don't really tell us what's driving I/O. For example, we might have these two queries:

    1. a query that scans 10000 documents that active users trigger, but the queried documents are the same for all users
    2. a query that scans 100 documents that active users trigger, but the queried documents are different for all users

    If you have 1000s or more active users, the working set (memory usage & i/o) is being driven by the second query. And, it probably performs better than the first query in…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Restored snapshots from a dedicated instance to a serverless instance

    I'd like to be able to spin up serverless instances for automatically provisioned dev/QA environments. I'd like to have production data available in them. So I'd like to restore a dedicated instance snapshot to a serverless instance.

    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

    2 comments  ·  Backup  ·  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. Kindly see how you can accomodate Dedicated Pricing for countries especially in Africa where dollar rates are very high

    Minimize pricing for Dedicate service the hourly rate multiply by 3 server node is high especially for startups in Africa

    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  ·  Billing  ·  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. MongoDB Connection Pool Proxy

    Currently there is no Connection Pool proxy supported by MongoDB.

    With the ever increasing use of serverless and containers, clusters will need to be over provisioned in order to account for the increased connection counts.

    A better solution would be a Connection Pool proxy allowing for a many-to-one relation for connections to MongoDB.

    In the case of Lambda, this would reduce the number of Zombie connections (Connections that have been terminated on the Lambda side but are still open on the server side.)

    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

    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)
  15. grpc

    You should create a grpc API like AstraDB has already done. Grpc is the ideal way for a serverless app to connect to a database. Get both of best worlds: native driver performance plus don't need to worry about database connections.

    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  ·  Data API  ·  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. U domain Verification

    If you are able to verify the parent domain for your company, then you shouldn't need to have to verify the sub-domains associated with that domain. Company's do not generally advertise their internal u-domains on the internet therefore any verification on that sub-domain will naturally fail. This is hindering us from integrating our Okta credentials with our login information.

    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  ·  IAM  ·  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. Alert - Network & Security

    Ability to setup alerts on the project to notify if any user added network ranges / IP's to access the database cluster.

    You can see the activity in the feed but there is no options available to set alert for such?

    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

    1 comment  ·  Alerts  ·  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. Improve the sample code for Connecting with MongoDB Driver

    When in Atlas you click the Connect button and get to the screen 'Connecting with MongoDB Driver', the Java sample isn't using the MongoClientSettings.builder() to set writeConcern and retryWrites. This is done in the connect string instead, even though the builder does provide those two settings.
    I suggest only using the MongoClientSettings.builder() for better type safety.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Terraform support for Database Triggers using Function events

    The Database Triggers resource supports only EventBridge right now. It would be awesome to see support for Function events as well

    19 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    planned  ·  Zuhair responded

    Hi we working to enhance the the use of Triggers and Functions in Terraform, but this effort still several quarters away. Feel free to reach on in the interim in case of any questions and happy to help. 

  20. Restrict whitelist ip

    I would like there to be an option to restrict users to what they can whitelist in network settings for a project. I want there to be option like "only users with owner access can create non-temporary IP whitelistings" so we can avoid having our developers adding IP addresses that gets outdated and pose a potential security risk.

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

Feedback and Knowledge Base