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

152 results found

  1. Expose auto cluster scaling options via Terraform

    We would like the ability to configure an auto scaling cluster via Terraform. Currently we need to modify our cluster after its creation via terraform to setup auto scaling parameters.

    37 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

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

    Thank you to everyone who provided input here and directly. We are about to release the provider, v0.6.0, which exposes the autoscale attributes for clusters and includes a recommendation to use a lifecycle block to prevent Terraform and Atlas from conflicting (this will be included in the clusters documentation that will come out w/ the release). Please continue to provide suggestions here or reach out directly to melissa.plunkett@mongodb.com. Thank you!

  2. 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)
    Close
    Close

    We’ll send you updates on this idea

    3 comments  ·  Terraform Provider  ·  Admin →

  3. 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)
    Close
    Close

    We’ll send you updates on this idea

    2 comments  ·  Alerts  ·  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].

  4. 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)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  5 comments  ·  Other  ·  Admin →

  5. Support arm64 in terraform-provider-mongodbatlas

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Terraform Provider  ·  Admin →

  6. Add Switzerland Regions

    Hello, our product heavily relies on mongo atlas and we're very happy with it. However, several of our (corporate) clients would like their application data to be hosted in Switzerland (for compliance/data protection reasons). I would love the ability to setup a Swiss only Atlas cluster for those clients, but the closes options we have in Germany only. Either cloud provider will be fine (ideally Azure). Many of your (future) clients would certainly welcome this too (banks! luxury! healthcare! pharma! transportation! public services!) - thanks for listening :)

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Other  ·  Admin →

  7. Enable AWS EBS Fast Snapshot Restore (FSR) on Atlas

    To speed up recovery after restoring from a snapshot or having a node replaced, it would be nice to have the option to use AWS Fast Snapshot Restore

    https://aws.amazon.com/blogs/aws/new-amazon-ebs-fast-snapshot-restore-fsr/

    This would allow the disk to have full performance as soon as available.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Backup  ·  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.

  8. 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)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  0 comments  ·  Integrations  ·  Admin →

  9. 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)
    Close
    Close

    We’ll send you updates on this idea

    8 comments  ·  Monitoring and Metrics  ·  Admin →

  10. 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)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  IAM  ·  Admin →

  11. I'd like to have a scheduled mongodump backup option

    I'm coming from mLab and I'm used to having an option in my backup strategy that includes a mongodump backup as well as what Atlas calls a CPS (cloud provider snapshot). The latter is actually a snapshot of the database directory at the filesystem level, which is great for instant restores within Atlas (same or different cluster). However, the mongodump backup (from mLab as an example) allows me to backup on a regular schedule and download those backups for restores locally and elsewhere outside of Atlas.

    Yes, I can run mongodump operations myself from a system outside of Atlas, but…

    72 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    9 comments  ·  Backup  ·  Admin →

  12. Ability to create database users limited to specific clusters

    We have a single project set up for our application, and multiple clusters under that project. Right now, it's impossible to create database users who only have access to certain clusters - the only configurable option is "database name".

    The issue is that some of the clusters have the same "database name" but I don't want them to be able to access a database in a specific cluster, though I do want them to access a database with the same name in a different cluster.

    Any plans to implement this?

    60 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    13 comments  ·  Other  ·  Admin →
    completed  ·  AdminAndrew Davidson (VP, Cloud Products, MongoDB) responded

    Folks I’m excited to share that database users scoped to particular sets of clusters (and Data Lakes) in an Atlas project is now live in Atlas!
    – It is now possible to create database users with privileges scoped to a specific set of clusters or Atlas Data Lakes in an Atlas project.
    – Existing users’ privileges can be edited to reduce their scope to a specific set of clusters or Atlas Data Lakes
    – All authentication mechanisms (SCRAM, X.509, LDAP, AWS IAM) may be used in conjunction with this ability

    Thanks for your patience: this was a long-time coming!

    Cheers
    -Andrew

  13. 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)
    Close
    Close

    We’ll send you updates on this idea

    10 comments  ·  Terraform Provider  ·  Admin →

  14. atlas portal ip whitelist

    We were given this idea from a security audit.

    From a security-in-depth perspective we would like to be able to restrict logins on the atlas portal to only whitelisted IP's, this would be analog as to how API whitelisting works at the organization level.
    This is to prevent login's other than from our permitted sites.

    8 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  6 comments  ·  IAM  ·  Admin →

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

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Admin →

  16. Allow Atlas clusters to be paused using terraform

    The ability to pause Atlas clusters through terraform would help with being able to pause our non-prod environments when not in use. Currently this has to be managed directly with the Atlas API

    26 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Terraform Provider  ·  Admin →

  17. 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)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Backup  ·  Admin →

  18. 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)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Online Archive  ·  Admin →

  19. 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)
    Close
    Close

    We’ll send you updates on this idea

    completed  ·  7 comments  ·  Other  ·  Admin →

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

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Admin →
1 2 3 4 6 8
  • Don't see your idea?

Atlas

Categories

Feedback and Knowledge Base

(thinking…)