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

1078 results found

  1. Google Private Service Connect

    Greeting from Fivetran!

    This is somewhat related to https://feedback.mongodb.com/forums/924145-atlas/suggestions/45272014-allow-customers-to-specify-the-number-of-service-a . Having 50 service attachments is not scalable for us which requires 50 IP addresses for each PSC. We have a large customer base and having each of them create PSC would require a lot of IP addresses and would quickly exhaust our subnets.

    From the support case it seems that the decision to use 50 PSC attachments comes from the fact that GCP load balancer does not allow more than one pool of servers per service attachment and that the ports are passed through as is as opposed 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)
  2. Add v1.5 API support to Terraform to support asymmetric hardware

    We use a base tier MongoDB cluster (M20) and an analytics tier (M30), where they are of different sizes due to different business requirements.

    Currently this is not supported by Terraform unless tiers use the same hardware (e.g. either both are set to M20 or M30).

    See the error message below.

    Error: error reading MongoDB Cluster (development): GET https://cloud.mongodb.com/api/atlas/v1.0/groups/1234567890/clusters/development: 400 (request "ASYMMETRICHARDWAREINVALID") Asymmetric hardware is not supported by the v1.0 API. Please use the v1.5 API instead. Documentation for the v1.5 API is available at https://docs.atlas.mongodb.com/reference/api/clusters-advanced/.

    Please add v1.5 API support to Terraform to support asymmetric hardware.

    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. Select exclusive copy snapshot from different region to restore for testing DR from copy snapshot.

    We have "Additional backup policy" feature enabled which will copy our snapshot to other region.As part of DR testing we want to exlusively select copy snapshot in other region to restore to perform DR.In the current cluster I don't see an option specifically to select snapshot from other region.

    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)
  4. Ability to quickly filter backup activity from the project activity feed

    The activity feed is often clogged with backup activities. It would be extremely useful to be able to quickly filter out the common 4 or 5 project activities that are related to a backup snapshot being taken.

    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)
  5. Improve the sample code for Connecting with MongoDB Driver

    When in Atlas you click the Connect button and get to the screen 'Connecting with MongoDB Driver', the Java sample isn't using the MongoClientSettings.builder() to set writeConcern and retryWrites. This is done in the connect string instead, even though the builder does provide those two settings.
    I suggest only using the MongoClientSettings.builder() for better type safety.

    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)
  6. Display "N/A" instead of "0" for doc count in timeseries collection in Compass

    In Compass 1.36.4, when I look at a database that has a time-series collection in it, in its list of collections, it displays the collection as having "Documents: 0" and "Avg. document size: 0", even when there are some documents in it.

    I think that's misleading. As I understand it, time-series collections do not support the estimated document count functionality that is used to populate these fields in the Compass GUI. That being the case, it might be better to display "n/a" or a blank in those fields, instead of a 0 which is not the correct value. A user…

    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. Pull Project Audit Logs

    Our requirement is to feed these audit logs in to a central system, which will help us report on elevated or unauthorized changes to the Database services.

    Currently, the only way to pull these logs through the API is to pull each file from each node within a cluster as a .gz file. (https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Monitoring-and-Logs/operation/downloadHostLogs)

    What we’d like to request is a way to pull the Project (or cluster) audit logs that acts like the Events API endpoint, where it is a paged list of Events that have occurred for a project. (https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Events/operation/listProjectEvents)

    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. Restrict whitelist ip

    I would like there to be an option to restrict users to what they can whitelist in network settings for a project. I want there to be option like "only users with owner access can create non-temporary IP whitelistings" so we can avoid having our developers adding IP addresses that gets outdated and pose a potential security risk.

    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)
  9. Remove the requirement to have an API Access List CIDR before being able to manage backup schedules

    The issue is described in this github issue, specifically in the linked comment: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/222#issuecomment-855905952

    Here is the requirement as described in the API docs: Remove All Cloud Backup Schedules
    Removes all cloud backup schedules for the specified cluster. "This schedule defines when MongoDB Cloud takes scheduled snapshots and how long it stores those snapshots. To use this resource, the requesting API Key must have the Project Atlas Admin role and an entry for the project access list."
    https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Cloud-Backups/operation/deleteAllBackupSchedules

    Our request is that the requirement to have an API Access List to manage backup policies be removed.

    At the very least,…

    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  ·  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. Integrated/unique metrics vision for primary replica-set

    It is really hard to understand the behaviour of primary replica-set on bigger timeframes, when it was switched some times. Would be very helpful to be able to see the metrics in a integrated chart, to understand consequences of some actions like application changes, index creations, version upgrades, etc.

    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)
  11. Alerts for Atlas Limits

    It would really help to get alerts on Atlas Limits (https://www.mongodb.com/docs/atlas/reference/atlas-limits/). Defining certain thresholds that would trigger an Alert as hitting these limits often involves work to re-structure something or creating a workaround. E.g. it is not possible to have more than 50 Endpoints per Project. But creating a new project is not a straightforward exercise. If the alert had occurred earlier there would have been more time to account for this.

    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)
  12. Granular cost and inventory details

    We are building a unified portal to view our databases and almost all other managed cloud providers like AWS provide instance level/node level view of clusters.
    Currently, there's no way for me to get instance level/node level inventory details.

    Also, when billing/cost is generated, it's generated on a cluster-level basis. Since we now have separate sizing for Analytical nodes and Electable nodes, it's better to separate out the cost to be at an instance level.

    Again, all cloud providers like AWS do give us instance-level costing for EC2/RDS so I don't see why that can't be technically possible.
    Support costs…

    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  ·  Billing  ·  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. Add the ability to configure the auto-resume setting for triggers through terraform

    Currently MongoDB triggers can be created through the TF, but to enabled the auto-resume setting this needs to be manually done through the Atlas UI. This should be an option on the "mongodbatlaseventtrigger" TF resource, so it can be all configured together.

    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. API to list clusters that has snapshots on it- even deleted clusters

    Today we use the API below to list the clusters that exists in a project

    https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Clusters/operation/listLegacyClusters

    GET https://cloud.mongodb.com/api/atlas/v1.0/groups/{GROUP-ID}/clusters?pretty=true

    After having the clusters list, we can list the snapshots from one specific clusters using the API:

    https://www.mongodb.com/docs/atlas/reference/api/cloud-backup/backup/get-all-backups/

    GET https://cloud.mongodb.com/api/atlas/v1.0/groups/{GROUP-ID}/clusters/{CLUSTER-NAME}/backup/snapshots

    Now on Mongo Atlas I can delete a cluster and ask not to delete their snapshots. So if I want to use the same functions I can't, because the list of the clusters do not show the clusters that have been deleted but still has snapshots on atlas.

    It would be great if the API that lists the cluster also give us…

    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  ·  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)
  15. Allow multiregion sharded clusters to have Primary nodes in multiple regions

    For multi-region sharded clusters, the primaries for each shard remain in a single (highest priority) region in Atlas. If these primaries can be spread across multiple regions, that will a) provide consistent average response time for applications that connect from multiple regions as active-active b) Limit the blast radius if the highest priority region is unavailable c) Better distribution of workload from an application side.

    This architecture is currently possible with EA deployments but not with Atlas.

    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

    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)
  16. Integration with Percona Monitoring & Management

    Please release Integration to Percona Monitoring & Management. 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  ·  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)
  17. Please let users know you will be making huge charges for no services provided!

    Please let know users that Atlas will generate huge charges for NO usage and will be hit with huge bills without having even used your service. Also, please let users know that MongoDB will not build or compile on Raspberry Pi either Ubuntu or Debian!

    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  ·  Billing  ·  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. AtlasBasic CDK

    AtlasBasic CDK should include an option to create to serverless cluster as opposed to dedicated/shared.

    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)
  19. Support Ticket subject lines

    MongoDB Support to have nicer subject lines for the notification emails sent out by the MongoDB Support Portal.

    There's nothing distinguishing except a case number (which mean nothing), and it’s hard for me to differentiate or even show up in local searches. Going to an external ticket tracking system is a bit of a hassle, and won’t be integrated with any of our local search or content management stuff.

    It would be good to have it headed with what my case is about.

    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. Restore protection similar to termination protection

    A restore protection option similar to the termination protection for clusters.
    When a cluster has restore protection enabled, it can't be the target cluster for a restore operation. This will prevent accidental restores to the wrong target cluster from affecting the protected cluster.

    The motivation is preventing mishaps from affecting critical production clusters.
    The UI for selecting the target cluster of a restore operation has you select the cluster from a dropdown and then type in "I Agree". That still leaves you open to mistakenly select the wrong cluster if you aren't paying good enough attention.
    The restore protection feature…

    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)
← Previous 1 3 4 5 53 54
  • Don't see your idea?

Feedback and Knowledge Base