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

1181 results found

  1. Allow multiple VPC CIDR ranges in Peering connection

    Allow multiple VPC CIDR for a single Peering connection from Atlas to AWS.

    Our AWS account has two CIDR ranges for a single VPC. Atlas peering connection only allows connection to a single CIDR range.
    Today, I need to create a separate private link connection to be able to connect to the second CIDR range.

    18 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

    4 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)
  2. Support Dynatrace integration for monitoring with Atlas

    This is a request to support an integration with Dynatrace for monitoring MongoDB deployments in Atlas.

    18 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. Atlas Cluster Labels in UI

    With the Atlas API, there is functionality to add labels to various clusters like EC2. It would be great if that was exposed through the Atlas UI as well.

    18 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)
  4. Carbon Footprint Calculator

    A widget or calculator in the Atlas UI, where the user can see the projected carbon footprint of a deployment per year while they are configuring the deployment. And / or a live counter of the carbon Footprint for each deployment/project/org.

    17 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  ·  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)
  5. Send Alert when IP access list changes

    Customer is requesting that an alert be sent out if project IP access list gets changed

    17 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. Show max IOPS line on IOPS graphs

    When monitoring disk IOPS, it isn't immediately clear when we are limited on IOPS. Having a red limit line on the IOPS chart on the metrics tab would help here.

    17 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)
  7. Allow cluster to define priority of availability zones

    Similar to how it's possible to select the preferred region in a multi-region cluster, it would be beneficial being able to select the preferred availability zone in a single-region cluster. This would allow an application to live as close to the cluster's PRIMARY node as is possible.

    17 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

    5 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. add details to alert Query Targeting: Scanned / Returned to identify what triggered it

    If you want to catch full scan on collection you could set up alert "Query Targeting: Scanned / Returned > 1".
    OPS Manager does not provide any details where it was triggered.
    it would be nice to get db/collection/query which caused this issue. Query still can be fast (for example, not many document in collection yet or hardware is idle/fast at the moment) and will not go to slow operation group.

    17 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)
  9. Share API key cross organizations

    Today, it's not possible to share an API key between different organizations (https://www.mongodb.com/community/forums/t/sharing-api-key-between-different-organizations/190785/13)
    It makes it impossible to restore snapshots from one organization to another automatically.

    It's very important for us, as we need this feature to clone our customers clusters into our organization

    16 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)
  10. Restrict specific users or client IPs to only Analytics node(s)

    There are use-cases where certain users or client IPs need to be given access restricted to only the Analytics node(s) . While it is possible to grant such users read-only permissions at the database/collection level, and have them use the ANALYTICS replica set tag in their connection string URI, it might still be possible for those users to connect to a Primary or a Secondary node (when not using the Analytics replica set tag) and run their query there.

    Therefore, a feature that will either restrict specific users access to only the Analytics node(s) or a functionality that will restrict…

    16 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  ·  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. Set schedules for pausing clusters

    It could be incredibly helpful if we had a way to set a schedule to pause any given cluster as well as a schedule to un-pause it. This would help with cost savings and would allow to shutdown development clusters on weekends, after hours and holidays.

    16 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  ·  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. Allow custom date range to be submitted in Query Profiler

    Currently the Query Profiler can plot queries that were logged up to 24 hours in the past.

    It would be helpful to allow for visualization of a custom date range older than 24 hours ago, rather than only queries logged within the past 24 hours. This could help with RCAs for events that occurred more than 1 day ago, and also help teams who collaborate to investigate queries over a time period longer than 1 day.

    16 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)
  13. Expose the killOp() action when creating custom roles in Atlas UI

    It would be nice to have the killOp() action exposed when creating a custom role in Atlas.

    I also think it would make sense to grant this action to the atlasAdmin role, but at a minimum I feel that Project Owners should be able to create a custom role that is allowed to kill ops that were initiated by other database users.

    16 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  ·  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)
  14. Log user Login to Activity Feed for Auditing

    When a user logins into the Atlas Portal this is logged to the Activity Feed.

    This feature would allow to better user auditing and identify potential security breaches.

    16 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)
  15. Allow Pending Users to be Added to a Team

    When trying to implement Atlas infrastructure for Organization/Project users, the Teams functionality is useless unless we can add pending users to a Team. Right now, if a new user doesn't login for two weeks, we can't assign them to a Team until two weeks after the implementation was supposed to be configured.

    16 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  ·  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)
  16. Prometheus database and collection metrics

    We checked the Prometheus metrics provided by MongoDB Atlas and didn't find metrics for the following:
    Database size

    Collection storage size

    Record per collection

    Indexes per collection

    Index size

    We would like to have this kind of metrics to add to dashboards.

    15 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)
  17. Pausing MongoDB Atlas Cluster with option of start/end time

    There is a parameter available for cluster resource to pause the cluster. With this parameter, we have to flip the status from pause to unpause whenever needed.

    I am looking for separate resource (like maintenance window) where one can configure to pause the cluster for specific window (start/end time)

    Example: I want to pause all non-prod clusters by Friday evening 5 PM EST and resume the cluster 7 AM EST. With trigger it is possible, but we do have hundreds of deployments. It would be great if we have resource where customer can specify their own timing to pause and…

    15 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)
  18. Allow the ability for a rolling cluster restart like during maintenance

    Currently there is no way to test how applications behave during maintenance apart from waiting for maintenance, the ability to force a rolling cluster restart as happens during maintenance would be great. The failover is a different process and affects primary mainly.

    15 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  ·  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. Atlas Endpoint Service "Description / Tag" Field

    Currently when creating an Atlas Endpoint Service, there is no way to add a "tag" or "description" to the endpoint.

    When a large number of endpoints are created, it because very challenging to identify which endpoint aligns with which customer service or application. Giving customers the ability to add "tag" or "description" metadata, would help give them better visibility into their configured endpoints.

    This is specifically requested by an Enterprise Atlas Customer - please reach out to me for details / specifics.

    15 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)
  20. Alerts Messaging Customization

    At the moment, it appears one cannot customize the messaging or subject line of the alerts. This makes it difficult to categorize the alerts. For instance, we would like to categorize alerts into different severity levels, such that severity level will help determine the level of attention that is paid to the alerts when they trigger. If it is possible to prefix or append some customization code and message to either the subject line and/or actual message, then a monitoring team can use the custom code/message to determine the severity or category of the alert when it triggers.
    Some alerts…

    15 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  ·  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)
  • Don't see your idea?

Feedback and Knowledge Base