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. Show hardware stats like CPU, System Memory in Metrics single-node view

    Currently, some hardware metrics charts like Normalized System CPU are only available in Metrics when viewing the replica set (multiple nodes).

    But if you click on one node to see metrics for that server alone, the hardware metrics do not appear in the available charts.

    This is confusing -- it'd be helpful if the same metrics plots, including hardware metrics, were shown in all Metrics views.

    It's possible to remove some nodes from the "replica set" view by unchecking them in the Toggle Members boxes at the top of the screen, but that will now allow you to view charts…

    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 →
  2. take snapshots off of the activity tab for maintenance.

    When I select the maintenance filter on the activity feed all the daily snapshots show up. I feel like there should be a backup screen that shows all the snapshots on the activity feed. this would make the maintenance screen more precise and relevant.

    . The maintenance screen should only show what software maintenance goes on the atlas clusters. This should also include all the release fixes. so, I do not have to go to your
    https://docs.mongodb.com/manual/release-notes/software releases page.

    It is very hard to tell what maintenance will be applied in a given time period. We have timeframes to apply…

    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  ·  Flag idea as inappropriate…  ·  Admin →
  3. ignore notimeout cursor (after initial warning?) to avoid breaking compatibility with apps

    In Q4 2020, the notimeout cursor was no longer allowed on free or shared instances.

    As several DB management tools hardcoded this option for optimum performance it breaks compatibility with them. We use a combination of free/shared-tier instances for dev in combination with dedicated instances for production; this limit effectively means we either have to WAY overprovision our dev resources, or we can't use our tooling anymore on it.

    Please provide a way to simply ignore the notimeout option, instead of breaking its connection.

    Thanks!

    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 →
  4. Don't cut alert names

    This is very hard to figure out what these alert mean, I have to go to the documentation and match them somehow, but it also looks like the documentation is not up to date.

    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 →
  5. Atlas Capacity Check for Cluster Creation or Changes

    When creating large new clusters sometimes Atlas does not have enough resources available from the cloud provider. When this happens a restore or cluster change fails without reporting what the actual issue is.

    Solution: Verify available capacity and issue a warning or error if it is possible that the operation will fail & recommend opening a support ticket (or have a dialog to automatically do so listing the details)

    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 →
  6. Scaling cluster connections independent of cluster size/tier

    Currently whenever you want to increase Atlas cluster connections, you have to scale up Cluster Tiers. When an application doesn't require additional disk storage but only additional connections the additional cost is difficult to justify.

    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  ·  Autoscaling  ·  Flag idea as inappropriate…  ·  Admin →
  7. SNMP

    Enable SNMP setup on Atlas Resources.

    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 →
  8. Kotlin support and Tutorials

    Add Tutorials and Native support for Kotlin language. Preferable with ktor as the server

    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  ·  Tutorials/How-tos  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow db.killOp() and manual restarts on secondaries

    Please allow us to kill user threads on Mongo secondaries. Sometimes we have long running queries on secondaries and need to kill those threads but can't do anything about it since we don't have admin privileges to kill threads.
    Also please add the ability to manually restart secondaries, not just failover the primary.

    Thanks.

    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 →
  10. Allow to set billing alerts per project

    I have different projects where I expect and calculate with different costs. I would like to set billing alerts per project, for example if an internal evaluation projects execeeds a specific biling the threshold is probably lower then for a production project.

    Similar to the currenty billing alerts, I would to set a billing alert, but either per project or with different thresholds for each project.

    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  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  11. More simple scheduled aggregations

    When we set up an aggregation in Aggregation Pipeline Builder, we can "Export pipeline to languages"..
    I think it would be great to be able to export complete, copy-paste-ready code as a function to be triggered in Atlas Triggers, as a Function, eg. on schedule,
    or any other simple way (no-code / low-code) to run aggregations on schedule.

    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 →
  12. Add MFA status to the API

    A field indicating whether MFA is on for organization users (i.e. on https://docs.atlas.mongodb.com/reference/api/organization-users-get-all-users) would be extremely useful!

    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. MongoDB Orphaned Docs Utility

    When we upgrade MongoDB there is the possibility that orphaned collections that need to be deleted can prevent the upgrade from completing.

    It would make sense for Atlas to include a proactive utility that searched a customers sharded cluster for orphaned docs and gave them the option to clean up the orphaned docs ahead of a major version upgrade.

    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 →
  14. IO throttling

    Atlas should be able to throttle IO in a way that does not allow excessive IO to degrade a node or take a node offline. Current functionality has no defense against a high IO data job other than to allow a node to fail.

    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 →
  15. Domain Validation should use subdomain rather than domain root

    When entering the txt value for validation atlas should use its own subdomain for the verification rather than requiring the domain root which is often populated with spf keys.

    Other examples of this implementation are

    Github: github-challenge-org.domain.com
    Mandrill: mandrill.
    domainkey.domain.com
    Google: google._domainkey.domain.com

    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  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  16. Display the MongoDB Network Peering Container ID in the console

    Instead of forcing use of the API, why not display the MongoDB Network Peering Container ID for the peering connection in use?

    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  ·  Flag idea as inappropriate…  ·  Admin →
  17. Governance rules at the organization level

    Hello team,

    Would it be possible to be able to set up governance rules at the organization level in order to control certain configuration elements.

    For example:
    Control authorized providers and regions for an organization to prevent creation of cluster in unauthorized regions. (We must keep the data in Canada for some of our databases)

    Check the allowed IP (IP Access List) addresses

    Disable the use of SCRAMS accounts for database access.

    Control the "Data Explorer" functionality at the organization level to prevent its activation at the project level.

    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 →
  18. Redirection of ATLAS activity feed to a MongoDB cluster that we own.

    Hello team,

    Would it be possible to have a feature to redirect activity logs from ATLAS to a MongoDB cluster.

    The idea is to be able to easily retrieve these logs with Kafka Connect and also to be able to easily query in these logs.

    One could configure the redirection of activities at the organization and projects level by providing the Atlas cluster to use and the access accounts.

    Example:
    Main organization
    - Project: "Activity Feed"
    - - Cluster: "Activity Feed Cluster"
    - - DB: "Atlas Activities by organization"
    - - - Collection: "Activities by project"

    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 →
  19. Atlas Shard Management

    Currently the Atlas UI only presents options for how many shards a cluster can have.

    Putting in a suggestion to perhaps allow similar functionality / features to Cloud Manager's shard management as shown : https://docs.cloudmanager.mongodb.com/tutorial/manage-data-sharding/#manage-sharded-collections

    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 →
  20. Support for delayed replicas

    It would be great if Atlas provided support for hidden, priority 0 delayed replicas. For workloads that do not need real time data or situations where data recovery is needed, a delayed replica would be the fastest way to mitigate both of those scenarios.

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

Feedback and Knowledge Base