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

1369 results found

  1. org owner permissions won't revoke due to role mapping

    When choosing to use idp role mapping, if a user is not part of a group, his permissions are revoked, including locking him out of crucial administration options.

    Users with the org owner permissions should be handled as super users and be excluded from any role mapping in order to refrain from having their permissions change

    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

    0 comments  ·  IAM  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Metric Charts Aggregated by Primary Node at the Time

    Providing an aggregated metrics based on the primary server. Right now in order to view history for the primary we have to compare the different charts based on failover, makes it cumbersome to view the active primary trends

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Allow backup of Archived Data and Region Level Redundancy

    1) For protection from Security threats like ransomware attacks where the complete data on disk can be corrupted we need a backup solution for the Archived Database. There should be cyclic backups from where the complete data can be retrieved.

    2) For HADR compliance and to support almost 100% uptime, we need the Archived Data to have Region Level Redundancy not just AZ level redundancy.

    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

    0 comments  ·  Online Archive  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Memory managed on the mongodb atlas nodes

    we recently had a major outage due to OOM on the mongodb shard nodes . we would suggest help preventing this by providing below features so this can be managed properly going forward

    1. Set the memory allocated to the WireTiger Cache
    2. Configure more memory for a tier. The current tier is M50 (8 vCPUs, 32GB memory). We would like to be able to allocate more memory for M50 to handle more connections and memory use for workloads. Scaling up to M60 will double the vCPUs to 16 which we do not want. Perhaps offer tier with high memory usage for…
    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Support double/string epoch time for date match

    Allow a broader range of data types (double, string..) for epoch times.

    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

    0 comments  ·  Online Archive  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. og the size of oplog-mongomirror.bson.sz at time of deletion in mongomirror logs

    currently when we run the mongomirror with --oplog, it does the status when it is deleted.
    It will be good , to add the size information of oplog-mongomirror.bson.sz, that will help us to decide the appropriate disk .

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Tags for Functions, Values

    A feature to quickly see which functions I already completed, tested, updated, whatever. Like a simple tagging system so that we could add tags to a function just for visibility to quickly see which functions need which work!

    (In addition to this idea: https://feedback.mongodb.com/forums/945334-atlas-app-services/suggestions/40550581-folders-for-functions-values )

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. showing metric about online archiving

    there is no any metric about online archiving. We would like to see Atlas Archival Seek, Atlas Data Federation AWS - Data Processed metrics on cluster section or data federation section which is in projects.

    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

    0 comments  ·  Online Archive  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. e-2-e mongo s3 export encryption

    Dear Atlas Team,

    Regarding https://www.mongodb.com/docs/atlas/backup/cloud-backup/export/ would it be possible to have the option of e-2-e encryption so that we just provide you with public key ?

    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

    0 comments  ·  Backup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. secrets versioning for database users

    We would like to have secrets versioning on atlas end so that secrets rotation is easier - as it is a periodic procedure in most companies, would be great to refer to a new secret version of an existing user instead of recreating the user.
    also considering this is sadly not gonna be handled https://feedback.mongodb.com/forums/924145-atlas/suggestions/44283477-vault-should-return-users-only-once-they-can-be-us would be cool to make rotation easier.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. There is a grammatic error in button text.

    The button says "Do not me show again"; it should say "Do not show me again".

    Thank you,
    Alpesh

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Change shortcut for GOTO

    The current shortcut (CTRL + SPACE + TAB) for the GOTO functionality is incredibly annoying as it results in a tab switch in Chrome, and it's also quite slow to reach for a shortcut.

    A suggestion would be to use CTRL + K which usually in Chrome is "Search on Google", but it's also used by GitHub for their version of "GOTO", so pressumably a whole lot of people are already used to it.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. mongoexport - generate multiple compress files as output

    This is a feature request for https://github.com/mongodb/mongo-tools/blob/master/mongoexport/main/mongoexport.go

    • similar to s3.format.maxFileSize parameter in ADL $out, cut a new file every xxxMB
    • similar to s3.format.columnCompression parameter in ADL $out, use gzip/zstd to compress the output BSON or JSON
    • support write to locally-mounted file system (EBS/NFS) and cloud object store S3/GCS

    The similar logic has probably implemented in the ADL $out codebase already, we just need to port them over to mongoexport

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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

    0 comments  ·  Integrations  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Add AWS Switzerland AZ

    Please add the new AWS Switzerland AZ to the list of allowed deployment locations
    https://www.mongodb.com/docs/atlas/reference/amazon-aws/

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Add alerts for long Index building

    Add an alert that is triggered if the time it takes for and index to build is higher than X minutes

    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

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Implement SCRAM-SHA-256 mechanism for Atlas or make a SCRAM-SHA-1 as default

    The main problem is inconsistency in the default authentication mechanism of clients and Atlas.

    This causes a failover from SCRAM-SHA-256 to SCRAM-SHA-1 by clients on authentication failure.

    This causes a huge number of errors in "Database Access History" which becomes useless.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Granular archiving window - schedule archiving at multiple times

    At present online archiving can only be sceduled once per day/week/month. There should be an option to add multiple scheduling windows in a day/week/month to enable schedules such as "every Saturday and Sunday", or "at 3AM and 10PM".

    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

    0 comments  ·  Online Archive  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Minimum Oplog Retention Period - Set Minimum Oplog Window

    The documentation states: "New in version 4.4: Starting in MongoDB 4.4, you can specify the minimum number of hours to preserve an oplog entry." https://www.mongodb.com/docs/manual/core/replica-set-oplog/#minimum-oplog-retention-period

    The mongodbatlas_cluster resource in the terraform mongodbatlas provider only provides for the oplog_size_mb argument. https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/cluster#oplog_size_mb

    It would be nice to have that exposed so that terraform can update that value.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base