457 results found

1. Need static private ip for cluster nodes

   Please see details in https://support.mongodb.com/case/00682480

   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

   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

2. in Atlas Cloud Manager, sort the network IP access list

   page security/network/accessList

   the list of IP addresses is unsorted and unmanageable

   please allow sort by IP or Name (Comment)

   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

3. SAML login on feedback.mongodb.com does not work with Google Auth

   It shows "SAML Error" and redirects the login page to cloud manager. As a result the login success is never passed to feedback.mongodb.com, it's necessary to login again (on the second attempt, it works)

   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

4. Atlas Shard Management

   Currently the Atlas UI only presents options for how many shards a cluster can have.

   Putting in a suggestion to perhaps allow similar functionality / features to Cloud Manager's shard management as shown : https://docs.cloudmanager.mongodb.com/tutorial/manage-data-sharding/#manage-sharded-collections

   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

   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

5. Expose Collection TTL in the UI

   It is very difficult to discover the TTL of a given collection. It would be great if the TTLs for each collection was visible in the collection UI.

   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  ·  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

6. Comments on Private Endpoints to aid identification

   On Atlas when creating private endpoints, add comments field to allow easier identification.

   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  ·  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

7. Ability to schedule monthly maintenance windows

   Ideally we'd have the ability to schedule maintenance windows that are monthly. Either the option to say maintenance run on the 3rd of the month or every 2nd Tuesday. The current issue I see is that your non-prod clusters and prod clusters can share the same window and get patched at the same time, or you pick different days of the week for patches (e.g. Monday for non-prod, Friday for prod), but we risk having prod patched before non-prod in that situation.

   I realize we have the ability to defer maintenances for a week, which is great. However, we're now at the mercy of a human remembering to defer a prod maintenance while the non-prod maintenance goes through.

   Ideally we'd have the ability to schedule maintenance windows that are monthly. Either the option to say maintenance run on the 3rd of the month or every 2nd Tuesday. The current issue I see is that your non-prod clusters and prod clusters can share the same window and get patched at the same time, or you pick different days of the week for patches (e.g. Monday for non-prod, Friday for prod), but we risk having prod patched before non-prod in that situation.

   I realize we have the ability to defer maintenances for a week, which is great. However, we're now… more

   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

8. Add a single-node option.

   mLab had the option to create a single-node deployment, which was very nice for development environments where redundancy isn't important, but keeping costs down is.

   Would be nice to see this in Atlas as well.

   32 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

   6 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

9. if we had option for diabling javascript execution on database we would have to no worry about it

   javascript excuiton can be used for harm and mass deletion data. İf we had no javascript execution we would be safer.

   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  ·  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

10. Option to configure an on-prem hidden replica set member for an Atlas replica set

    As described in https://docs.mongodb.com/manual/tutorial/configure-a-hidden-replica-set-member/, on-prem mongodb deployments allow to configure a hidden replica set members which are good for workloads with different usage patterns from the other members in the replica set. It would be useful to have similar functionality for Atlas replica sets.
    In fact, to elaborate, being able to configure an on-prem hidden replica set member for an Atlas replicaset will help in meeting regulatory requirements where organisations are required to host a near real time mirror of data on on-premises.

    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

    3 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

11. Have the ability to downgrade

    Currently Atlas doesn't support the ability to downgrade major version. I know with Ops Manager on-prem you can do that, which is helpful if you find issues during an upgrade. Would it be possible to get the ability to downgrade one major version on the roadmap?

    As of today, if we have issues with an upgrade, we have to build a new cluster with the older version, export and import into the new cluster. That's a much more painful process including the fact that you have to change the connection strings of your applications to point to the new cluster name. And on top of that, you have to take a longer outage to move all of your data between clusters.

    Currently Atlas doesn't support the ability to downgrade major version. I know with Ops Manager on-prem you can do that, which is helpful if you find issues during an upgrade. Would it be possible to get the ability to downgrade one major version on the roadmap?

    As of today, if we have issues with an upgrade, we have to build a new cluster with the older version, export and import into the new cluster. That's a much more painful process including the fact that you have to change the connection strings of your applications to point to the new cluster… more

    10 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

