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. Add an option to include sample data during cluster build

    When working through tutorials or University courses, often you need to build a new cluster and then add sample data to it. It would be nice if you could just check a box in the cluster creation page to have the cluster brought up with sample data already provisioned, thus combining two commonly used steps, into one.

    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. Make the app_id optional in the mongodbatlas_event_trigger resource when an aws_eventbridge event processor is defined

    Currently, when you define a trigger that uses the AWS Eventbridge via the UI it auto creates a realm App that links the DB change to the event bridge.

    However, with the mongodbatlaseventtrigger resource you have to manually defined an empty realm app and give the resource the app_id of that empty app.

    This is obviously not a 100% automated process.

    This could be, if the provider created the empty realm app by itself, then referencing the created app app_id.

    This would only be needed:
    1. when the appid is not provided
    2. the following attribute was

    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. prometheus integration to use PrivateLink

    There is a possibility to integrate Prometheus into an Atlas project.
    However, for enabling this integration, one needs to add Prometheus's IP address in the IP Access List.
    This procedure has 2 flaws in it:
    1. Prometheus runs as pods on some use-cases, meaning that its IP is ephemeral.
    2. For projects that work solely with PrivateLink enabled and no open IP in the IP Access List, one cannot use the Prometheus integration (already talked with support about that).

    The improvement here is to add the Prometheus integration to work as well in "PrivateLink-only" mode.

    74 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. Authentication Process Improvement

    At the time for user login authentication VDI user authentication is not done properly. Not able to fetch the system details. Need improve in that section--- For example--->" You're receiving this message because of a successful sign-in from a device that we didn’t recognize. If you believe that this sign-in is suspicious, please reset your password immediately. "

    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)
  5. Enable and disable balancing on a collection

    Shell commands sh.enableBalancing() and sh.disableBalancing() were not permitted on Atlas hosted MongoDB. Is it possible to grant this permission?
    Currently it failed with error:

    uncaught exception: Error: command failed: {
    "ok" : 0,
    "errmsg" : "not authorized on config to execute command { update: \"collections\", ordered: true, writeConcern: { w: \"majority\", wtimeout: 60000.0 }, lsid: { id: UUID(\"ed83ed26-e07b-4f34-a90a-a145bbe58a48\") }, $clusterTime: { clusterTime: Timestamp(1646788928, 17), signature: { hash: BinData(0, 347249E35ED43BDADAE12FB0F794C091CB86206E), keyId: 7052082196881866761 } }, $db: \"config\" }",
    "code" : 13,
    "codeName" : "Unauthorized",
    "operationTime" : Timestamp(1646788928, 18),
    "$clusterTime" : {
    "clusterTime" : Timestamp(1646788928, 18),
    "signature" : {
    "hash" : BinData(0,"NHJJ417UO9ra4S+w95TAkcuGIG4="),
    "keyId"

    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)
  6. AWS multi-region key (CMK)

    While using AWS multi-region key, if a customer selects a new region for their CMK, Atlas will trigger a key rotation process which could take some time to complete depending on the disk usage. Can we introduce native support for AWS multi-region key so Atlas does not have to re-encrypt data if CMK ID is the same in the new region.

    https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html

    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

    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)
  7. Compare and sync data across clusters

    I would like to have the ability to compare and sync collections across different clusters. The use case would be to support data migration between different environments.

    Like this feature from Studio3T
    https://studio3t.com/knowledge-base/articles/compare-mongodb-collections/?utm_source=post&utm_medium=fb&utm_campaign=3tslpage

    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)
  8. Mongo DB alerts for latest version or release

    Automatic alerts from Mongo DB Team for the latest releases / versions available similar to the EOL(End of Life) alerts.
    This helps in planning the changes and upgrades reducing the manual effort on searching for latest versions.

    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

    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)
  9. AWS Graviton2

    Hello,

    in 2020 AWS announced the Graviton2 Processor for EC2 servers. Do you support that architecture? If you don't, Do you have any plan for this?

    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)
  10. Add specific database API Metrics for MongoDB Atlas.

    A while back we ran into an issue where we ran out of connections in MongoDB Atlas. It took quite a while to determine which database was being overrun with bad connections. It would be very nice if the API, which we use to pull metrics into another monitoring platform, allowed us to get certain metrics at the database level instead of the overall system level. The metrics I am suggesting are
    Active Connections
    Response Time
    Failed Connections
    Number of requests
    Operation Execution Time

    These would help us more quickly discover the source of the problem and trace it back…

    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)
  11. Allow OpLog Backups in Atlas M0-M5 Shared-Tier clusters running on MongoDB v.5.x

    I have a backup process that is taking hourly dumps of the oplog on my production cluster running MongoDB v.5.0.6.

    It works fine using older versions of mongodump. However, when I update my tools to any version higher than 100.3.1 (100.4.x and above), my oplog backups fail with the following error:

    CMD : 2022-02-16T15:39:03.186-0500  Failed: error creating intents to dump: error counting local.oplog.rs: (Location40602) $collStats is only valid as the first stage in a pipeline.
    

    According to Atlas Support, this issue is limited to M0-M5 clusters and will need to be addressed by the Atlas development team.

    Can I ask…

    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)
  12. Last Database User Access

    My team has found ourselves in the position of needing to iterate through the Database Access History Logs in order to discover whether or not a database user is still being used for the past t time periods.

    We need to have this functionality in order to guarantee a seamless credential rotation.

    With the current API this operation will require iterating over each cluster's access logs for the past t time periods. If I have "n" clusters and "t" time periods this is an O(n * t) runtime. I'm not really great at O() notation, but if t is greater…

    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)
  13. Control IP Access list for project-only API keys at the project-level exclusively

    When setting up API keys as a project owner, you only get one opportunity to manage the access list without getting an Organization Owner to modify it thereafter.

    This creates a bottleneck where users need to ask for their API key access list to get changed (or alternatively make a new keypair, and have the API Keys list cluttered).

    If a key is only being used in one project, it should be allowed by the project owner to update the access list at any time since there is no risk of it affecting the organization.

    19 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)
  14. Deploy Custom Role to specific clusters only.

    You added the ability to deploy users to specific clusters. Great but you forgot to do it for the "custom roles". We use the "custom role" with LDAPS so we do not create a user on Atlas.

    https://feedback.mongodb.com/forums/924145-atlas/suggestions/38819875-ability-to-create-database-users-limited-to-specif

    Can you extend this functionality to "custom role" also %

    13 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)
  15. Database Audits information

    Add information to event source audit logs.

    For example, I add in the Atlas portal a new user with access to databases.

    When I download the cluster level audit file, I only find the information that the user was added by "mms automation", I don't have any information on which user or API Key was used for create this new database user. It is therefore very difficult for the monitoring team to verify if the user was created by an authorized user or API Key.

    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)
  16. Create Atlas UI Triggers Programatically

    Currently, a trigger which gets displayed on the Atlas UI (under Data Services > Triggers) cannot be created programmatically, they may only be created by clicking through the Atlas UI.

    The triggers created from the Atlas UI automatically creates a new realm app named "TriggersRealmApp" even when a realm app with the same name already exists. There is no way to have any of the triggers created under any other realm app displayed in the Atlas UI. The only way is to create them under the auto generated "TriggersRealmApp" which gets created after the first trigger from the…

    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)
  17. How to configure an alert to trigger based on a specific query executing longer than, for example, 1 second.

    If query is running more than X sec an alert to trigger based on a specific query executing longer than, for example, 1 second.

    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)
  18. Export & Import alerts

    It will be nice to have the ability to export a list of alerts from one project and import it in another 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

    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)
  19. Add per-user connection limit

    To prevent one user/application from exhausting available connections it would be extremely helpful to have the ability to set per-user connection limits.

    This connection limit would only prevent the specified user from connecting once their limit is reached and still allow other users to connect.

    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)
  20. Add Tailscale peering

    In lieu of doing 0.0.0.0/0 network access, it'd be great to peer into Tailscale so that anyone that is authorized in our organization's Tailscale VPN can connect effortlessly.

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

Feedback and Knowledge Base