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

1273 results found

  1. Allow triggers to be tested locally

    Our team uses and loves Stitch/Realm triggers. We've got them wired up so that we can update them from a bash script. They work well, but they are hard to debug -- it'd be nice if there was a CLI option to test them against a local mongodb instance.

    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

    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)
  2. More detailed update status

    It would be amazingly helpful to see more detailed information on recovering nodes. Just knowing that the node is, for example, "81% of the way on initial sync" is much more informational (and lets users know that it isn't stuck) as compared to the node being in "Startup2" recovery.

    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. "Native" Azure integration (Costing, Resource Groups)

    I would love to do away with MongoDB CosmosDB on Azure - simply because
    a) CosmosDB emulator is troublesome to install (for local development)
    b) Limited MongoDB feature support
    c) Difficulty getting Bulk inserts/upserts to work well in CosmosDB MongoDB (due to rate limiting and bugs with IsUpsert=true)

    Currently we have 18 CosmosDB databases - nfortunately, the main barrier of entry for my organization in adopting Atlas is it's Azure integration - specifically:
    a) Atlas resources are not visible/manageable via Azure Resource Groups - this makes our existing Azure DevOps practices/infrastructure as code obsolete for this (versus all our other…

    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  ·  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)
  4. Graph connections per user (or per database)

    Show a graph of connections per user.

    It would be very useful to see how many connections each user has (or also, each db) over time.

    It would allow us to see more clearly and faster which service uses how many connections.

    11 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)
  5. SHA1 Digest hash for Atlas Cloud Backup Restore

    Atlas Legacy Backup used to have digest hash (SHA1 Checksum) on the restore job, but it is currently not available in Atlas Cloud Backup. This feature will be helpful in validating the integrity of the downloaded file.

    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

    4 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)
  6. Add a Transaction Commits / Sec Metric Graph to Atlas

    Add a graph in Atlas to display "transactions.totalCommitted" on a per second basis to the Atlas metrics UI. Customers that are using transactions are often more interested in the # of transaction commits per second than opcounters.

    I have had to use mongostat on a number customer evaluations because this metric is not available.

    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)
  7. Allow suggest password feature

    In both mobile and desktop version of Chrome and Safari, there is a feature for automatically generating a strong password.

    In the registration form for MongoDB Atlas, the password field in the registration form cannot take values entered this way. Please add this feature since password managers are in fact quite normal in this era.

    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

    under review  ·  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)
  8. Allow custom date range to be submitted in Query Profiler

    Currently the Query Profiler can plot queries that were logged up to 24 hours in the past.

    It would be helpful to allow for visualization of a custom date range older than 24 hours ago, rather than only queries logged within the past 24 hours. This could help with RCAs for events that occurred more than 1 day ago, and also help teams who collaborate to investigate queries over a time period longer than 1 day.

    16 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)
  9. Allow 'Download Logs' for user that is not a Project Owner but Project Data Access Read Only or Project ReadOnly

    Currently in order to allow a user to download logs, it is necessary to make that user Project Owner. In a situation when a user outside the company is invited to review the project, it is not possible to grant such high level role when the access needed is only to look at logs. Project ReadOnly or Project Data Access ReadOnly should be sufficient to access logs, if the user is also granted atlasAdmin@admin access to Database

    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

    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)
  10. Extend sub-hourly metrics retention to 72 hours

    Right now the 1- and 5-minute metric data is lost after 48 hours (when it is combined into the hourly data). This makes it impossible to take a close look, on a weekday, at an event that occurred over the weekend.

    It would be nice to be able to look at a problem on the weekend and say "I'll look at this more closely on Monday", and then have the ability to actually investigate it on Monday.

    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)
  11. Make Connect modal button to a location accessible from any cluster tab

    I often want to connect to the cluster after browsing in the Collections tab (e.g. to run some test queries via the shell).

    The Connect button (available in the Overview tab) makes connecting easy, but this button is not visible in the Collections tab -- I have to click into Overview or the Clusters page to access the Connect modal button.

    Can we surface a Connect button so that it is clickable from any tab in the cluster page?

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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  ·  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. Allow to resend alert to a PagerDuty service

    Like with other type of alert targets (Send to), we would like to be able to resend an alert to PagerDuty.

    The reason is that an alert sent to PagerDuty can be mistakenly resolved but the real issue is still there, and the alert is still firing in Atlas.

    Because it is already firing, it won't fire again so from that moment on, there is no way to get a notification of that alert so we might be missing a real issue.

    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)
  14. 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 leave the…

    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)
  15. Snapshot cluster and copy

    In one click I would like to copy the exactly one database and put it in another cluster. This is especially useful for debugging.

    This would allow us to easily recreate the database from our production cluster and put our staging (or other possible clusters) cluster into an exact state to help replicate issues or bugs.

    8 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. Allow customers to download Atlas BI Connector process logs (similar to MongoDB Server logs)

    What is the problem that needs to be solved? Customers are willing to troubleshoot / analyze Atlas BI Connector logs by themselves (they would like to investigate schema sampling timings, SQL/MongoDB query optimizations, connectivity issues, etc.).

    Why is it a problem? (the pain) Currently available Download Logs option on Atlas Clusters does not include Atlas BI Connector process logs.

    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)
  17. Allow users to download backup snapshots from BYO-KMS encrypted clusters

    Many clients download backup snapshots to keep an offline copy of their data either to restore it into their on-prem development environment or to keep an offline copy of their data. At the moment, Atlas does not allow downloading backup snapshots that have customer BYO-KMS encryption enabled.

    21 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)
  18. Google Data Studio Connector

    Create official Google Data Studio connector.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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.

    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  ·  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)
  20. Make collections scrollable

    We have databases with many collections. The problem with that is that in order to select certain collection, I have to scroll the results part of the page. So I'm going up and down all the time I select another collection and make some query.

    In sum, please add scroll in the collection explorer UI.

    Regards

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

Feedback and Knowledge Base