12. LDAP Authentication: Allow Private Endpoint to the customer

    Currently, LDAP Authentication from Atlas to a customer's LDAP service can go via the Internet or via VPC peering. In lieu of VPC peering, I propose using a Private Endpoint FROM Atlas TO a customer VPC that hosts the LDAP service.

    NOTE: This would NOT be using the same Private Endpoint connection that Atlas currently supports today, which allows customers to reach their clusters privately (Customer -> Atlas).
    This would be an additional Private Endpoint in the other direction (Atlas -> Customer).

    Advantages of using Private Endpoint vs VPC peering:
    * Security: The customer VPC is not exposed to Atlas, just the LDAP service
    * Configuration: The customer won't need to verify that the Atlas VPC CIDR doesn't conflict with the customer CIDR
    * Scalability: Each Project requires a separate VPC peering connection which makes for a difficult situation with having to configure each Project VPC CIDR to be non-overlapping. In contrast, the same LDAP Private Endpoint can be shared to multiple Project VPCs.
    * Complexity: Configuring a Private Endpoint is less complex than a VPC peering connection, both for Atlas and for the customer.
    * Routing/security groups: The customer does not need to configure VPC routing, nor do they need to configure security groups to protect resources in the VPC

    In AWS, the customer LDAP service would need to be hosted as a Network Load Balancer. The good news is that NLB targets can be hosts in AWS or in a customer data center.

    Currently, LDAP Authentication from Atlas to a customer's LDAP service can go via the Internet or via VPC peering. In lieu of VPC peering, I propose using a Private Endpoint FROM Atlas TO a customer VPC that hosts the LDAP service.

    NOTE: This would NOT be using the same Private Endpoint connection that Atlas currently supports today, which allows customers to reach their clusters privately (Customer -> Atlas).
    This would be an additional Private Endpoint in the other direction (Atlas -> Customer).

    Advantages of using Private Endpoint vs VPC peering:
    * Security: The customer VPC is not exposed to Atlas,… 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  ·  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

13. Create alarms base on events + Add control policies

    Events (in the perimeter: organization, projects, cluster) are useful for monitoring activities. But it would be very useful to be able to set the alarm on these events. The goal is to be informed when certain actions occur.

    The best is to be able to have a configuration control policy. Especially to control security, network configuration, etc ...

    For example:
    - Be able to avoid the use of user scram.
    - Be able to avoid using unauthorized IP addresses
    - Be able to avoid changing the configuration of access to database data (DataExplorer) from the Atlas portal

    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

    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

14. Warning if attempting to change cluster configuration while an index operation is in progress

    When changing the cluster configuration to scale it up or down, there is no warning if there's a index build currently running on the primary/secondary. I created an index, saw it finish on the primary and then scaled the cluster, without thinking about that the index is only now built on the secondary, too.

    During the downscaling the index build got aborted and attempted to build in foreground then. However this for some reason did not work and I had to contact support to help me with getting the secondary up again.

    My proposal would be to either:
    - Display a warning when trying to change the cluster configuration that requires a reboot of the nodes, while an index build is currently in progress on one of the nodes
    - Show the index build also for the secondaries in the "realtime" metrics to raise awareness that an index build is happening on the secondaries only after the primary has finished and to show progress for the secondaries as well.

    When changing the cluster configuration to scale it up or down, there is no warning if there's a index build currently running on the primary/secondary. I created an index, saw it finish on the primary and then scaled the cluster, without thinking about that the index is only now built on the secondary, too.

    During the downscaling the index build got aborted and attempted to build in foreground then. However this for some reason did not work and I had to contact support to help me with getting the secondary up again.

    My proposal would be to either:
    - Display… more

    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

15. Enable setting the security.redactClientLogData parameter.

    We're using Atlas to store PII (HIPAA), and we need to store the log files for an extended period of time, but we don't want any PII / HIPAA data to be stored in the logs.

    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

    8 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

16. ignore notimeout cursor (after initial warning?) to avoid breaking compatibility with apps

    In Q4 2020, the notimeout cursor was no longer allowed on free or shared instances.

    As several DB management tools hardcoded this option for optimum performance it breaks compatibility with them. We use a combination of free/shared-tier instances for dev in combination with dedicated instances for production; this limit effectively means we either have to WAY overprovision our dev resources, or we can't use our tooling anymore on it.

    Please provide a way to simply ignore the notimeout option, instead of breaking its connection.

    Thanks!

    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  ·  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

