1364 results found

1. Control Over how to upgrade minor versions or rollback if required

   Hello Team,
   
   We recently faced an issue with the automatic minor version upgrade that rolled our clusters from 6.0.16 to 6.0.17 through Atlas. Since 6.0.17 has some problems, can we request the following features:
   
   1. Disable automatic upgrades of minor versions.
   
   2. Allow manual rollback to previous minor versions when necessary.

   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

   Submit Rating

2. Control shard balancing window with Terraform

   This documentation page talks about how to manage shard balancing - https://www.mongodb.com/docs/manual/tutorial/manage-sharded-cluster-balancer/#schedule-the-balancing-window
   but it requires connecting to the db first, I see no way to manage this through the Atlas Gui or terraform.
   We have had some instances recently where shard balancing has caused a large resource usage spike on our cluster and affected our services and we would really like to be able to set a shard balancing window using terraform to prevent this from happening during the middle of the day

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

3. Ability to create granular auditing

   I want to be able to create granular auditing for a specific cluster inside a project. Right now, the audit is applied to every cluster inside a project. Some clusters need more auditing than others, and their performance should not be affected by other cluster configuration.

   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

   Submit Rating

4. Support Online Archive in AWS Hong Kong region

   Request to make Online Archive available in AWS Hong Kong region

   Customer are using MongoDB Atlas in AWS HK region to store data that are required to be located in the same region.

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

5. Authority Root/Intermediate Certificate from Let's Encrypt update

   Need to be notified when Authority Root/Intermediate Certificate from Let's Encrypt will be upgraded. It can be a alert/rss flow/notification/email to inform the customer company.
   From documentation https://www.mongodb.com/docs/atlas/reference/faq/security/#hard-coded-certificate-authority (Which certificate authority signs MongoDB Atlas TLS certificates?)

   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

   Submit Rating

6. Exploring MongoDB's Role in Event Sourcing and Kubernetes for Payment Processing

   Hi team, IHAC on premise, looking at kafka for event sourcing but really keen to understand what role MongoDB could play in a kubernetes context. Restricting MongoDB to just store views is IMHO not using the full potential of change streams for example. I believe Kafka could be used for inter system communication but inside this domain (payment processing) it should be better to use MongoDB itself as event store.

   The event sourcing architecture model lends itself well to a serverless processing model, and kubernetes is a great option on premise, but potentially also cross cloud.

   Do we have any plans to create a MongoDB KNative connector?
   Example: https://pkg.go.dev/github.com/googleinterns/knative-source-mongodb

   Hi team, IHAC on premise, looking at kafka for event sourcing but really keen to understand what role MongoDB could play in a kubernetes context. Restricting MongoDB to just store views is IMHO not using the full potential of change streams for example. I believe Kafka could be used for inter system communication but inside this domain (payment processing) it should be better to use MongoDB itself as event store.

   The event sourcing architecture model lends itself well to a serverless processing model, and kubernetes is a great option on premise, but potentially also cross cloud.

   Do we have any… 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  ·  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. Better streamlined logs in GCP

   Running Application and MongoDB in the same public cloud provider. Want to have logs in one place so that in case of any issues, I can debug any production issues properly. For example, in our Development or local environment, we have everything running on Docker Desktop and MongoDB on local Windows laptop. Using Docker tilt - Dev team can see UI, Service tier and backend(MongoDB) logs one after the other in one place. If the request is timing out, we can see that it's a collection scan that is happening not index scan so we need to either create the index or fine tune our query or change the code - making it super easy. But in our GCP Production every thing runs in GCP kubernetes and logs are stderr and stdout of kubernetes and app but no mongoDB even when MongoDB is deployed within GCP. GCP support stated that we can install Google Cloud Ops Agent can be installed to forward the logs to GCP but it seems that won't work as there will be lag. We were told to do a lot of work to make it work which is error prone. It should be out of the box so that any users are not tempted to use cloud native DB solutions that comes with public cloud and still use MongoDB. Please refer Case #01336915

   Running Application and MongoDB in the same public cloud provider. Want to have logs in one place so that in case of any issues, I can debug any production issues properly. For example, in our Development or local environment, we have everything running on Docker Desktop and MongoDB on local Windows laptop. Using Docker tilt - Dev team can see UI, Service tier and backend(MongoDB) logs one after the other in one place. If the request is timing out, we can see that it's a collection scan that is happening not index scan so we need to either create the… 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  ·  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

