1362 results found

1. Ability to enable LDAP and IAM auth at the same time

   We would like the ability to have LDAP and IAM auth enabled on the same cluster at the same time. Today, you can only have one enabled, not both. Our goal is to use IAM auth for programatic access and LDAP auth for human access.

   Please let us know when this gets prioritized.

   9 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

   1 comment  ·  IAM  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Serverless instances on AWS South American region

   It will be nice to have serverless instances on AWS South America. This model is great for this region and I strongly believe that it can have a lot of demand.

   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

   4 comments  ·  Serverless Instances  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Should give download CSV option for getting all the slow queries details

   It will be better if a have an option to download all the slow query related information as whatever we see in the Atlas UI.

   5 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

   1 comment  ·  Performance Advisor  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Ability to choose a Primary shard for newly created database

   In a multi tenant architecture, the isolation of a tenant on a specific shard (when database sharding is involved) is expected. At this time, the ability to choose a Primary shard for newly created database would come in handy

   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

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Add project user role to Create App Services apps

   (Creating on behalf of a customer.)
   Create an Atlas project user role to only allow Create App Services apps (similar to the Atlas Search index creator role we have.

   5 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  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Add Terraform support for Device Sync

   Device Sync (https://www.mongodb.com/docs/atlas/app-services/sync/get-started/) can't be managed via Terraform. This would be a great addition to the provider!

   1 vote

   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

   1 comment  ·  Terraform Provider  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Add metrics to monitor CPU credits for burstable performance Atlas clusters

   Add metrics to Atlas for tracking burstable CPU credit spend for M10 and M20 cluster tier instances. Additional add support for creating alerts based on these metrics.

   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

   3 comments  ·  Monitoring and Metrics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Allow autoscale for connections

   Allow autoscale for connections

   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

   2 comments  ·  Autoscaling  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Option to Enforce Certain MFA Methods

   Allow certain MFA methods to be disabled for our Organization.
   e.g. we don't trust SMS or Email so want to force our users to only use Google Auth / Security Key/Biomeytric or Okta.

   3 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

   1 comment  ·  IAM  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Integration with Percona Monitoring & Management

    Please release Integration to Percona Monitoring & Management. Thank you.

    1 vote

    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  ·  Integrations  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Increase total number of archives limit

    Hello,

    We are looking to archive hundreds of collection from each of our clusters. Right now, online archive only allows you to archive maximum 50 collections. It would be very helpful to increase that limit to at least 500. It would be okay if all of them are not active, but it would really help if we could archive more than 50 collections in total.

    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

    1 comment  ·  Online Archive  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Parent - Child account set up

    I have a client that has multiple BUs and would like to organize them under a Parent account. From my understanding, Atlas does not currently support a Parent-child account set up. This would be beneficial to have as we continue to onboard our enterprise clients and we get more use cases.

    1 vote

    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

    1 comment  ·  IAM  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Support Ticket subject lines

    MongoDB Support to have nicer subject lines for the notification emails sent out by the MongoDB Support Portal.

    There's nothing distinguishing except a case number (which mean nothing), and it’s hard for me to differentiate or even show up in local searches. Going to an external ticket tracking system is a bit of a hassle, and won’t be integrated with any of our local search or content management stuff.

    It would be good to have it headed with what my case is about.

    1 vote

    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  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Support Azure Blob Storage in addition to AWS S3 for Online Archive

    Currently, there is only one option to store the archive data and that is in AWS S3 buckets. We have contractual obligations with clients to store data in Azure. It would be great if MongoDB gave an Azure alternative to AWS S3 like Azure Blob Storage.

    8 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  ·  Online Archive  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Please make it possible to deploy instances to AWS local zones

    Please make is possible to be able to deploy instances in AWS local zones, to be able to comply with local regulations, where data needs to be stores in a specific country,

    1 vote

    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  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Allow disabling TTL Monitor (to allow restoring a snapshot)

    Problem:
    If you are restoring a snapshot to check the data, or to look at old data, and the collection has a ttl index, then a snapshot, once restored, will immediately mark a bunch of records for deletion, thus making it impossible to examine, export, or otherwise use that data.

    Solutions recommended by support include a) download the snapshot (which is very large) and load it on a local instance with the ttl monitor disabled. b) open a ticket to ask for the ttl monitor to be disabled on a target cluster, however once complete you also need to ask for the ttl monitor to be enabled, as otherwise "...eventually, the sessions collection may become full". This means that examining backup data now has multiple support delay loops involved.

    We need a way to restore a snapshot so that we don't lose data to the ttl monitor, without requiring support involvement.

    Possible Proposed Solutions:
    - Allow project owners to disable the TTL Monitor for a cluster, OR
    - Allow restoring a snapshot to include an option to disable TTL monitor for [ select a duration | v ], OR
    - Allow a new cluster, on creation, to be created with the ttl monitor (permanently?) disabled (and some other mechanism clearing the sessions or anything else thats necessary) ,OR
    - some other solution to allow marking a restore as "don't allow restored records to be ttl'd out"

    • It might also be useful to provide a mechanism for cleaning the sessions while the TTL Monitor is disabled

    Why this matters to me:
    - We tried to pull data from a backup to calculate a longer history and didn't realize that the data was being deleted while we were trying to export the data, which meant we provided bad info.
    - There was no real way for us to restore quickly - best case is a several hour delay after creating a cluster to restore to.
    - Without some solution here, relying on snapshots as backups seems really.... bad, and needlessly slow to recover.

    Problem:
    If you are restoring a snapshot to check the data, or to look at old data, and the collection has a ttl index, then a snapshot, once restored, will immediately mark a bunch of records for deletion, thus making it impossible to examine, export, or otherwise use that data.

    Solutions recommended by support include a) download the snapshot (which is very large) and load it on a local instance with the ttl monitor disabled. b) open a ticket to ask for the ttl monitor to be disabled on a target cluster, however once complete you also need to ask… more

    5 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  ·  Backup  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. change streams serverless

    Hi. I need the "change streams" feature implemented for serverless deployments.

    At this time it's unclear when will it be implemented, hence it's difficult to plan ahead.

    Why is that important?
    My nodejs app relies on change streams. Without it - the app simply cannot start because basic functionality is missing.

    Our devteam maintains a few complete vertical qa/testing stacks. Developers/QA/Product people load their change into these stacks and share with others. They are then used for product UI validation, sanity/automated testing etc.

    Because the app depends on change streams, those stacks are restricted to use only production Atlas clusters.

    The bandwidth and performance required from those stacks is miniscule. Using the production clusters is not cost effective (and waste of hw resources!).

    My understanding is that the Serverless deployments were created exactly for this reason. However for us they are completely useless unless to us they support change streams.

    Please update re the feature's expected timeline.

    Hi. I need the "change streams" feature implemented for serverless deployments.

    At this time it's unclear when will it be implemented, hence it's difficult to plan ahead.

    Why is that important?
    My nodejs app relies on change streams. Without it - the app simply cannot start because basic functionality is missing.

    Our devteam maintains a few complete vertical qa/testing stacks. Developers/QA/Product people load their change into these stacks and share with others. They are then used for product UI validation, sanity/automated testing etc.

    Because the app depends on change streams, those stacks are restricted to use only production Atlas clusters.

    … 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

    1 comment  ·  Serverless Instances  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Custom the time interval when do the primary failover manually

    Currently, the time interval of the primary failover manually is done within several seconds. We want to increase the time interval of the primary failover, so the chaos engineer could be done in our server which connects to Atlas.

    1 vote

    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  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Disable (or warn about) destructive features

    We already have Termination Protection enabled in our production cluster. That's great, but only applies to the whole cluster.

    It would be great if there was a way to enable additional finer-grained safety features in MongoDB that would apply to large-scale destructive actions taken in either Atlas or mongosh. These could be presented as additional warnings or require additional confirmation even for users with administrator rights to re-consider their life choices. I.e. "are you really REALLY sure you want to drop that collection?". These could apply to the entire project, rather than individual databases or collections.

    For example, these features are rarely if ever used in our production environment:

    • db.collection.drop()
    • db.collection.remove() or db.colletion.deleteMany(), especially if the query is empty or results in a very large number of documents
    • db.collection.dropIndex() and db.collection.dropIndexes() -- the "Require Indexes for All Queries" setting is too late to catch this
    • $out operator (and perhaps $merge as well) in aggregation pipelines.

    Of those, only $out is somewhat covered: MongoDB Atlas Data Explorer's aggregation query warns the user before executing a pipeline that ends in a $out stage. mongosh has no similar warning.

    We already have Termination Protection enabled in our production cluster. That's great, but only applies to the whole cluster.

    It would be great if there was a way to enable additional finer-grained safety features in MongoDB that would apply to large-scale destructive actions taken in either Atlas or mongosh. These could be presented as additional warnings or require additional confirmation even for users with administrator rights to re-consider their life choices. I.e. "are you really REALLY sure you want to drop that collection?". These could apply to the entire project, rather than individual databases or collections.

    For example, these features… more

    2 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  ·  Data API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Add option to "Explain" a query from the "Profiler" page.

    The profiler page shows a list of queries with metadata about them. It would be great to have the option to "explain" any query from this view, or in the slide-out view after clicking on a query.

    7 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  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating