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

144 results found

  1. 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 →
  2. Update all clusters to have MongoDB 4.4

    I hope that all clusters will be able to use MongoDB 4.4 - including shared ones like M0

    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

    completed  ·  1 comment  ·  Admin →
  3. Support GCP IAM for Cluster Authentication

    Achieve feature parity with AWS IAM cluster authentication support.

    85 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

    14 comments  ·  IAM  ·  Admin →

    Your applications can now access Atlas Clusters with Google Service Accounts using MongoDB Workload Identity Federation (https://www.mongodb.com/docs/atlas/workload-oidc/). The feature is supported by MongoDB 7.0.11 dedicated clusters (M10 and above).


    For your workforce access, we recommend to use Workforce Identity Federation (https://www.mongodb.com/docs/atlas/workforce-oidc/) with your corporate identity provider.


    Thank you for your feedback.

  4. Tag/label project

    Give the ability to tag/label a project

    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

  5. Expose minRetentionHours oplog option

    MongoDB 4.4 introduces the new minRetentionHours for the oplog.
    Currently this option is not exposed in the Atlas UI and the command replSetResizeOplog is not allowed.
    Would be nice to have this option available in Atlas (and be accessible via Terraform too)

    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

    completed  ·  2 comments  ·  Other  ·  Admin →
  6. Change M10+ cloud providers

    I would like to be able to change the cloud provider and region of a M10+ cluster.
    It would be nice also to have a per-cluster connection string that does not depend on the cloud provider. So we can change the provider and region without changing the application settings.

    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

    1 comment  ·  Other  ·  Admin →
  7. Allow Realm to stream application logs to Splunk (or other third party services)

    It would be ideal if there was some native way to send Realm application logs to Splunk (and other third-party log aggregation services), instead of having to build an application in a separate environment to poll this API endpoint (https://docs.mongodb.com/realm/admin/api/v3/#logging-apis) and push logs to Splunk from there.

    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

    completed  ·  0 comments  ·  Integrations  ·  Admin →
  8. Ability to delete account

    I really need to delete my account as this is not what I am looking for.

    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

    8 comments  ·  Other  ·  Admin →
  9. 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

  10. Integrate Azure Private Endpoint

    Enable connectivity in Azure using private endpoints

    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

    completed  ·  5 comments  ·  Other  ·  Admin →
  11. Allow user to specify either more date types, or arbitrary archive criteria

    Currently to configure the online archive service, you specify which column you want to use, which must be a Date type. Our collections often use integer fields holding the offset from the epoch, and there are other fields people might reasonably used.

    My suggsetion would be to allow for a diverse set of date types, or ideally, allow the user to specify the criteria themselves with a mongo query.

    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

    completed  ·  1 comment  ·  Online Archive  ·  Admin →
  12. Possibility to change 'frequency_type' of snapshot backup policy item via Terraform

    Hi,

    I’m facing an issue about Snapshot Backup Policy creation/modification via Terraform ( FYI, I open a case to the support of MongoDB  https://support.mongodb.com/case/00668262). Let me explain :

    When I want to create a MongoAtlas Cluster via terraform, I want to apply a custom Snahsphot Backup Policy with ONLY 2 items during the creation of the cluster :
    N° Item Frequency type Frequency Retention
    0 Daily 1 7 Days
    1 Weekly 1 (Saturday) 4 weeks

    However, during the creation of the mongo atlas cluster, I can see an error
    Error: Error applying plan:

    1 error occurred:
    * module.cluster…

    28 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

    The Cloud Backup policy has been completely reworked as of provider version 1.0.0, with a few more fixes in 1.0.1 (coming shortly). This should address the pain points that have been raised here and elsewhere.

  13. 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].

  14. Atlas backup to second region

    We would like the option to have our Atlas backups automatically copied to a 2nd region to support our DR initiative. I realize we could create a live database node in a 2nd region, but that is more costly and complex. Having the backup sync to another region that we can restore off of in case the primary region fails would be simpler and more cost effective.

    Is this something that is on your roadmap, and if so, when will it be released?

    Thanks!

    169 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

    32 comments  ·  Backup  ·  Admin →

    Hi Everyone!
    We are excited to officially announce the general availability of Snapshot Distribution (multi-region backups)!
    You can find it available in your clusters today. 


    It is available through the UI (at the bottom of the cluster backup policy tab called “Additional Backup Copies”) and through the API. 


    Check out our resources to learn more - Docs | Blog post.


    Sincerely,

    The MongoDB Team

  15. option to create a final snapshot before deleting a cluster

    Today when an Atlas cluster is deleted, all backups/snapshots of this cluster are deleted along with it.

    This is especially an issue when working with automation tools like terraform, where a cluster can be deleted by accident easily.

    In AWS Aurora Postgres, for example, there is an option to create a "final snapshot" before deleting the cluster.

    If this option is enabled for a cluster, whenever a user triggers the deletion of the cluster (either manually, via API, or any other method), a final snapshot will be created, before the cluster is deleted.

    This final snapshot is then available independently…

    91 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

    8 comments  ·  Backup  ·  Admin →

    Hello All,


    I am pleased to announce that 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.


    At any…

  16. Integration with Microsoft Teams

    Add third-party service integration for Microsoft Teams, as we do for Slack.
    Most likely the following can be leveraged to achieve the integration: https://docs.microsoft.com/en-us/graph/teams-proactive-messaging

    28 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  ·  Integrations  ·  Admin →
    completed  ·  Elle responded

    This is now available! You can find the integration on the integrations page in Cloud. Documentation to follow in coming days. 

  17. Show all team users on one page

    When we do SOC2 reviews, we have to take screenshots of the permissions various users have. Currently, a specific "team" in Atlas only shows 5 users at a time and is paginated. Taking screenshots of 5 users at a time is pretty tedious, so it would be amazing to have a page with the full list.

    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

    completed  ·  0 comments  ·  IAM  ·  Admin →
  18. Export metrics to Prometheus

    Currently there is only a community supported Prometheus integration (exporter) available which polls db.serverStatus() and doesn't include as much metrics as the Atlas UI/API provides. A similar integration as with New Relic and Datadog would help many customers that are using Prometheus and Grafana for monitoring.

    83 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

  19. Change Azure snapshot backups from LRS to GRS

    Sorry but this is a must. GRS is a 2 region datacenter backup, LRS only 1. Fire or disaster will take out everything if LRS is used.

    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

    3 comments  ·  Backup  ·  Admin →

    Hello,


    We recently released a feature that we call Snapshot Distribution which allows any Atlas user to copy their backups into additional cloud provider regions that are supported in Atlas. 


    This allows you to store the backups in whatever region you prefer automatically. In the event of a disaster in a cloud provider region, Atlas will intelligently use a backup copy in an additional region for a restore.


    You can read more about this in this blog, https://www.mongodb.com/blog/post/introducing-snapshot-distribution-atlas , and our docs, https://www.mongodb.com/docs/atlas/backup/cloud-backup/scheduling/#configure-service-to-automatically-copy-snapshots-to-other-regions .

  20. Alert when a snapshot restore succeeds/fails

    Simply send an email alert when a restore finishes (or errors).

    This is important for us because we run a restore (from prod to qa) every weekend and it takes over 14 hours. If it fails, we need to know so we can quickly kick it off again before Monday. Otherwise the QA team will be dead in the water.

    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

    1 comment  ·  Backup  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base