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

    As a diabetic who relies on Nightscout but is not very experienced regarding building apps and utilising databases, etc., I just wanted to say thank you very much for the clear step-by-step mlab migration instructions and video that you provided. I was able to follow these and it all seems to have worked! 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  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  2. Indicate operation errors already in the plan phase

    This idea originates from my original bug report: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/284

    Changing the name of an existing custom_db_role is currently not possible without ending in an error in the apply step. The plan for a name change currently indicates the replacement due to the name change:

    # module.versioner.mongodbatlas_custom_db_role.this must be replaced
    
    -/+ resource "mongodbatlas_custom_db_role" "this" {
    ~ id = "someid" -> (known after apply)
    project_id = "5c860ed2a6f2396cd47f4785"
    ~ role_name = "old_name" -> "newName" # forces replacement

    Applying this results in the following error:
    > Error: error deleting custom db role (mongoversioner): DELETE https://cloud.mongodb.com/api/atlas/v1.0/groups/projectid/customDBRoles/roles/old_name: 409 (request "Conflict") Deleting specified custom role would…

    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  ·  Terraform Plugin  ·  Flag idea as inappropriate…  ·  Admin →
  3. Helpful error message when restoring backup

    When I recently attempted to restore a db backup I got a cryptic error message stating "Error: Cluster Not Found"--which was extremely confusing considering that I pressed the restore button in the backup options. After some great tech support, I added my user as project owner and everything worked fine.

    Please make the error message clearer in both the Restore and Download backup 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

    0 comments  ·  Backup  ·  Flag idea as inappropriate…  ·  Admin →
  4. Replace editor with MLab's editor

    Get rid of the dropdowns and give me a text box. Or at least an option to toggle off type safety.

    I see the strength of Mongo as being untyped, but this editor is forcing in type. In addition, it is incredibly clunky to use when adding new fields by hand.

    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 →
  5. 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 →
  6. Alias for Cluster name

    Add an alias to cluster name, as we are not allowed to change the cluster name. If we have an option to add an alias to cluster name. We can use it, in-case the user created the cluster with the wrong name. And in-screen u can show as clustername(alias). For better understanding.

    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 →
  7. The page fault metric is not available in the Datadog integration

    The page fault metric is not available in the Datadog integration

    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 →
  8. Better message for "Removed Indexes" in Activity Feed during Atlas rolling index build

    During a rolling index build, it is expected to have 2 "Deployment configuration published" notifications - 1 for Added Indexes and another 1 for Removed Indexes. This is because an entry for this desired index is added to the automation config and then the automation agent builds it accordingly. Once the agent is done building it, we remove the entry for that index from the automation config. Indeed, this does not drop the index.

    However, from the term of "Removed Indexes", it can cause confusion that the index is dropped. Hence, this feature request is filed for clearer message so…

    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 →
  9. Show index name/details when creating or dropping index via Data Explorer

    When Atlas user creates a rolling index in Data Explorer, we can see the name of the index being built in Activity Feed. However, if Atlas user creates an index or drops an index, the index name is not revealed in Activity Feed. This creates some complexity to trace which index is created or dropped via the Data Explorer

    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 →
  10. Trigger event when user confirmation state change

    I suggest that after user registered they should ve able to log in regardless of his account confirmation state, but if he is in a pending state, he could not do any read/write operation unless his own user data and his own user extra data,

    And the user can also detect if his confirmation state is change

    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 →
  11. Implement a refresh button for the BI Connector in Atlas

    When changes, such as when collections are added or removed, occur to an existing database with BI Connector enabled, the BI Connector needs to be cycled off and then on. This process is not well explained for Atlas. I feel that a refresh button that ripples Bi Connector in Atlas when changes occur would be beneficial, rather than having to dive in to edit configurations --> slide the "enable bi connector" from off, wait, than back to on.

    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 →
  12. mongorestore

    As per the mongorestore


    1. to preserve UUID must use drop collection

    2. if the collection is dropped then it will affect user/login access.

    This cascading effect makes it's impractical to use. We wanted to use mongorestore UUID as an idempotent operation, in case halfway things go wrong and have to start again then it's useful to preserve UUID.

    Also, in the mongorestore there should be an option to ignore/skip index creation, we were trying to bring data from the legacy app without indexes. It seems that's not possible at this moment.

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

    When I tried to register for Atlas webinar, host country selection was mandatory. By default it displays the USA first value in the dropdown and have to scroll down to select another country. It would be a good user experience if on the registration page visitor/user's country is identified and by default selected, this will prevent unnecessary scrolling.

    Also, a very annoying thing is that in order to register for the webinar have to agree to subscription. Subscription to email and other notification should be optional, otherwise, it's a bit dodgy tactic more suitable to some social media companies who…

    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. Privilege advisor capability

    It would be incredibly helpful to have some sort of capability that allows users within the Atlas portal to be able to see what privileges are needed to perform various actions. For example, we have users that are not able to configure alerts, or other users that are not able to add users to a project. It isn't always clear what privileges are needed in order to give users those capabilities. Either some sort of tool would be helpful, or very clear documentation on privileges that are needed for each capability within Atlas.

    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 →
  15. Find filter autofill list should be Collection dependant

    The Clusters > Collections > Find option offers an auto-fill drop-down of previous entries, which is super helpful. However, it seems to offer suggestions from previous queries of all the Collections. This is not helpful, since Document keys tend not to overlap across Collections, so it would be even more helpful if the drop-down only listed previous queries from the selected Collection.

    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 →
  16. Live Migration Should Include Database User, Password and Role Information

    Please provide the option to include database username, password and role information during a Live Migration. DBAs often do not have direct access to database credentials and have to collect them from the various development teams.

    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 →
  17. Way to enforce 2FA across organisation

    Please add the capability to enforce 2FA (As a setting) for any user invited to join a team. This would be a good step towards better security management

    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  ·  IAM  ·  Flag idea as inappropriate…  ·  Admin →
  18. MongoDB Sink Connector - Confluent Cloud

    Confluent cloud -Mongodb Sink connector requires Atlas whitelist IP to 0.0.0.0/0 which is a security issue on our side. Can mongodb partner with confluent and provide a solution that can be accessed through VPC private link? We are very interested in mnogodb Sink Connector for our solution so we don't have to maintain aws ec2 instances for the sink connectors.

    https://www.confluent.io/blog/confluent-cloud-offers-kafka-mongodb-connector-fully-managed-clusters/

    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. Aggregation builder history

    Add some way to restore old aggregations pipelines from history, that way, even if I accidently closed the UI. I will have backup.

    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 →
  20. API Improvements - OpenAPI and more auth options

    The API should be documented with OpenAPI to allow better tooling.

    Ideally using the above OpenAPI spec you could auto generate a SDK or API client for popular languages.

    Lastly, the API should accept authentication options other than digest. There is very poor support for digest authentication by popular HTTP clients. I don't like trying to implement security protocols myself, as there is often some quirk I have not fully understood that ends up leaving me less secure than I hoped.

    In many questions online when searching for information about digest authentication, the person asking the question is asking 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  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base