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

1257 results found

  1. 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)
  2. 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)
  3. More granular user privileges for Database User in same project

    When having several clusters in the same project, it would be nice if we could configure different privileges to different clusters for the same user credentials.

    Like in the following example

    Name | Cluster1 | Cluster2 | Cluster3 | Cluster4
    User1 | R/W | R | R | R/W
    User2 | R | R/W | R | R

    Currently it's not possible to specify different privileges on the cluster level.

    8 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

    2 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)
  4. mute alerts during set times

    We would like to be able to set a time frame for when an alert can be triggered.

    Our use case is that some devs schedule high impact queries to run at night. If the rule is triggered at night, then we don't care, but if it's triggered during the day, it's something we look at and fix.

    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  ·  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)
  5. Persist setProfilingLevel Setting in Atlas

    Currently the profiling level resets to 0 every time the mongod process restarts. You can persist this with a self-hosted mongo by editing operationProfiling.mode in the conf file, but this is not possible in Atlas.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Need network whitelisting of API key for CI and Terraform

    Hi great Mongo people.

    The API key under organizational settings operates under a whitelisting model. There is currently no way (I can see) to open the key to 0.0.0.0/0.

    But in use cases where you make calls to Atlas to manage infrastructure through Terraform (like I do) and use a CI SAAS tool like Gitlab (like I do) that is built on a cloud (like GCP) there is an insane amount of whitelisting that is required. Also, about every 3rd run I have to come in and add another white list IP so that my Terraform can run.

    Could you…

    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)
  7. Support Linode as a cloud service

    Linode is a widely used cloud provider between developers that do not like the outrageous interface & costs of the main providers (Google, Atlas, AWS). Linode has free in-network bandwidth as well, making for private connections to be much cheaper.

    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

    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. Data Explorer pagination or seperate tab for name spaces

    Right now the data Explorer renders all collections and this often results in time outs for very big deployments. To make the UI usable I propose that the side bar with all the collections be a seperate tab, paginated server side or otherwise. Thank you

    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)
  9. when making backups don't have the banner say "deploying your changes"

    I was very confused recently when I logged in and saw the message "We are deploying your changes" despite nobody having made any changes to the cluster. Apparently what was happening was our scheduled backup was happening. This was a really confusing message to be seeing and resulted in a support request to work out what changes were being made.

    It would be much better if the message when a scheduled backup was happening was more clear about what is happening and less misleading.

    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. selected option scroll disappear on click to scroll

    In Atlas within Insert Document: When using the data type selection, clicking on the scroll bar or arrow causes the select option to disappear. Possibly increasing the size of the select option depth to where scroll is not needed may help.

    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)
  11. Deletion Protection

    Customer suggested protection from Cluster deletion similar to AWS RDS

    https://www.amazonaws.cn/en/new/2018/amazon-rds-now-provides-database-deletion-protection/

    TL;DR - a notification when a user tries to delete a cluster, that "this cluster is protected, if you need to delete please visit the console to enable deletion"

    This would be a critical piece of functionality where roles/permissions are not sufficient.

    6 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)
  12. Use existing main Integrations Slack key for all alerts automatically

    When updating the main Integrations Slack key, the token changes is not automatically deployed to the mongo alerts created earlier (slack notification). This feature would be helpful as at this time we have to update manually all alerts configured with a new token.

    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

    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)
  13. Refresh button like "Contact Team" button

    There should be a refresh button like the "Contact Team" button on the bottom righthand corner in the "database" section, so that users don't always need to scroll up and down, just to update their schemas

    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)
  14. Encryption at rest with our own keys - Manage alert and shutdown parameters

    It would be interesting to improve the encryption at rest feature in order to be able to define the alert parameters in case of unavailability of the key as well as the delay before a Replica Set fails.

    for example. I want to be alerted if my key is not available x times in the last 10 minutes and stop the replica game after 60 minutes if the situation is not resolved. This makes it possible for the support team to take corrective action without causing downtime.

    8 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

    3 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)
  15. Atlas should allow deployments of non-voting members on region for tiebreaking purposes

    No allowing non-voting members criples the ability to combine regional failover, while keeping the application servers in just two regions, where the event of having a third region primary may imply high latencies, that impacts SLOs.

    This particular severe for architectures that rely on 2 main datacenters (regions) and use a 3rd for tiebreaking purposes only.

    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

    2 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. Applying an index suggestion should remove redundant indices automatically

    An index suggestion for a compound index should check if it makes an existing index redundant. If so, it should remove it automatically after adding the compound index, or at least add the option to do so.

    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)
  17. Ability to read the logs in old format

    there should be option to download log files as native format, as we need to download multiple tools to get it to normal!!

    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)
  18. Feature Request: DNS record per zone for global cluster

    Today Atlas creates a single DNS record for the global cluster which has SRV records pointing to all servers in the cluster across all zones.

    This causes issues when a service hosted in US tries to use this DNS record as it now connects to every server in the SRV list of the DNS record. We ideally would want the US service to connect to its closest mongos router (US zone) and not all the mongos routers as it is unnecessary waste of resources. Our workaround today is to manually pick the servers and build the connection string in old…

    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

    2 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. Add an alert or notification option for every "pause" or "resume" cluster action

    Add an alert or notification option for every "pause" or "resume" cluster action

    9 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  ·  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)
  20. Change Display name for clusters

    Ability to change display name for clusters.

    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