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

145 results found

  1. Make it possible to add tags in the Datadog integration so I can tell my staging and production environments apart more easily

    Datadog recommends having only one account and feed data from all environments into it, and then it’s important to tell them apart by using tags.

    Please add the ability to set tags in the Datadog integration configuration, e.g. env:production

    24 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

    completed  ·  7 comments  ·  Other  ·  Admin →
  2. Allow creation of Atlas organizations in Terraform

    there are really 3 steps for our dev teams to get moving in Atlas:
    1. create an org
    2. create a project
    3. create a cluster
    the first one is the only one that still has to be done from a console. if we had a terraform script to create an org in our account, we could trigger creation after approval in ServiceNow

    23 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

  3. Third party integration resource with terraform

    Add a terraform resource for third party integrations (such as PagerDuty) to allow it to be set up.

    22 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

  4. Add 1 second granularity to ATLAS metrics

    At present the finest granularity of ATLAS metrics is 1 minute ,as the metrics are averaged by 1 minute , this would not provide info on spikes lasting less than few seconds
    reducing the granularity to 1 second would give more insight

    21 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

  5. Allow Pending Users to be Added to a Team

    When trying to implement Atlas infrastructure for Organization/Project users, the Teams functionality is useless unless we can add pending users to a Team. Right now, if a new user doesn't login for two weeks, we can't assign them to a Team until two weeks after the implementation was supposed to be configured.

    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

    completed  ·  2 comments  ·  IAM  ·  Admin →
  6. Add option to create project without alerts

    Currently a project is created with a set of default alerts. We need to customize these but we can only add new alerts via terraform. It would be helpful if there was a boolean flag in the mongodbatlas_project resource to disable default alert creation

    17 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

  7. AWS EBS gp3 Volumes

    Please add support for the newly announced and already generally available AWS EBS feature. [1]

    The top capability is: "The new gp3 volumes deliver a baseline performance of 3,000 IOPS and 125 MB/s at any volume size. Customers looking for higher performance can scale up to 16,000 IOPS and 1,000 MB/s for an additional fee." [2]

    That basically means decoupling storage performance from storage size.
    It would eliminate all our IOPS pain as 3000k is more than enough for our usecase. Currently, we are slightly overprovisioning storage size in order to guarantee minimal IOPS performance.

    [1] https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ebs-general-purpose-volumes-gp3/
    [2] https://aws.amazon.com/ebs/general-purpose/

    17 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

    completed  ·  4 comments  ·  Other  ·  Admin →
  8. hide index

    Add a button/toggle to Hide and Unhide an Index from the Data Explorer/Indexes display for a 4.4+ deployment.

    16 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

    completed  ·  1 comment  ·  Data Explorer  ·  Admin →
  9. Programatically disable/enable Auto indexing Serverless

    We have Serverless instances. We want to be able to programmatically (using atlas api and terraform resource) disable/enable
    mongo atlas to auto create suggested indexes for given mongo Serverless instance. Currently, it is enabled by default and can be disabled only by toggle in Mongo UI.

    With programmatically way we can easily disable/enable auto indexing on all our Serverless instances.

    This is important to us because we want to use only indexes that we create.

    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

  10. Terraform feature request: Cluster Termination Protection

    Termination Protection has been added. Would be great to add support for it in the terraform provider, so clusters can be provisioned and configured entirely via terraform.

    Without this support, we need to perform some configuration manually in the UI.

    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

  11. A metric of availability of a cluster mongodb atlas for building my SLO

    Hello
    As other databases provider , their databases services (like postgresql ....) give metrics on availability of a the service (ex: postgres.canconnect) . I would like to have some metrics on the availibity of a cluster mongodb atlas for building my SLO:
    ex: mongodb.can
    connect

    Thanks,

    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

  12. Authentification on Azure (IAM)

    Hello,

    We absolutely need a more modern authentication method than using LDAPS to authenticate users against the MongoDB databases that we deploy with Atlas. When will we see a modern authentication service at this level? Ideally, we want cloud functionality equivalent to AWS IAM but on Azure.

    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

    4 comments  ·  IAM  ·  Admin →

    You can now access Atlas Clusters through Microsoft Entra ID using MongoDB Workforce Identity Federation (https://www.mongodb.com/docs/atlas/workforce-oidc/). The feature is supported by MongoDB 7.0.11 dedicated clusters (M10 and above).


    Thank you for your feedback.

  13. Provide "Last Login Date" for Atlas users via Atlas API

    The Atlas API should include "Last Login Date" for the GET /orgs/{ORG-ID}/users endpoint.

    14 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

    completed  ·  3 comments  ·  Other  ·  Admin →
  14. Add Alerts for Triggers

    Add alerts for when Triggers are suspended or exceed a threshold.

    14 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  ·  Alerts  ·  Admin →

    Thank you all for your feedback! There are alerts available for Trigger suspension that can be configured in your Project Alerts (App Services > Trigger > cannot be restarted or auto resumed). Additionally, we have added a multitude of alerts for the metrics you see in the metrics dashboard on the App homepage - reference sheet here. These can also be found in the Project Alerts under App Services > Metrics > [select condition/metric].

  15. Restore snapshots on s3 back to atlas cluster

    Currently we store Atlas snapshots on S3 for D.R purposes as well as for compliance reasons.

    There was a scenario where an instance was deleted by mistake, and once an instance is deleted all of the atlas managed backup snapshots were gone. In order to restore the Atlas instance we had to do the following:

    1) create a new atlas instance

    2) restore the snapshot from s3 to a temporary mongodb database and then do a dump and restore in order to migrate the data back into the new atlas instance.

    This is a time-consuming process, so if there is…

    13 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 →

    Hello,


    I would like to update everyone on some changes we have made over the last couple of quarters that resolves multiple parts of the overall goal here, in addition to the methods Ben outlined in the past


    First, is Import Archive from S3 in Atlas. This walks you through how to import an archive from S3 back into Atlas.


    In addition to this we now have other protections around cluster and backup deletion protection to protect against human error but also to ensure you can comply with various requirements automatically in Atlas. 


    You now have an option to retain all backups when terminating an M10+ cluster.

    - When you terminated a cluster through the Atlas Ui, on the termination confirmation pop up, you will now see an additional toggle labeled "Keep existing snapshots after termination". If you select this option when terminating your cluster, all of your…

  16. Allow creating alerts via terraform

    Allow creating alerts via terraform

    13 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

  17. Ability to create/update triggers using terraform

    Ability to create/update triggers using terraform

    12 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

  18. YubiKey

    Please consider adding 2FA support for hardware keys (Yubikey). Our company started enforcing this in our compliance policy for accessing production environments.

    12 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  ·  IAM  ·  Admin →
  19. Allow adding a Team to a Project via Terraform

    I can create a Project in Terraform, but I cannot add a Team to it afterwards.

    I am an Organization Member, so I cannot see Projects that I do not have explicit access to. This means that for any Project I create via Terraform, I need to ask someone with more permissions to add my Team to the Project.

    11 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

  20. Return private endpoints for peered network from mongo-db prometheus discovery endpoint

    We are using VPC peering to connect with Mongo Atlas. With the recent account about, prometheus integration. We added scrape config to mongo-db discovery API. However, scraping times out. Upon checking further it is found that discovery API returns public endpoints not private ones. Hence connection is failing. Is there a way that discovery API can send private endpoints.

    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  ·  Alerts  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base