17. major version downgrade request (4.0 to 3.6)

    Right now I am running the MongoDB cluster on 3.6. Now I want to upgrade this cluster to 4.0. But when I want again to revert back to 3.6 I have no option to downgrade.

    Use case :

    Right now our production is running on 3.6, when we upgrade this to 4.0 and if we face any major issues on prod, then we have no option to get back to old version 3.6.

    Without this option we cannot move our production to 4.0.

    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

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

18. Improving Directions to Support on Atlas

    Submitting this on behalf of customer (libra@wavecreststudios.com):

    If I may provide some feedback, the Atlas site is not clear for how to get
    support. Clicking Support in the upper right menu brings you to the support
    portal, which you can't use if you don't have a plan. It's only when
    you're viewing all your projects (and not viewing a specific project) that
    there's a support link on the left side to upgrade your plan.

    Also, and this was very frustrating, it's not clear that "chat support" is
    for general questions and not for urgent issues (usually chat means
    immediate help). I had to wait an hour for a response while
    mid-conversation (we had already talked for a bit), and I don't think it's
    unreasonable to assume if you're in the middle of a chat with someone that
    they will get back to you in a few minutes. You should add a message to
    the top of the chat window when first opening it that chat is not for
    support beyond basic questions, and provide a link to the account's support
    plan settings. That would have saved me a few hours last night.

    Submitting this on behalf of customer (libra@wavecreststudios.com):

    If I may provide some feedback, the Atlas site is not clear for how to get
    support. Clicking Support in the upper right menu brings you to the support
    portal, which you can't use if you don't have a plan. It's only when
    you're viewing all your projects (and not viewing a specific project) that
    there's a support link on the left side to upgrade your plan.

    Also, and this was very frustrating, it's not clear that "chat support" is
    for general questions and not for urgent issues (usually chat means… more

    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

19. Improving Directions to Support on Atlas

    Submitting this on behalf of customer (libra@wavecreststudios.com):

    If I may provide some feedback, the Atlas site is not clear for how to get
    support. Clicking Support in the upper right menu brings you to the support
    portal, which you can't use if you don't have a plan. It's only when
    you're viewing all your projects (and not viewing a specific project) that
    there's a support link on the left side to upgrade your plan.

    Also, and this was very frustrating, it's not clear that "chat support" is
    for general questions and not for urgent issues (usually chat means
    immediate help). I had to wait an hour for a response while
    mid-conversation (we had already talked for a bit), and I don't think it's
    unreasonable to assume if you're in the middle of a chat with someone that
    they will get back to you in a few minutes. You should add a message to
    the top of the chat window when first opening it that chat is not for
    support beyond basic questions, and provide a link to the account's support
    plan settings. That would have saved me a few hours last night.

    Submitting this on behalf of customer (libra@wavecreststudios.com):

    If I may provide some feedback, the Atlas site is not clear for how to get
    support. Clicking Support in the upper right menu brings you to the support
    portal, which you can't use if you don't have a plan. It's only when
    you're viewing all your projects (and not viewing a specific project) that
    there's a support link on the left side to upgrade your plan.

    Also, and this was very frustrating, it's not clear that "chat support" is
    for general questions and not for urgent issues (usually chat means… more

    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  ·  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

20. Merge All Of the MongoDB services Into 1

    I have multiple feedbacks/ideas:

    1) There is MongoDB Atlas, Realm, & Stitch. Why don't you merge all of it into one - MongoDB Atlas.

    2) Instead of creating Organizations -> Project -> Clusters, you can just create Organizations -> Clusters without the Project.

    There are a lot of platforms, which is very confusing for all of the developers to use. Instead, there can be only one platform in which, they can perform everything with simple integration of the programming languages.

    You could simplify your docs as well and like I said, have only one type of integration with all of the programming languages.

    If you implement my idea, it will become very easy for developing and you can get more customers. Why should everything be hard?

    I have multiple feedbacks/ideas:

    1) There is MongoDB Atlas, Realm, & Stitch. Why don't you merge all of it into one - MongoDB Atlas.

    2) Instead of creating Organizations -> Project -> Clusters, you can just create Organizations -> Clusters without the Project.

    There are a lot of platforms, which is very confusing for all of the developers to use. Instead, there can be only one platform in which, they can perform everything with simple integration of the programming languages.

    You could simplify your docs as well and like I said, have only one type of integration with all of… more

    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

    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