8. Query profiler drilldown by number of write conflicts

   One sort of issue that can lead to elevated CPU utilization but is otherwise hard to identify is queries with high numbers of write conflicts. Having some way to drill down to queries that exhibit these symptoms would be quite convenient.

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

9. In Atlas, add an alert condition for long-running queries

   In Atlas, add an alert condition for long-running queries

   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  ·  Alerts  ·  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. Forward MongoDB Atlas logs to Securonix

    This is a feature request to integrate the forwarding of MongoDB Atlas logs to Securonix.

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

11. Properly Formatted Prometheus Integration (mongodb_ metrics)

    The (mongodb*) metrics collected by the integration lack the metric type and the description is extremely vague (mongodbcatalogStats_views has "catalogStats." as description). It would be easier to setup dashboards and queries if the type (e.g., gauge, counter) was properly set up and the metric provided a proper description.

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

12. Adding balancer activity from sharding Statistics into Atlas UI

    The customer often experience multiple performance issues in different clusters related to chunk migrations and in each case the customers are struggling with being able to determine that chunk migrations were occurring and started at the same time as the performance issue. The customer is limited in the observability available to identify this problem via Atlas UI:

    Using db.serverStatus().shardingStatistics on each shard can provide what the customers need.

    https://www.mongodb.com/docs/manual/reference/command/serverStatus/#mongodb-serverstatus-serverstatus.shardingStatistics

    In particular, key metrics below will provide good insight on balancer activity :

    For donor:

    1. db.serverStatus().shardingStatistics.countDonorMoveChunkStarted

    : The total number of times that MongoDB starts the moveChunk command or moveRange command on the primary node of the shard as part of the range migration procedure. This increasing number does not consider whether the chunk migrations succeed or not

    1. db.serverStatus().shardingStatistics.countDocsClonedOnDonor

    : The cumulative, always-increasing count of documents that MongoDB clones on the primary node of the donor shard.

    1. db.serverStatus().shardingStatistics.totalDonorMoveChunkTimeMillis

    : Cumulative time in milliseconds to move chunks from the current shard to another shard. For each chunk migration, the time starts when a moveRange or moveChunk command starts, and ends when the chunk is moved to another shard in a range migration procedure.

    1. db.serverStatus().shardingStatistics.countDocsDeletedByRangeDeleter

    : The cumulative, always-increasing count of documents that MongoDB deletes on the primary node of the donor shard during chunk migration.

    1. db.serverStatus().shardingStatistics.rangeDeleterTasks

    : The current total of the queued chunk range deletion tasks that are ready to run or are running as part of the range migration procedure.

    For Recipient:

    1. db.serverStatus().shardingStatistics.countRecipientMoveChunkStarted

    : Cumulative, always-increasing count of chunks this member, acting as the primary of the recipient shard, has started to receive (whether the move has succeeded or not).

    1. db.serverStatus().shardingStatistics.countDocsClonedOnRecipient

    : The cumulative, always-increasing count of documents that MongoDB clones on the primary node of the recipient shard.

    The customer often experience multiple performance issues in different clusters related to chunk migrations and in each case the customers are struggling with being able to determine that chunk migrations were occurring and started at the same time as the performance issue. The customer is limited in the observability available to identify this problem via Atlas UI:

    Using db.serverStatus().shardingStatistics on each shard can provide what the customers need.

    https://www.mongodb.com/docs/manual/reference/command/serverStatus/#mongodb-serverstatus-serverstatus.shardingStatistics

    In particular, key metrics below will provide good insight on balancer activity :

    For donor:

    1. db.serverStatus().shardingStatistics.countDonorMoveChunkStarted

    : The total number of times that MongoDB starts the moveChunk command or moveRange command… 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  ·  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

