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

455 results found

  1. Add hint support for MongoDB API functions

    The "hint" option for Mongo Shell query/write operations is very useful when the Query Planner does not select the right index by default, or just to make sure the right index is used. When you cannot use the "Hide index" feature on the index selected by default, "hint" becomes the only way to have an efficient IXSCAN.

    However, the "hint" feature does not exist on the MongoDB API functions (https://www.mongodb.com/docs/atlas/app-services/functions/mongodb/api/). This means that no command we can run inside a Trigger can specify a "hint" option.

    I think that "hint" is a great "backup" feature for cases where…

    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)
  2. Atlas shards with different clusters tiers

    For solutions of hot and cold storage, there is at least 2 options:
    - Online archiving
    - Hot and cold cluster (using a trigger and datalake)
    But these solutions have limitations (https://www.mongodb.com/docs/datalake/limitations/)

    There is another solution: using sharding.
    We can set shards like so:
    1 shard: Data from the last 2 months -> Hot data
    1 shard: Data between 2 and 24 months -> Warm data
    1 shard: Data more than 24 months -> Cold data

    The usage pattern: 95% of the accesses/queries go to shard with the hot data.
    On Atlas, we need to set the same…

    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)
  3. Allow access to Admin API using AWS IAM role

    It's possible to authenticate to a database using AWS IAM role. The same should be possible for the Admin API.

    The problem with the API keys is that they can be taken away and used elsewhere. They pose an additional risk in an AWS integrated environment.

    This also relates to upcoming Cloudformation Resources where the extension needs to store the API Key in AWS Secrets Manager. The resource already has a role that could simply be configured to be trusted on the Atlas side.

    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)
  4. Get all databases from one cluster

    Add a new Admin API to Atlas: Get all databases from one cluster

    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)
  5. Add option to "Explain" a query from the "Profiler" page.

    The profiler page shows a list of queries with metadata about them. It would be great to have the option to "explain" any query from this view, or in the slide-out view after clicking on a query.

    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)
  6. show the reason why you can't increase oplog

    in the settings=>additional settings=>More Configuration Options=>Set Oplog Size
    show the reason why you can't increase this parameter (let's say you have insufficient free space etc.)

    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)
  7. When Adding new CKM key/role Atlas should validate if it can safely change existing CKM key

    When we create new CKM key with new role and update credentials on project level, Atlas validates that new role can read new key. But it does not validate if new role can read existing CKM key.

    When Atlas starts re-encrypting existing cluster, first node goes down but can't be started because new role can't read old key. There is no way to restore/rollback this change unless raise a ticket for MongoDB support.

    Suggestion: when we upgrade credentials/role/KMS key in UI, Atlas should validate if it can finish this change BEFORE applying changes to nodes.

    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)
  8. Atlas UI enhancement

    Hi,

    Atlas UI is displaying "Database Deployments" earlier it used to be as cluster or clusters.

    1. When we hit the create button all it talks about "CLUSTERS > CREATE NEW CLUSTER"
    2. Right side top corner, we can also see it states "All Clusters"
    3. Terraform resources/attributes talks about Clusters
    4. Only place we see in the home page "Database Deployments"

    Our customers are getting confused with Database Deployments with Databases within the clusters. Customers are thinking they need to create more database (database deployments) if they want to have for their application, which is not true. They can create multiple database in…

    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)
  9. Download file button for GridFS on Atlas GUI

    When using the "Browse Collection" feature from the Atlas Web frontend it would be nice to be able to download/view files stored in GridFS. Tools like "Studio3T" or "NoSQLBooster for MongoDB" support that use case.

    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. Reshard Global Writes Collections

    MongoDB supports resharding, so not being able to change the global writes shard configuration is very strange. It makes it impossible to fix mistakes with the shard configuration. Even if it requires blocking to redo or remove the shard configuration it should be possible.

    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)
  11. Make Real Time Performance Panel, Data Explorer and Performance Advisor and Profiler GDPR compliant

    As the data used for Real Time Performance Panel, Data Explorer and Performance Advisor and Profiler are processed/routed in/over the USA european customers that need to be GDPR compliant can't activate those three options. Unfortunately these three features offer a great feature set which really hurts to not have. This is a high prio topic for us.

    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)
  12. Support migration between Atlas clusters using Atlas API

    Support live migration between Atlas Clusters through Atlas API. If we need to migrate, it'd be good to be able to do so through the API.

    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  ·  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)
  13. Add Atlas instance in Azure Sweden

    We host data that is preferred to reside in Sweden. Do you have plans to expand to the newly added Azure Sweden data centers?

    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  ·  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. Purge of unused accounts after X days/months

    After X number of days/months (say 12 months), accounts that haven't been accessed or have never been accessed go into a 3 month freeze period, before they are automatically disabled and deleted. A report of such accounts should be auto generated and archived. The freeze period intention sends a warning to the account holder as well as an alert to administrators of the atlas org.

    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)
  15. Prevent Federated Users to gain access to other Projects

    Hi,

    We have set Federated authication and RoleMapping to project. This roleMapping gives Project Owner Rights to a particular project. Project Owner have the right to invite other people into their project.

    Role mapping is only applied when a user logs in. However, if the user receives an invitation to a project when logged in (to say Project ***) and accepts an invitation (to say Project YYY, for which they should not have any access), they will receive the Atlas role in that project (Project YYY) designated by the invitation, allowing them to perform any actions provisioned by that role.

    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  ·  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. Migrate to new cluster without auto upgrade (5.1.0)

    Hi,
    Our clusters are in auto upgraded feature of MongoDB versions right now.

    We want to stop the auto upgrade feature for now and migrate our clusters to new one with the MongoDB version 5.1.0.

    But, when we try to create a new cluster it's not showing the option for version 5.1.0.
    And we need 5.1.0, because we're going to restore the data from the current cluster which is versioned 5.1.0.

    Your help is much appreciated.

    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  ·  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. Derisk cluster changes that cause restarts

    Problem statement:
    Some configuration changes cause rolling restarts of the cluster (e.g. audit filter, enabling x509 auth). It is not immediately obvious which changes will cause restarts and for a big cluster, this is a huge hit to performance due to cold caches.

    Ideas:
    1. Block planner changes which would cause restarts until maintenance window (maybe with an opt-in for this, + notification that the config change is blocked)
    2. Throttle replica set restarts, allowing time for the cache to be warmed on secondaries (would require mirrored reads in 4.4 to be effective)
    3. Properly document what changes will cause…

    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)
  18. Permit setting a default collation at the project level, to apply to all collections etc within the databases it contains.

    Currently the highest level that collation can be set is at collection creation, and it is inherited then for any indexes created on that collection and by commands like find() that run against it.

    But it would be nice to be able to specify a default collation at the database level, or even the Atlas Project level, to apply to all collections in all databases therein, howsoever created.

    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)
  19. 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

    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)
  20. Put some kind of connection string generator / link / text on the "Database Access" screen

    Hello!

    It took quite a while for me to find a template connection string for Atlas, as I only thought to check the "Database Access" screen. Eventually I found the "Connect" button the "Clusters" screen, but it was a pretty frustrating time looking for something as essential as a connection string.

    It would be great if you added something that would have prevented that-- a little widget where you pick your cluster and it spits out a template string. Or even just some text like "Looking for your connection string? Go to clusters, it's over there!"

    Thanks!

    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)
1 2 9 11 13 22 23
  • Don't see your idea?

Feedback and Knowledge Base