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

1242 results found

  1. Safe mode to pause non-essential changes

    I'd like to be able to put the cluster into a "Safe Mode" during an incident.

    For example, I'm responding to an incident or I suspect something's fragile or breaking, and I don't want any scheduled activities to make it worse or distract me. I also don't want to have to know what changes are scheduled, I want to pause them all regardless.

    This would pause any scheduled or non-critical changes, like upgrades, building indexes, probably resyncs, etc.

    But it would keep running cluster-safety/health-supporting mechanisms like auto-heal, and probably backups.

    And it would put up a banner on the cluster…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    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. Storage autoscaling of storage should also occur when Atlas searches are being rebuild

    When the storage requirement exceeds the available storage when rebuilding Atlas searches a warning is issued and manual intervention is needed.

    I would like that autoscaling of storage will occur when needed for rebuilding Atlas indexes.
    This would save us time and no need to react to warnings.

    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  ·  Autoscaling  ·  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. Atlas metrics granularity after 48 hours

    For metrics older than 48 hours, the data is presented in 1-hour intervals. This level of granularity is often too coarse for a thorough examination of past events and trends. Such a broad view can obscure smaller yet significant details critical for understanding and resolving performance issues that occurred in the past.

    Suggested Improvement:

    having a smaller granularity value for historical metrics beyond the 48-hour timeframe. Providing data in smaller intervals would greatly enhance our ability to conduct in-depth analyses and diagnose past performance issues accurately. This would be particularly beneficial for conducting detailed investigations of historical data and identifying…

    3 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

    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 hourly backup every 24 hours, or support Point-In-Time restore without an hourly backup

    To have Point-In-Time restore, an hourly backup policy is required.
    However, the maximal interval for an hourly backup is every 12 hours.
    I would like to take a backup only once every 24 hours, but still have Point-In-Time restore possible.

    So, please support either PIT-restore without an hourly backup policy in place, or support an hourly backup policy with an interval of 24 hours.

    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  ·  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)
  6. Push Atlas org events and projects to S3

    Similar to cluster logs being pushed to s3 feature, if a feature to push organization, project and cluster events to s3, our event ingestion pipelines could be simplified significantly. Without the feature we are forced spin up event ingestion agents and make them reliable/available. These ingestion agents source the events via API and publish them to cloud watch logs, that are eventually fed into our observability stack. If the events can be pushed into s3, we can eliminate multiple intermediate components.

    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  ·  Activity Feed  ·  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. 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)
  8. Push Logs to AWS S3 bucket: Terraform

    Push Logs to AWS S3 bucket, This feature is helpful, It gives a flexibility for large organizations who need to segregate logs considering Inventory, Security and Observability to organize logs to a respective destinations from S3.However the terraform provider does have api's to fulfill this feature https://www.mongodb.com/docs/atlas/push-logs/ . If it can available in terms of terraform resources, This will help our organization to enable logging in terraform IAC to simplify the logging and deployments

    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)

    Hi Jai, thanks for sharing feedback. This item is already under development and should be published to Terraform Registry over next few weeks! 

  9. Allow to change defaultWriteConcernSource to global to avoid flipping the flag

    Customers experience following error messages due to the defaultWriteConcernSource mismatch between the source and target cluster when restore the snapshot.

    Error: Can not restore a snapshot with custom default write concern 1 to a cluster that does not have a custom default write concern.

    Error: Can not restore a snapshot with custom default write concern majority to a cluster that does not have a custom default write concern.

    Ability to directly change the defaultWriteConcernSource without flipping between w:1 and w:majority will be convenient for the users.

    Option location:

    Cluster > configuration > Additional Settings >
    More Configuration Options > Default…

    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  ·  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. 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)
  11. BI connector host name via API call

    BI connector hostnames in the Atlas UI: https://www.mongodb.com/docs/atlas/bi-connection/ is not supported via API , Currently, customer has to manually copy and store the values to be reused by other applications. The customers are hoping to get these values in an automated way, for example with API calls or SDK.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. View all documents in a collection on Atlas UI

    The current limitation in Atlas restricts viewing documents within collections to a maximum of 200 per view. It would be beneficial to have the functionality to scroll through all documents without encountering the message: "To view additional results, connect to your cluster using the mongo shell."

    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  ·  Data Explorer  ·  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. Make IP linking easy for Atlas customers deployed on Google Cloud

    I know it may not seem MongoDB's responsibility, but understanding how to get IP addresses for my Google app engine services so that I can put them in MongoDB (which for some reason wants IP addresses instead of URLs) it's difficult. If MongoDB wants to sell to Google Cloud customers they should make it easy to set up, not only for the billing.

    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)
  14. Atlas raise alerts if resource consumption hits threshold notifications only when it's already scales up to the max tier

    Atlas can be configured to raise alerts if resource consumption hits threshold only when the Atlas cluster already scales up to the max tier allowed. This can be help to avoid notification spams which does not require operation team actions and focus on the critical resource consumption alerts like cpu, memory, disk IO.

    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

    1 comment  ·  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)
  15. Better auditing of App Service actions in Activity Feed

    The Activity Feed should show who has created an app in the App Services. Currently this is not the case, instead you will find the following information in the Activity Feed:

    A user(or Code Deployment) has deployed changes successfully to an App Service.

    3 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Use kubernetes Atlas operator to create and manage only users

    We are already managing the Atlas project using terraform and do not want to have two separate tools managing the same resource. We would still like to generate atlas users automatically through the operator. If there was a method of just providing the project ID as a string like we are able to in the terraform resource definition, this would not be a problem.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We're planning an investigation into this in Q2 (May-July for us). It's something more than one customer has asked for and allowing an Atlas ID to be used rather than a reference for another K8s resource feels like a reasonable approach. 


    No commitments for now till we've investigated in a little more detail. 

  17. There is no way I can delete my account.

    There is no way I can delete my account. It says I have to get rid of active organizations. When I try to get rid of my organization it says I have to get rid of my active clusters. When I try to get rid of my clusters. In clusters page it says I have no clusters.
    I tried to sign out and wait but the same problem continues.

    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)
  18. 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)
  19. 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)
  20. Define the secret name for the connection string output from the operator

    Hello all, instead of using a predictable naming convention for secrets:

    $project-$cluster-$username

    I'd like to be able to nominate the output secret name similar to how crossplane does this.

    More details found at the Github Issue: https://github.com/mongodb/mongodb-atlas-kubernetes/issues/1369

    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