13. Alert notification for new cluster created in the project

    Greetings, Support
    After looking over the alert settings, I discovered that there aren't any alarms that can be monitored to be informed when a new cluster is created on the present project. Please include a notice about the future release, as it directly correlates with and impacts the price and invoicing.

    (Confirmed with support as there is not such alerts in Atlas with the current settings and case:01298603)

    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  ·  Alerts  ·  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. 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 access to the Atlas environment.

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

15. Support tags in terraform-provider-mongodbatlas mongodbatlas_project

    terraform-provider-mongodbatlas mongodbatlas_project doesn't currently support tags.

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

16. Add support for GCP (Google Cloud Platform) region of dammam (me-central2)

    Dear MongoDB Atlas Support Team,

    I hope this email finds you well. I am writing to inquire about the availability of the MongoDB Atlas region in Dammam, Saudi Arabia.

    As our organization expands its operations, we are seeking a reliable and secure cloud database solution. However, we are obligated to comply with local regulations that mandate the hosting of our data within Saudi Arabia. Therefore, it is essential for us to find a suitable hosting option that meets these requirements.

    After reviewing the available regions for MongoDB Atlas, we noticed that the Dammam region (me-central2) is not currently listed. We kindly request your assistance in clarifying whether this region is planned for future availability or if there are any alternatives that can help us meet the data localization requirements within Saudi Arabia.

    We understand the significance of data sovereignty and the importance of adhering to regional regulations. Therefore, we would greatly appreciate your guidance and support in identifying the best solution that aligns with our compliance needs.

    Thank you in advance for your attention to this matter. We look forward to your prompt response.

    Sincerely,
    Salem Yaslem

    Dear MongoDB Atlas Support Team,

    I hope this email finds you well. I am writing to inquire about the availability of the MongoDB Atlas region in Dammam, Saudi Arabia.

    As our organization expands its operations, we are seeking a reliable and secure cloud database solution. However, we are obligated to comply with local regulations that mandate the hosting of our data within Saudi Arabia. Therefore, it is essential for us to find a suitable hosting option that meets these requirements.

    After reviewing the available regions for MongoDB Atlas, we noticed that the Dammam region (me-central2) is not currently listed. We… 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  ·  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

17. 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 security policy.

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

18. (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

    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

19. Need Prior notification For The Scheduled maintenance

    We have noticed that our servers undergo scheduled maintenance, resulting in unexpected reboots. However, we lack information about the nature and purpose of these maintenance activities. We require a prior notification regarding scheduled minor/major maintenance to ensure that we can take proactive measures from our end. This would enable us to prepare appropriately and minimize any potential disruptions or issues caused by the maintenance.

    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  ·  Alerts  ·  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. Reestablish private endpoint if in status "Rejected"

    Create an AWS endpoint for connection with the (already established) MongoDB Atlas endpoint service -> AWS endpoint is in "Pending acceptance" status.
    Establish the connection with "mongodbatlasprivatelinkendpointservice" -> AWS endpoint goes into "Available" status.
    Destroy the "mongodbatlasprivatelinkendpointservice" connection -> AWS endpoint goes into "Rejected" status.
    Recreate "mongodbatlasprivatelinkendpoint_service" with the same variables -> terraform does recreate he resource, but the resource is not functional.
    In the MongoDB Atlas GUI it shows "Failed. Endpoint failed to reach available state. Click 'Edit' to fix the problem."
    The problem cannot be fixed by using "Edit" !

    According to AWS support it is possible to accept an endpoint in "Rejected" status - therefore the re-creation of "mongodbatlasprivatelinkendpoint_service" should be working completely and change the endpoint status to "Available".

    Create an AWS endpoint for connection with the (already established) MongoDB Atlas endpoint service -> AWS endpoint is in "Pending acceptance" status.
    Establish the connection with "mongodbatlasprivatelinkendpointservice" -> AWS endpoint goes into "Available" status.
    Destroy the "mongodbatlasprivatelinkendpointservice" connection -> AWS endpoint goes into "Rejected" status.
    Recreate "mongodbatlasprivatelinkendpoint_service" with the same variables -> terraform does recreate he resource, but the resource is not functional.
    In the MongoDB Atlas GUI it shows "Failed. Endpoint failed to reach available state. Click 'Edit' to fix the problem."
    The problem cannot be fixed by using "Edit" !

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