455 results found

1. Show billing amount on top all the time

   Would be nice if I can see my current billing on top all the time, even in Atlas, like it used to be before UI change. Thanks.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Support multiple LDAP servers and TLS connection options

   When integrating my Atlas project with an LDAP service, we want to specify multiple LDAP servers rather than just one, and to specify options for the TLS connection such as allowing invalid hostnames. Both of these can be done in self-managed MongoDB Enterprise.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Vanity URLs for projects and clusters

   Right now URLs for mongodb clusters are generatd by MongopDB. For the clusters I create it would be much easier to remember and distribute if I could create a canonical name per project and have each cluster member have its named assigned by the cluster.

   So instead of demodata.rgl39.mongodb.net I could use demodata.joedrumgoole.com.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Terraform for LDAP user/groups

   We'd love to be able to create LDAP user and group accounts in Atlas via terraform. The existing mongodbatlasdatabaseuser resource doesn't support LDAP, so we are forced to use the API to create those users and groups.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Provide Atlas support for "Classic" VNet Peering topology

   Provide Peering support for "Classic" (Hub and Spoke) VNet Peering topology, either directly or via a NAT

   12 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. It would be useful to have an ability to pragmatically keep up to date with the latest prices in a RESTful fashion.

   Something like /offerings/aws/compute/M10 returns:

   {
   // some metadata about this pricing api.
   "prices": [
   {
   "priceId": "c800b6d9163b0db7",
   "region": "us-east-1",
   "charges": {
   "compute": {
   "price": 0.11,
   "interval": "hourly",
   "currency": "USD"
   },
   "storage-GB-month": {
   "price": 0.015,
   "interval": "hourly",
   "currency": "USD"
   },
   "backup-GB-month": {
   "price": 2.5000000001,
   "interval": "hourly",
   "currency": "USD"
   }
   }
   }
   ]
   }

   Use case: For those that use programs to calculate costs, this will reduce some of the guesswork involved by looking at cryptic documentation and invoices to calculate and forecast costs and be able to charge appropriately to match systems with demand.

   Amazon has similar API endpoints available:

   https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonEC2/current/us-east-1/index.json
   ^ warning: 87Mb JSON file.

   Something like /offerings/aws/compute/M10 returns:

   {
   // some metadata about this pricing api.
   "prices": [
   {
   "priceId": "c800b6d9163b0db7",
   "region": "us-east-1",
   "charges": {
   "compute": {
   "price": 0.11,
   "interval": "hourly",
   "currency": "USD"
   },
   "storage-GB-month": {
   "price": 0.015,
   "interval": "hourly",
   "currency": "USD"
   },
   "backup-GB-month": {
   "price": 2.5000000001,
   "interval": "hourly",
   "currency": "USD"
   }
   }
   }
   ]
   }

   Use case: For those that use programs to calculate costs, this will reduce some of the guesswork involved by looking at cryptic documentation and invoices to calculate and forecast costs and be able to charge appropriately to match systems with demand.

   Amazon has similar API endpoints available:

   https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonEC2/current/us-east-1/index.json… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Login auto-redirects to 2FA screen but shouldn't, or offer logout

   I have three MongoDB Atlas logins and when I visit the Atlas login page it then redirects me to the 2FA page.

   I actually just want to swap between accounts, so either a logout option would be useful, or let me return to the login screen from the 2FA screen. Unfortunately if I click 'back' the app forwards me back to the 2FA screen.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Expose the `indexStats` action when creating custom roles in Atlas UI.

   The $indexStats aggregation pipeline allows user to get the statistics regarding the use of each index for the collection. This aggregation pipeline requires the indexStats diagnostic action.

   However, currently Atlas UI doesn't expose this action when creating custom roles. It would be nice to have this action listed in the "Collection Actions => Diagnostic Actions" list.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. readPreferenceTag flexibility in Atlas

   Looking to get more flexibility to target electable nodes and the workload isolation nodes. Some ideas are to allow for custom tags or having tags that allow for targeting read-only and electable nodes together. This allows for users use the read-only nodes to scale out reads along side the electable secondaries without having to juggle multiple connection strings.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Allow me to pay for a month of "developer" level support without committing to a subscription

    AWS lets you pay for a month of support at any time.
    My understanding of MongoDB support is that if you discontinue support and then start again a year later, you have to pay for all the interim months.
    Another way of doing this would be to pay per-incident. I like the monthly model better because it would work for people just getting started to ask a lot of questions.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Zapier Integration

    Currently The Mongo Atlas connection string is not supported by Zapier! What??

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Provide UI to test failover of a sharded cluster

    Currently we can test failover of replica set to test that application gracefully handle elections etc. I'd like to see a way to do the same for sharded clusters. Maybe this could turn off a random mongos router node at the same time as trigger an election on one of the shards.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Atlas MongoDB Users Page has Confusing Role Assignment

    There is currently some confusion that has been introduced in the UI regarding the “old” way of specifying namespace-level roles and the “new” way that is used when using custom roles in Atlas.

    Let's say I create a user, hi, with the readWrite default role on funkydb:

    https://cl.ly/bf42cae9383b/Image%202019-02-27%20at%2010.21.46%20AM.png

    And create a separate MongoDB user, hi_again, assigned the funkydbreadwrite custom role (which is defined the same way, with the readWrite default role on funkydb):

    https://cl.ly/0b0b1ee50722/Image%202019-02-27%20at%2010.22.48%20AM.png

    These two roles are essentially the same, but the UI in the MongoDB Users tab renders them differently:

    https://cl.ly/5cc211e2c7d7/Image%202019-02-27%20at%2010.19.40%20AM.png

    In the example described above, the @admin and @funkydb portions in the "MongoDB Roles" column seemingly have different definitions even though both are functionally the same.

    A few suggestions for improving the UI:

    • Have all user roles specified with @admin in the MongoDB Users tab, that way there is no confusion with regards to where these role definitions are stored (in the admin database). Any references to @namespace other than @admin should not be used in the MongoDB Users’ “MongoDB Roles” tab (https://cl.ly/a4a7fa3710f1/Image%202019-02-27%20at%204.28.31%20PM.png). The current UI implies that these users are stored on that database, which we know not to be the case.
    • Custom roles should be linked in the "MongoDB Users" tab to the actual Custom Roles that is is referring to (https://cl.ly/014f6e327dd0/Image%202019-02-27%20at%204.29.22%20PM.png), or at the very least to the "MongoDB Roles" tab. For extra clarity, the modal should actually pop up for that custom role to give the user the full picture of what that role does.
    • I've always found calling out the namespace in the MongoDB Users tab if they were defined with a default role through the old UI (by clicking "Add Default Privileges" in the modal window) to be confusing, especially given that we now have custom roles that specify @admin by default. We should probably have an additional column in the MongoDB Users tab that notes which namespaces the role in question is scoped to, to make it more explicit. As in the prior suggestion, the "MongoDB Roles" column would still be changed to @admin in all instances, and this would be a new column to indicate which namespaces the role is being applied to.

    There may be some aspects of this that I overlooked, however the current implementation leaves a lot to be desired, and can be difficult to reason about from just looking at it from the customer side of things.

    There is currently some confusion that has been introduced in the UI regarding the “old” way of specifying namespace-level roles and the “new” way that is used when using custom roles in Atlas.

    Let's say I create a user, hi, with the readWrite default role on funkydb:

    https://cl.ly/bf42cae9383b/Image%202019-02-27%20at%2010.21.46%20AM.png

    And create a separate MongoDB user, hi_again, assigned the funkydbreadwrite custom role (which is defined the same way, with the readWrite default role on funkydb):

    https://cl.ly/0b0b1ee50722/Image%202019-02-27%20at%2010.22.48%20AM.png

    These two roles are essentially the same, but the UI in the MongoDB Users tab renders them differently:

    https://cl.ly/5cc211e2c7d7/Image%202019-02-27%20at%2010.19.40%20AM.png

    In the example… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Live Migrate from Backup or Snapshot

    If I already have Cloud Manager backups, or can take an EBS snapshot, I want to be able to quickly Live Migrate this replica set to minimize migration time and load on my existing infrastructure.

    9 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Middle Clicking MongoDB Account should open a new tab
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Support HITRUST certification for Atlas

    Some companies want a certification from HITRUST https://hitrustalliance.net/about-us/ in order to put workloads in the cloud

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Extend / Configurable retention time of audit logs

    This is a feature request to extend or have configurable retention time of audit logs more than 30 days in Atlas.

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Change/Option to change Default Storage Compression to zlib

    This is a feature request to change or provide an option to change Default Storage Compression to zlib

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Pause and Resume clusters needs a timestamp in the JSON

    Currently clusters can only be paused for 7 days. After that period they must be resumed for at least one hour. However the time of resumption is not included in the result from the resume REST call. If that data was included a script could determine easily when to pause a cluster again after maintenance jobs are finished.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Allow multiple Billing emails

    Allow multiple billing e-mails instead of just one. There are multiple people in our org who want a copy of the invoices, but I don't want them sent to the entire org (which is what happens if there's no billing e-mail)

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close