151 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  7 comments  ·  Other  ·  Delete…  ·  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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
   completed  ·  Zuhair responded

   This feature has been released in v1.10.0 of the Terraform Provider for MongoDB Atlas! Thank you for the feedback. 

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   10 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
   completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

   Support for 3rd party integrations is now included in version 0.7.0 of the Terraform MongoDB Atlas Provider, available today!

   Thank you for the feedback.

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   8 comments  ·  Monitoring and Metrics  ·  Delete…  ·  Admin →
   completed  ·  AdminFrank (Admin, MongoDB) responded

   10-second level granularity for Atlas projects is available with M40+ clusters. More information on this is available here: https://www.mongodb.com/docs/atlas/monitor-cluster-metrics/#std-label-premium-monitoring

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  2 comments  ·  IAM  ·  Delete…  ·  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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   7 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
   completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

   Just added in the latest version 1.1.1: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/project#with_default_alerts_settings

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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  4 comments  ·  Other  ·  Delete…  ·  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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   completed  ·  1 comment  ·  Data Explorer  ·  Delete…  ·  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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Serverless Instances  ·  Delete…  ·  Admin →
   completed  ·  AdminFrank (Admin, MongoDB) responded

   The ability to programmatically enable/disable automatic indexing on MongoDB Atlas serverless instances via the admin API/terraform resource is now available.

   For more details, please see the relevant documentation here.

   • Admin API documentation
   • Terraform documentation

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →

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.canconnect

    Thanks,

    15 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Monitoring and Metrics  ·  Delete…  ·  Admin →

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    4 comments  ·  IAM  ·  Delete…  ·  Admin →
    completed  ·  AdminFuat (Admin, MongoDB) responded

    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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    completed  ·  3 comments  ·  Other  ·  Delete…  ·  Admin →

14. Add Alerts for Triggers

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

    14 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Alerts  ·  Delete…  ·  Admin →
    completed  ·  AdminLaura Zhukas (Associate Product Manager, MongoDB) responded

    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 the ability to copy the snapshots directly back to the atlas instance that will save some time.

    In addition, this also can benefit a scenario where we archive/purge data on a periodic basis and if needing to restore the data back for compliance reasons we can restore the snapshot, stored in S3, taken before the purge/archive process to another Atlas instance. (with the understanding that the mongo snapshot versions are the same as what is being offered in atlas).

    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… more

    13 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Backup  ·  Delete…  ·  Admin →
    completed  ·  AdminEvin Roesle (Senior Product Manager, Cloud, MongoDB) responded

    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 backups for that cluster will be retained.

    - You can also choose to retain you backups for a cluster when deleting a cluster through the Atlas Administration API. When deleting a cluster through the API, you can include the retainBackups parameter and this will retain all of your backups after termination as well.

    - You can view or use the backups from a terminated (or other active) M10+ cluster by selecting the "Backup" tab in the left side navigation of the Atlas UI.

    
    

    To protect from accidentally deleting a cluster in general, you can utilize the Termination Protection setting in Atlas, which when enabled prevents users from deleting any cluster.

    
    

    In addition to these options, if you would like to protect your backups, in all scenarios, from ever being deleted before the designated retention period has ended, please learn more about our new backup feature called Backup Compliance Policy. 

    - Backup Compliance Policy allows organizations to configure a project-level policy to prevent the deletion of backups before a predefined period, guarantee all clusters have backup enabled, ensure that all clusters have a minimum backup retention and schedule policy in place, and more.

    - With these controls, you can more easily satisfy data protection requirements (e.g., AppJ, DORA, immutable / WORM backups, etc.) without the need for manual processes.

    - Please note that the Backup Compliance Policy can not be disabled without MongoDB support once enabled so please make sure to read our documentation thoroughly before enabling.

    
    

    In addition to Backup Compliance Policy, organizations can also utilize our multi-region Snapshot Distribution to automatically copy backups (snapshots and oplogs) to additional Atlas regions. If your primary cloud experiences a region outage then Atlas will be able to recover with a copied backup from another region, just like any normal restore.

    
    

    With all of these features, you can automatically  protect your data and meet compliance directly in Atlas.

    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… more

16. Allow creating alerts via terraform

    Allow creating alerts via terraform

    13 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

    Released in version 0.4.0: https://www.terraform.io/docs/providers/mongodbatlas/r/alert_configuration.html

    GA info 0.4.0
    https://www.mongodb.com/blog/post/new-major-version-of-terraform-mongodb-atlas-provider

17. Ability to create/update triggers using terraform

    Ability to create/update triggers using terraform

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

    Support for Triggers added in version 1.0.0 of the Terraform MongoDB Atlas Provider.

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    6 comments  ·  IAM  ·  Delete…  ·  Admin →
    completed  ·  AdminFuat (Admin, MongoDB) responded

    Hello, you can use your U2F keys (like YubiKey) as second factor in authentication. It is listed as "Security Key/Biometrics" (also referred as WebAuthn) under Multi-Factor Authentication options. 

    https://www.mongodb.com/docs/atlas/security-multi-factor-authentication/. 

    
    

    We highly recommend  to set up at least 2 MFA option on different devices to avoid lockouts.

    
    

    Thank you,

    
    

    Fuat

    -

    
    

19. efficient backup restore between MongoAtlas Projects

    Hello,

    currently, when we restore a SNAPSHOT from one cluster to another cluster in the same MongoAtas Project (example from "production" project to "production" project), this is very efficient (several minutes).

    On the other hand, if we execute the same backup restore from one cluster to another cluster on another MongoAtlas project (example : from "production" project to "staging" project), this is much less efficient and it will take several hours (instead of several minutes above).

    This is very efficient in the same MongoAtlas project because it will use cloud provider system using hard disk management.

    Could you improve efficiency of backup restore system between MongoAtlas Projects ?
    Similarly, could you do the same if cluster nodes are on different regions ?

    Thank you.
    Regards.
    David

    Hello,

    currently, when we restore a SNAPSHOT from one cluster to another cluster in the same MongoAtas Project (example from "production" project to "production" project), this is very efficient (several minutes).

    On the other hand, if we execute the same backup restore from one cluster to another cluster on another MongoAtlas project (example : from "production" project to "staging" project), this is much less efficient and it will take several hours (instead of several minutes above).

    This is very efficient in the same MongoAtlas project because it will use cloud provider system using hard disk management.

    Could you improve efficiency… more

    11 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Backup  ·  Delete…  ·  Admin →
    completed  ·  AdminKaylee (Admin, MongoDB) responded

    We have released the ability to enable faster restores across projects in AWS for Atlas Backups! You can enable faster cross-project restores by clicking the “Faster Restore” button in the cluster Backup page.

    Learn more here

20. 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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
    completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

    This has been released in version 0.4.0
    https://www.terraform.io/docs/providers/mongodbatlas/r/team.html
    and
    https://www.terraform.io/docs/providers/mongodbatlas/r/project.html

    More info on 0.4.0:
    https://www.mongodb.com/blog/post/new-major-version-of-terraform-mongodb-atlas-provider