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

1362 results found

  1. LDAP Users shouldn't be successfully authenticated if not authorized

    Today, if you login with proper LDAP credentials to an Atlas cluster, you are authenticated into that cluster, even if you are not authorized to have access. This is not at all how databases should work, nor is it how most databases do work today. If a user is not authorized, that connection should fail immediately.

    Allowing successful authentication, even when not authorized, can increase the security vector for ddos attempts as well as causes confusion when successful attempts are logged, even though the user was not authorized to see data.

    Please reject any non-authorized user from connecting to an…

    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

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

    7 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  ·  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)
  3. add cluster manager email

    Hi,
    It would be nice to be able to assign a cluster manager email / contact per cluster and not per project. We have different team members managing different clusters within each of our projects and it would be great if we could alert them specifically on specific events in a cluster (like new index suggestions, disk increase, 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)
  4. Collection query audit logs

    It would be nice to be able to see what queries were run on which collection over the last x days.

    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)
  5. View Atlas user sign in method in logs or UI

    We'd like to see how are users are signing into Atlas.
    At the moment we can just see username, email and permissions.

    I want to see which Auth method they used to sign in e.g. email & password, GitHub SSO, Google SSO, AD 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

    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. Adding indexes(Not search index) using terraform

    I would like to create mongodb atlas index using terraform. But as of now we can able to create search index in mongodb atlas using terraform. here the expectation is to create normal index using terraform.

    35 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. EmbeddedDocuments Search multiple compound fields

    Today, it doesn't seem that a $search index on a list of object documents allows for an embeddedDocument search to match on multiple properties within the document.

    So, if I have:

    [{
    name: 'Doc 1',
    attached: [ { name: 'a', type: 'string' }, { name: 'b', type: 'number' }]
    },
    {
    name: 'Doc 1',
    attached: [ { name: 'a', type: 'string' }, { name: 'b', type: 'string' }]
    }]

    I would like to be able to write a compound query like this:

    [
    {
    $search: {
    index: "default",
    compound: {
    must: [
    {
    embeddedDocument: {
    path: "attached",
    operator: {
    compound:…

    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 API  ·  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. MongoDB Atlas historical stats by collection

    It would be helpful to have historical metrics for storage by collection. Storage space used, indexspace used, number of indexes.
    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Support resource tags included in billing ingestion dashboard while filtering Charts billing dashboard by resource tags

    It's important to support resource tags included in billing ingestion dashboard and filtering the charts based on these resource tags. Include the resource tags in Atlas billing dashboard as filter/group criteria

    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  ·  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)
  10. Support Auto-Resume in Trigger resource

    can we have an autoresume argument in mongodbatlaseventtrigger (https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/eventtrigger)?

    as in the screenshot, Auto-Resume suspended trigger can be switched on in Atlas UI.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Webhook

    Currently alert notification configuration allows webhook targets with a secret configuration. This limits us in terms of which webhooks could be configured. There are multiple webhooks which do not support secret configuration rather support Headers to be passed with authentication details.

    This request is to support additional set of header to be passed/added in the webhook configuration for alert notification.

    For example, during alert notification configuration I should be allow to configure additional set of headers like Authorization: "Basic cdge....==" and Source: "Atlas"; with Webhook URL configuration which is further used by target to first authorise POST call made by…

    7 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. 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)
  13. Support the unlimited mode for t3 AWS instances (M10 and M20)

    We use M10/M20 instances (AWS backend), which accumulate CPU credits over time. The problem is that when Atlas nodes run out of CPU credits, performance goes down and we see a lot of CPU steals. This is a common issue with AWS EC2 instances. We would like to have an option within Atlas UI (a tick box perhaps) to enable the unlimited mode for t3 instances (M10/M20).

    https://aws.amazon.com/ec2/instance-types/t3/

    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)
  14. Tuning of Performance Advisor

    Give users the option to modify the guidelines by which Performance Advisor provides its suggestion. A way for customers to input context so that Performance Advisor can give better suggestions

    Customers have been commenting that Performance Advisor suggestions are too aggressive at times for things such as creating/dropping indexes. They note that the frequency that they query something Performance Advisor suggests creating doesn't warrant the memory usage it would take to create that index. On the other hand, they may not use an index frequently, so Performance Advisor suggests dropping the index, but that item is critical to their application…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Add a role or modify Project Cluster Admin role to allow administrators to mange backup

    Today you must be Project Owner to manage backup scheduling and retention. This is far more excessive a permission than needed for DBAs to manage backup scheduling and retention. A role or another permission group for administrative tasks would be important for this product.

    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

    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)
  16. Improve Metric Correlation

    Would be nice to better correlate metrics, server events, and individual operations.

    For example would be helpful to have in the profiler indication of automatic scale up/down of the cluster in order to easily correlate actions that trigger them in the last 24h.

    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)
  17. Map IDP groups to Atlas teams

    At the moment Atlas does not support mapping IDP groups to existing Atlas teams. We would like that the integration would support that. For example:

    okta group "devops" --- mapped to ---> Atlas team "devops"

    Each time the customer adds a user to this idp group, the user will be given the proper permissions in Atlas.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Profiler: expose the dashboard ID and chart ID from which the query is originating

    My MongoDB analytics node performance is decreasing.
    Looking at the profiler it seems that some specific queries are super slow.
    I can see the full query, I can see that they originate from MongoDB charts ("appName": "atlas-data-federation|app-services|xxxxx").
    But I cannot see which dashboard ID and which specific chart ID this query is originating from.
    So I cannot, for example, easily find which chart to delete.

    Is this something you could help with? or any work around?
    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. AtlasProject CRD status fields

    Hi, we have created the Atlas project via Terraform and used the mongodb operator for cluster and user management, but for now, we use sidecar to set the status.id field in AtlasProject CRD since we use skip-sync flag ( so operator will not change project config) and the operator will not sync this field for us.
    If it is possible add a parameter to the spec where I could set this ID within resource creation ( so if we have a skip flag it will automatically set status.id ), so we can get rid of sidecar ( sidecar was implemented…

    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)
  20. Associate domains to an IDP at Organization level rather than for entire mongodb.com

    At this time domain to IDP associations apply to entire mongodb.com. This makes it very difficult for large companies that have several independent departments to use mongodb.com. Some departments might want to create separate Atlas organizations and others simply access Support section of mongodb.com web-site. They wouldn't want to share an IDP created within one Atlas organization.

    One possible approach to addressing this issue is for an Atlas organization to have a distinct sub-domain on mongodb.com (e.g. bigco-org-a.mongodb.com). Another approach would be to have a field for Atlas Organization name on logon page.

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

Feedback and Knowledge Base