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
  1. Include cluster labels in the billing usage details

    Similar to how AWS includes tags/labels in their billing dashboard, I'd like the ability for my cluster labels to be included as a column in my billing usage details (or even the exported CSV).

    This will allow me to categorize my billing usage as granular as clusters in addition to the current method which is by project.

    7 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  ·  Billing  ·  Flag idea as inappropriate…  ·  Admin →
  2. Log Redaction for Atlas

    It would be good to see Log Redaction work in Atlas as well, similar to On Prem
    https://docs.mongodb.com/manual/administration/monitoring/#log-redaction

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow domain or URL for whitelisting

    Currently Atlas IP Access List entries allow to specify only either a single source IP addresses or ranges of IP addresses using CIDR notation. It would be great if user can add a domain or url for whitelisting where the IP address or range is not static.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  4. Export results of an aggregation query to csv file

    I have created an aggregation pipeline from the aggregation tab of a collection but unable to export the results of that query to a CSV file.

    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

    1 comment  ·  Data Explorer  ·  Flag idea as inappropriate…  ·  Admin →
  5. Seeing ports that Clusters listen to

    In your documentation and even through the atlas web api, there is no straightforward method to see what ports my clusters communicate on. This is highly frustrating as I am using the Mongodb Atlas Private endpoint and need to Allow Inbound/Outbound communications on certain ports for the endpoint to work.

    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

    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  6. Improve Cluster Name Limits

    Cluster names currently impose the following limits:


    • Cluster names shorter than 23 characters can't end with hyphen or dash (-)


    • Cluster names 23 characters or longer can't use a hyphen or dash (-) as its 23rd character.


    Instead, we should either trim or replace the hyphen at the end of a 23 character name.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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

    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  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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  ·  Integrations  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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

    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  ·  Flag idea as inappropriate…  ·  Admin →
  13. migration should check actual disk space used by source MongoDB

    The easy migration system seems to check the total disk space used on the source machine, and does not discriminate between that disk space used for MongoDB (which will be needed on Atlas) and those used for other applications.

    Because the source system contains a lot of logs and a complete copy of our databases in different folders, we have had to configure Atlas to use >2x the actual disk space it'll need.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  14. For resource mongodbatlas_cluster all properties related to provider move to separate block

    Current resource

    resource "mongodbatlas_cluster" "cluster" {
    
    project_id = var.project_id
    name = var.cluster_name
    disk_size_gb = var.disk_size_gb
    num_shards = var.num_shards
    replication_factor = var.replication_factor
    auto_scaling_disk_gb_enabled = var.auto_scaling_disk_gb_enabled
    mongo_db_major_version = var.mongo_db_major_version
    //Provider Settings "block"
    provider_name = var.provider_name
    provider_disk_iops = var.provider_disk_iops
    provider_volume_type = var.provider_volume_type
    provider_instance_size_name = var.provider_instance_size_name
    provider_region_name = var.provider_region_name
    provider_backup_enabled = var.provider_backup_enabled
    }

    Suggested resource

    resource "mongodbatlas_cluster" "cluster" {
    
    project_id = var.project_id
    name = var.cluster_name
    disk_size_gb = var.disk_size_gb
    num_shards = var.num_shards
    replication_factor = var.replication_factor
    auto_scaling_disk_gb_enabled = var.auto_scaling_disk_gb_enabled
    mongo_db_major_version = var.mongo_db_major_version
    //Provider Settings "block"
    cluster_provider = {
    name = var.provider_name
    disk_iops = var.provider_disk_iops
    volume_type = var.provider_volume_type
    instance_size_name = var.provider_instance_size_name
    region_name = var.provider_region_name
    backup_enabled = var.provider_backup_enabled
    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  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  15. Monitoring for WiredTiger data handles

    Add process measurements for monitoring WiredTiger data handles.

    From Atlas documentation https://docs.atlas.mongodb.com/reference/atlas-limits/#collection-and-index-limits :
    > While there is no hard limit on the number of collections in a single cluster, the performance of a cluster might degrade if it serves a large number of collections and indexes. Larger collections have a greater impact on performance.

    but now there is no way to get this information except db.serverStatus()

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow threshold on "System Memory: Available" alert condition to be a percentage

    In Atlas, it would be ideal if you could specify a percentage of total memory as the threshold for the "System Memory: Available Is..." rather than a literal number value. If it was possible to set this as a percentage, then the alert could be applied to all hosts in a project, rather than having to set hostname conditions and create a separate alert for each cluster.

    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

    2 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  17. support external nodes

    Allow manual addition of externally-hosted non-voting (hidden) node(s) to an Atlas cluster. This would permit:
    - compliance with data management rules that require a copy of all data to be kept in-house (ie outside cloud)
    - easier migration out of Atlas for real-time DB use cases where a stop/backup/restore is not a feasible route

    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  ·  Flag idea as inappropriate…  ·  Admin →
  18. Ability to block sending of Alert Close Notification

    We have set up alerts and have noticed that when a condition is back to normal, there is another alert generated acknowledging its closed. Is there a way we can manage this (like disable or block it for some alerts)?

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  19. Atlas auto-scaling configurable alerts

    It would be useful, and contribute to a complete alert experience, to have auto-scaling event alerts configurable in project alerts. Users should be able to send alerts to their target system of choice, and prevent numerous alerts to specific users.

    Currently auto-scaling alerts are only emails to project members (as per the following https://docs.atlas.mongodb.com/cluster-autoscaling/#acknowledge-auto-scaling-events).

    Examples of configurable alerts:
    - Scale-up unsuccessful due to max cluster-tier too low -> change email recipient of these alerts
    - Scale-up event has occurred -> send alert via SMS and Slack.

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  20. High resolution monitoring and alerting for WT dirty cache ratio, eviction workloads and checkpoints.

    Implement better monitoring and alerting for WT dirty cache ratio. This should include sub-minute resolution and support an understanding of eviction workload as well as performance impact of checkpoints under heavy write workloads.

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base