1373 results found

1. Separate metric graphs of egress outside the region per database, collection, user, destination

   Separate metric graphs of egress outside the region per database, collection, user, destination, so that I can easily find out what is causing the egress traffic which is billed on my account. This will also help me identify what parts could be good to move to different cluster in another region closer to the user,

   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  ·  Monitoring and Metrics  ·  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

2. Allow default settings on alerts on project/organization level

   It would be great if there was a way to set the default notification channels for alerts on the project and organization level.

   I was recently informed by the support team that there is no possible way of doing so, and that all alerts should be changed individually rather than for the whole project in one go.

   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  ·  Monitoring and Metrics  ·  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. MongoDB to throw error when detect '.' in keys insert

   Not sure if MongoDB was supposed to be unstructured even for keys. Because MongoDB currently does not support '$' and '.' in its keys, is it possible for MongoDB to throw an error if '$' or '.' are detected in keys during insert? MongoDB currently does not do that and is problematic to fix for previous large databases which have '$' or '.' in keys

   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  ·  Data Explorer  ·  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

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

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

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

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

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

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

10. Ability to stop the snapshot restore in the Atlas UI

    This is a feature request for ability to stop the snapshot restore in the Atlas UI

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

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

13. Add eventTypeName for Maintenance Windows in alertConfigs response

    After adding a maintenance window to an Atlas project, the alertConfigs returns additional entries that do not include an eventTypeName field, it seems that these additional entries relate to the maintenance window but it's not clear:

    {
    "created" : "2020-02-28T16:04:18Z",
    "enabled" : true,
    "groupId" : "",
    "id" : "",
    "links" : [ {
    "href" : "https://cloud.mongodb.com/api/public/v1.0/groups/***/alertConfigs/5e593a02559f765dca07acfe",
    "rel" : "self"
    } ],
    "matchers" : [ ],
    "notifications" : [ {
    "delayMin" : 0,
    "emailEnabled" : true,
    "intervalMin" : 60,
    "roles" : [ "GROUPOWNER" ],
    "smsEnabled" : false,
    "typeName" : "GROUP"
    } ],
    "updated" : "2020-02-28T16:04:18Z"
    }, {
    "created" : "2020-02-28T16:04:18Z",
    "enabled" : true,
    "groupId" : "",
    "id" : "",
    "links" : [ {
    "href" : "https://cloud.mongodb.com/api/public/v1.0/groups/***/alertConfigs/5e593a02559f765dca07ad01",
    "rel" : "self"
    } ],
    "matchers" : [ ],
    "notifications" : [ {
    "delayMin" : 0,
    "emailEnabled" : true,
    "intervalMin" : 60,
    "roles" : [ "GROUPOWNER" ],
    "smsEnabled" : false,
    "typeName" : "GROUP"
    } ],
    "updated" : "2020-02-28T16:04:18Z"
    }, {
    "created" : "2020-02-28T16:04:18Z",
    "enabled" : true,
    "groupId" : "",
    "id" : "",
    "links" : [ {
    "href" : "https://cloud.mongodb.com/api/public/v1.0/groups/***/alertConfigs/5e593a02559f765dca07ad04",
    "rel" : "self"
    } ],
    "matchers" : [ ],
    "notifications" : [ {
    "delayMin" : 0,
    "emailEnabled" : true,
    "intervalMin" : 60,
    "roles" : [ "GROUP_OWNER" ],
    "smsEnabled" : false,
    "typeName" : "GROUP"
    } ],
    "updated" : "2020-02-28T16:04:18Z"
    } ],
    }%

    Can eventTypeName be added to this response?

    After adding a maintenance window to an Atlas project, the alertConfigs returns additional entries that do not include an eventTypeName field, it seems that these additional entries relate to the maintenance window but it's not clear:

    {
    "created" : "2020-02-28T16:04:18Z",
    "enabled" : true,
    "groupId" : "",
    "id" : "",
    "links" : [ {
    "href" : "https://cloud.mongodb.com/api/public/v1.0/groups/***/alertConfigs/5e593a02559f765dca07acfe",
    "rel" : "self"
    } ],
    "matchers" : [ ],
    "notifications" : [ {
    "delayMin" : 0,
    "emailEnabled" : true,
    "intervalMin" : 60,
    "roles" : [ "GROUPOWNER" ],
    "smsEnabled" : false,
    "typeName" : "GROUP"
    } ],
    "updated" : "2020-02-28T16:04:18Z"
    },… 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  ·  Monitoring and Metrics  ·  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. Allow Atlas Database Access History be accessed by Atlas read only role
    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  ·  Monitoring and Metrics  ·  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. Time Sensitive Alerts

    I would like the ability to (optionally) set a time window for any alert. IE Alert me if average write latency rises above 500 msec from 8am to 8pm. If outside those times don't alert me.

    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  ·  Alerts  ·  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. Add more details on backup policy changes in Atlas activity feed

    In Atlas when you search for "Cloud provider snapshot schedule updated for cluster" in the project's Activity page, it doesn't provide any details on schedule policy changes information, the customer have to call the snapshot schedule API to get the policy schedule change information. However, the API call output still doesn't have any history change information for audit purpose.

    Please consider add that information to the Atlas activity feed page.

    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  ·  Backup  ·  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. Allow to Peer with VPC's that doesn't follow Private Networks Ranges

    Allow to Peer with VPC's that doesn't follow Private Networks Ranges

    Currently I have one infrastructure based on a VPC with the CIDR range of 30.0.0.0/16, and I'm unable to make it safe with VPC peering because of the restrictions on this.

    https://docs.atlas.mongodb.com/security-vpc-peering/

    I thinl that allowing to peer with any AWS VPC's that do not overlap would be nice, as it is difficult to change the VPC when you have a running infrastructure, just to integrate safely with MongoDB Atlas

    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

18. More granular results in Activity Feed

    I can't see all the data I want today

    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  ·  Monitoring and Metrics  ·  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. Support TLS1.3 in Atlas Control Plane and Clusters

    Add TLS1.3 as an option for encryption-in-motion.

    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

20. Missing time zone name

    I was trying to Select my country's timezone but I could not find it. Namibia's timezone is Africa/Windhoek +2 GMT or otherwise Central Africa Time +2 GMT after it abolished the Daylight savings time in 2017. However, none of the options are available for timezone selection when setting cloud preferences.

    Please note I can not use another country's timezone even if they are similar.

    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