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

460 results found

  1. UI/UX: make site scaling for large screens

    UI/UX: make site scaling for large screens, now text fonts are too small

    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)
  2. Atlas SQL Interface: Support queries based on BinData (UUID)

    We have a need to write reports that query MongoDB via the Atlas SQL Interface using BinData (a UUID with BinData type 4) as selection criteria (see support ticket Case 01313460: Query bindata using atlas sql interface). We were told that this is currently not supported, although querying data based on a unique identifier is a most basic and essential function as far as DB interfaces are concerned.

    Example query from ticket: SELECT * FROM bn_events WHERE _id = CAST('6b0be834-c03e-47bc-9c7d-4726a1e8c69a' AS BINDATA)

    This is a serious limitation that may prevent us from being able to use Atlas SQL Interface 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)
  3. To Include sub dashboards Format in Atlas Charts

    To Integrate related dashboards as sub-dashboards under a single main dashboard to improve organization and navigation

    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)
  4. Unblock users in Russia and Belarus

    Currently MongoDB blocks access to MongoDB Atlas for users who are located on the territory of Russian Federation, Belarus (and other countries).

    MongoDB Support team confirmed this is the case and stated that the reason is US regulations and sanctions, referring only to the blog post published on their website (https://www.mongodb.com/blog/post/mongodb-assistance-ukraine-shut-down-work-russia). The blog post does not mention that the access to users is blocked.

    To our best understanding not many other tech companies have implemented such strict measures.

    We've also taken the time to delve into the sanctions topic and have reviewed every public release of sanctions on…

    4 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

    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. Always show an option for both SRV Connection String and Standard Connection String

    There are more than a few examples where users DNS does not resolve SRV Connections strings. They are often directed to select an old version / legacy connection string.

    Two issues with this are:
    1. Sometimes outdated/deprecated options are provided (ssl=true)
    2. Serverless does not provide this.

    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)
  6. Azure VNet terminology needs updating

    Setting up the Peering Connection (Project Network) has antiquated terminology and instructions.

    Microsoft Entra ID is the new name for Azure AD. The names Azure Active Directory, Azure AD, and AAD are replaced with Microsoft Entra ID. Microsoft Entra is the name for the product family of identity and network access solutions. Microsoft Entra ID is one of the products within that family. https://learn.microsoft.com/en-us/entra/fundamentals/new-name#:~:text=Microsoft Entra ID is the,the products within that family.

    The name change took place on July 15, 2023. https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/new-name

    Currently:

    Directory/Tenant ID

    This is a 32-character alphanumeric string. Find this in the Azure portal in Azure Active…

    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. Customer feedback around the UI of Atlas - unable to edit multiple documents at once

    The customer wanted me to provide product feedback around the inability to edit multiple documents at once from the Atlas UI. The customer uses a 3rd party tool to do this instead and thought it would be better and more intuitive if this was built right into the Atlas UI.

    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)
  8. Stop scamming your users

    How about you stop scamming your users with deceptive instruction on your download pages.

    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)
  9. Within Atlas, create service to allow project owners to schedule shutdown/start up times of cluster to reduce hosting costs

    Request to provide an enhancement to the Atlas service to allow project owners to schedule shutdown/start up times of clusters(or databases) and provide some notification of a successful shutdown and startup. This should be a feature with the Atlas UI and API.

    This will allow teams that have non-critical environments to effectively "turn off" and freeze the state of a cluster in order to reduce hosting cost during off hours. This can provide a better value proposition for existing customers and a selling point for new customers, without having to introduce a third party tool that requires additional configuration and/or…

    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

    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)
  10. Restore a snapshot from one organization to another organization via API call

    I have tried to create automation to restore the snapshot from One organization cluster to other organization cluster. Example Prod cluster from Organization A -> Stage cluster from Organization B.

    currently this method is not possible to restore a snapshot from one organization to another organization via API call as API key cannot be shared over the scope of different organization.( As per mongo atlas support Engineer)

    Please enable this feature to automate the snapshot restore instead of using UI for restore.

    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. Analytics node with NVMe option

    We currently have use mongodb mainly to correct data and visualize with chart features. Some chart require heave disk read operation and need more performance. We need fast storage access only for analytics nodes. If we can select NVMe option only for analytics nodes, we use it but we don't want to switch whole clusters to it since main cluster don't need higher cpu/memory/stroage/iops. We just want to use NVMe only with analytics nodes. Some restriction such as min storage size for main cluster is acceptable but don't want to upgrade to higher tier of main cluster.

    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. Altas CIDR ranges for network containers are too restrictive

    Background:
    For each MongoDB Altas project, the clusters built in that project are built using a "network container", which tells MongoDB Atlas which pool of IPs it can select from given a CIDR range for its underlying infrastructure.

    AWS minimum imposed CIDR value/subnet size: /28
    MongoDB minimum imposed CIDR value for clusters deployed to AWS: /24

    Azure minimum imposed CIDR value/subnet size: /29
    MongoDB minimum imposed CIDR value for clusters deployed to Azure: /21

    For customers who elect connecting to MongoDB Atlas via VPC peering, they know that IP space is a scarce resource. Reserving /24 or /21 IP space…

    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

    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. Push Logs to AWS S3 bucket: IAM role Max_Session expect 12hours

    With respect to the feature "Push Logs to AWS S3 bucket " Atlas expect max-session-duration for IAM cross account role is : 43200 (12HRS) by default.
    Some organizations like us have limitations on max-session. We reached out MongoDB Support, They said " The Atlas team has confirmed that currently, we do not support max session durations of less than 12 hours. However, there is an internal ticket for improvement, where session duration can be internally configurable via MongoDB's internal support UI. Case ref: 01276442

    This will provide a flexibility for the organizations to have max-session configured according to their internal…

    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. Enable the choices of using NVMe SSDs in MS Azure from tier M60 to M40, M50, comparable to AWS.

    Enable the choices of using NVMe SSDs in MS Azure from tier M60 to M40, M50, comparable to 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

    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)
  15. Export logs to S3 at the organization level rather than project level

    Currently if we have to export logs to S3 we need to enable log export to S3 at project level. If I multiple projects then same things needs to be done, there should be an option to send logs to S3 on organization level when setup should send the logs to S3 bucket with path name (projectname+'/'+clustername).

    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)
  16. Support for Push-Based Logging to Azure and GCP

    Asking on behalf of customer, please add Support for Push-Based Logging to Azure and GCP instead of just to AWS S3 buckets: https://www.mongodb.com/docs/atlas/push-logs/

    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)
  17. (RBAC) Remove CREATE_COLLECTION grant from INSERT permission

    In according to the least privilege principle we would like to have a better granularity when defining roles. This feature would help us to have uncontrolled collection creations by applications

    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

    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)
  18. Default Maintenance Window to Out of Hours

    With Atlas MongoDB, maintenance windows when not defined default in many cases to periods during peak hours. With maintenance such as automated rolling upgrades, this can impact performance. I would suggest defaulting this to a time overnight relative to the hosted region of the cluster.

    In addition, there appears to be no obvious way to see what the maintenance window is without inspecting automated updates in the Activity Feed. If this is the case, adding it to the interface would be useful. Note that even toggling the manual setting of the maintenance window to on will default to the first…

    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. Start/Stop Atlas instance from external script

    Currently the ability to stop or restart an Atlas instance is not allowed from the customer's side of things, and is an action that can only be performed by MongoDB Support.
    We would like to have this feature added.

    This use case very important for our organization as different application teams should be able to bring up or down the database as they need.
    We cannot grant permissions on Atlas console to all the teams in our setup.
    Instead, we may have a custom script developed using Javascript or similar scripting languages and enable users to start or stop Atlas…

    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)
  20. VPC flow log to identify the rejected source IP by IP access list

    Customers can identify the source IP addresses dropped by Atlas IP access list if cloud provider flow log like VPC flow log is enabled and stored in the storage like S3.

    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)
← Previous 1 3 4 5 22 23
  • Don't see your idea?

Feedback and Knowledge Base