468 results found

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

   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

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

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

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

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

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

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

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

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

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

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

    7 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

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

14. Terminate existing connections from IPs when removed from the whitelist

    When removing entries from an Atlas Project's IP whitelist, existing connections from those IPs are maintained, and thus those hosts can continue to perform operations until the connection times out. I'm aware such connections can be dropped by doing a Test Failover or pausing and unpausing the cluster, but in some scenarios this is not ideal if even possible. This also seems like a security gap: When access is revoked from a particular IP or CIDR block, any existing client connections originating from that IP or CIDR should be terminated and the hosts behind that IP or CIDR should be disallowed from establishing new connections until such a time as they are re-added to the whitelist, if ever.

    When removing entries from an Atlas Project's IP whitelist, existing connections from those IPs are maintained, and thus those hosts can continue to perform operations until the connection times out. I'm aware such connections can be dropped by doing a Test Failover or pausing and unpausing the cluster, but in some scenarios this is not ideal if even possible. This also seems like a security gap: When access is revoked from a particular IP or CIDR block, any existing client connections originating from that IP or CIDR should be terminated and the hosts behind that IP or CIDR should be… more

    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

    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

15. Description field for VPC peering page

    Add a description field to easily identity the peering items in Peerings tab. Example: "Peering for Stage Kubernetes cluster apps"

    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

    2 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

16. Project Homepage / Ability to add descriptions to Atlas projects

    We have a lot of Atlas projects in our org, some are outdated, unused, orphaned, some important and used for production. It would be great to have a way to describe what each of them are for, who to contact for questions, etc.

    For example, when you switch to a project, you land on the project homepage that has the description right there, alongside an overview of how many clusters, users, last change, if whitelists are enabled etc. Even better if I can use Markdown or some other "rich" editing experience to create the description and add links, bullet points, etc.

    We have a lot of Atlas projects in our org, some are outdated, unused, orphaned, some important and used for production. It would be great to have a way to describe what each of them are for, who to contact for questions, etc.

    For example, when you switch to a project, you land on the project homepage that has the description right there, alongside an overview of how many clusters, users, last change, if whitelists are enabled etc. Even better if I can use Markdown or some other "rich" editing experience to create the description and add links, bullet points,… more

    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

    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. Add support for arbiters

    We have a situation where we are required to build in an AWS region that only has two AZs (ca-central-1). In addition, there are no other AWS regions in the country (Canada). And due to our requirement around data sovereignty, we can't host this data set within a different country.

    Because of this, we can't guarantee our cluster will stay up if we lose a single AZ unless we put an arbiter in a 2nd region (since no data is copied to the arbiter). However, Atlas does not support arbiters currently. I know arbiters aren't ideal, but in this edge case, it would benefit us. With our non-Atlas MongoDB cluster we can support this model, but with Atlas, we cannot. And this may keep us from moving this particular cluster into Atlas until it is supported.

    Let us know if you have any questions.

    Thank you!

    We have a situation where we are required to build in an AWS region that only has two AZs (ca-central-1). In addition, there are no other AWS regions in the country (Canada). And due to our requirement around data sovereignty, we can't host this data set within a different country.

    Because of this, we can't guarantee our cluster will stay up if we lose a single AZ unless we put an arbiter in a 2nd region (since no data is copied to the arbiter). However, Atlas does not support arbiters currently. I know arbiters aren't ideal, but in this edge… more

    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

    2 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. Requesting database wise billing data in a shared cluster

    Currently we developing a portal to provide cost details to each customer who are using our platform. We have shared clusters in out pre environment and need to calculate cost for each customer for lower environment.

    Better if you can provide an API call to get this database wise cost details.

    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

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

20. Fix a glitch in the web app's UI

    Just pointing out a little glitch in the UI:
    When we have very long values, the key is invisible and the field type is pushed to the side.
    Screenshot attached.

    •  

    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

    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