471 results found

1. Support for VPC Lattice

   Additionally to the existing VPC PrivateLink Endpoint method to have connectivity it would be great if I could integrate a MongoDB Atlas project via a VPC Lattice service and share that one with customer accounts on AWS. - Red Bull Media House

   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

2. Ability to schedule "Hedged read" Turn on/off

   Customer experienced read latency during maintenance after sharding.
   Our guidance is to turn on "Hedged read" option.
   So the customer need to turn on/off "Hedged read" before/after maintenance, because turning on "hedged read" increase CPU usage that means server cost increasing.

   Currently "hedged read" on/off can be done by technical support from MongoDB but this feature is needed for operational efficiency and reducing human error.

   8 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

3. On-Demand Pricing

   I have been an enthusiastic MongoDB user for a couple of years now. My business is very small and the utilization of the database is very irregular. For example, I only have a higher workload on one day of the week and on most other days I only have a load in the morning and often nothing at all at night and at weekends. That's why the smallest available plan that can also be used in production (M30) is actually too expensive for me. A pay-per-use pricing concept would be ideal and I'm not sure whether this would be possible as a cloud solution with MongoDB. Since I haven't found a solution, I'm biting the bullet and switching to AWS DynamoDB. I don't need the infinite scaling features, but the ability to pay by use is infinitely valuable to me. I really hope that something like this will be possible in the MongoDB world at some point.

   I have been an enthusiastic MongoDB user for a couple of years now. My business is very small and the utilization of the database is very irregular. For example, I only have a higher workload on one day of the week and on most other days I only have a load in the morning and often nothing at all at night and at weekends. That's why the smallest available plan that can also be used in production (M30) is actually too expensive for me. A pay-per-use pricing concept would be ideal and I'm not sure whether this would be possible… 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

4. add cluster manager email

   Hi,
   It would be nice to be able to assign a cluster manager email / contact per cluster and not per project. We have different team members managing different clusters within each of our projects and it would be great if we could alert them specifically on specific events in a cluster (like new index suggestions, disk increase, etc.)

   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

5. Add usability to tags

   Atlas has the option to set tags to clusters. But - now what? They are just pieces of text floating around, but are completely useless.
   How about enabling to filter clusters in a project or even organization based on those tags? Split costs based on them? Query them with API calls? I have no use of those tags when they are just texts in the main page of Atlas...

   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

   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

6. Adjust the Blue Mode into the actual Dark Mode

   Thanks a lot for the newly added "Dark Mode", it looks awesome. One suggestion would be to shift the blueish tone to a more grey tone instead. As we know blue light disrupts sleep :)

   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. Support the unlimited mode for t3 AWS instances (M10 and M20)

   We use M10/M20 instances (AWS backend), which accumulate CPU credits over time. The problem is that when Atlas nodes run out of CPU credits, performance goes down and we see a lot of CPU steals. This is a common issue with AWS EC2 instances. We would like to have an option within Atlas UI (a tick box perhaps) to enable the unlimited mode for t3 instances (M10/M20).

   https://aws.amazon.com/ec2/instance-types/t3/

   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. Sortability for Network Access IP list

   In the Network Access page for Mongo Atlas, on the IP Access List tab, it lists the IP addresses/blocks that are defined, along with their comments, in a table.

   The rows in this table don't seem to be sorted in any way. Doesn't look like they're ordered by IP address, Comment, or creation date. And when I click on the column headers, it doesn't sort them. IMHO, that makes it hard to find specific entries, and also to skim through to get an overview of what all is in there.

   It would be nice if this table were sortable by clicking on the IP Address and Comment column headers, and if it were sorted on one of those by default.

   It would also be nice if this table showed the creation and modification times for each entry (and was sortable on those too), along with the username of the user that created each entry (and was sortable on that too).

   I'm not including a screenshot in this post, because it would take a while to construct an example using bogus/redacted data in a test Atlas account. But if it's not clear what I'm suggesting here, let me know and I will do so.

   This suggestion post is kind of an expansion of these other existing suggestion posts:

   • https://feedback.mongodb.com/forums/924145-atlas/suggestions/43202850-in-atlas-cloud-manager-sort-the-network-ip-access
   • https://feedback.mongodb.com/forums/924145-atlas/suggestions/44103186-add-date-added-and-date-updated-to-network-access
   • https://feedback.mongodb.com/forums/924145-atlas/suggestions/40844107-sort-ip-whitelists-in-atlas

   In the Network Access page for Mongo Atlas, on the IP Access List tab, it lists the IP addresses/blocks that are defined, along with their comments, in a table.

   The rows in this table don't seem to be sorted in any way. Doesn't look like they're ordered by IP address, Comment, or creation date. And when I click on the column headers, it doesn't sort them. IMHO, that makes it hard to find specific entries, and also to skim through to get an overview of what all is in there.

   It would be nice if this table were sortable by… 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

9. Display a cluster tier size (e.g. M20) on the all Clusters page

   I am opening this new feature request on behalf of the customer. Would it be possible to display a cluster size (e.g. M20) on the main status page alongside other cluster information that's already on the page?

   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

10. Atlas - Queue cluster pause request to perform it when it's possible

    It is impossible to pause a cluster that was recently resume.

    The documentation indicates it is a voluntary feature (https://www.mongodb.com/developer/products/atlas/pause-resume-atlas-clusters/) to allow the Atlas service to apply any pending changes or fixes to the cluster that may have accumulated while it was paused.

    I agree with this, but it cause a problem for automation (for example sometimes we launch a platform exclusively for testing purpose and then shut it down, it is complicated to add a delay for pausing the Atlas cluster) and even manually for example at the end of the day of work this requires either staying later just to replay the pause or leaving the cluster running all night for example.

    I want to suggest you to improve this feature by recording the pause request and applied it once you finished your maintenances. You might introduce a new cluster state (terminating ?) to show to everyone that the cluster will be paused in few time.

    It is impossible to pause a cluster that was recently resume.

    The documentation indicates it is a voluntary feature (https://www.mongodb.com/developer/products/atlas/pause-resume-atlas-clusters/) to allow the Atlas service to apply any pending changes or fixes to the cluster that may have accumulated while it was paused.

    I agree with this, but it cause a problem for automation (for example sometimes we launch a platform exclusively for testing purpose and then shut it down, it is complicated to add a delay for pausing the Atlas cluster) and even manually for example at the end of the day of work this requires either… more

    10 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

11. Ability to create mirror/snapshot clusters for load and behavior testing

    We would like to request the following:

    1. The ability to create a "mirror" or "snapshot" of a production cluster to a staging cluster.
    2. This could be either real-time or scheduled (once per day, once per week, etc.) If scheduled, it would be nice to be able to spin up a new cluster each time it's mirrored (so that previous mirrored cluster remains available)
    3. The mirroring should be allowed to use a different hardware type, for example, our production cluster uses NVME disks, but our mirrored cluster we'd use cheaper HDDs with lower CPU.
    4. The mirrored cluster should be allowed to use a different MongoDB server version than the one it replicated from.
    5. When mirroring, have ability to exclude collections and exclude/mask certain fields within a collection (e.g. via an aggregation pipeline-like syntax)
    6. Ability to get API triggers when the mirrored cluster is copied and ready. We would use these triggers to perform additional actions such as switching our staging environment to point to the new cluster, inserting/removing data manually, etc.
    7. Have ability to mirror production cluster query traffic to the mirror cluster, i.e. for load-testing. This is particularly useful when upgrading database version, or experimenting with different instance types. Having the ability to "sample" queries (e.g. 1-out-of-10 queries gets mirrored) would be useful, and also to restrict any data insertion so the queries are read-only.

    Related to: https://feedback.mongodb.com/forums/924145-atlas/suggestions/40311163-option-to-restore-one-or-more-db-from-snap-to-clus

    We would like to request the following:

    1. The ability to create a "mirror" or "snapshot" of a production cluster to a staging cluster.
    2. This could be either real-time or scheduled (once per day, once per week, etc.) If scheduled, it would be nice to be able to spin up a new cluster each time it's mirrored (so that previous mirrored cluster remains available)
    3. The mirroring should be allowed to use a different hardware type, for example, our production cluster uses NVME disks, but our mirrored cluster we'd use cheaper HDDs with lower CPU.
    4. The mirrored cluster should be allowed to… 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

12. Manage Feature Compatibility Version (FCV) flag separately from version upgrade

    When performing a major server version upgrade (e.g. to MongoDB 7.0), Atlas automatically set the Feature Compatibility Version (FCV) flag to the same version.

    We would like to see this be a two-step, i.e.
    1. When upgrading to 7.0, Atlas keeps the FCV pinned at "6.0"
    2. 1~2 weeks after upgrading, Atlas reminds us increase the FCV to "7.0", i.e. once we've seen it running stable.

    We had a major production-outage issue in upgrading to MongoDB 7.0 and because of the current Atlas FCV behavior we could not downgrade back to 6.0.

    We understand that some users don't care about FCV, so for such users there could be a "YOLO" mode which is the current behavior. However, we don't think YOLO mode should be default.

    It seems there are a number of similar feature requests, e.g.:
    - https://feedback.mongodb.com/forums/924145-atlas/suggestions/40881025-have-the-ability-to-downgrade
    - https://feedback.mongodb.com/forums/924145-atlas/suggestions/42176614-major-version-downgrade-request-4-0-to-3-6

    When performing a major server version upgrade (e.g. to MongoDB 7.0), Atlas automatically set the Feature Compatibility Version (FCV) flag to the same version.

    We would like to see this be a two-step, i.e.
    1. When upgrading to 7.0, Atlas keeps the FCV pinned at "6.0"
    2. 1~2 weeks after upgrading, Atlas reminds us increase the FCV to "7.0", i.e. once we've seen it running stable.

    We had a major production-outage issue in upgrading to MongoDB 7.0 and because of the current Atlas FCV behavior we could not downgrade back to 6.0.

    We understand that some users don't care about… 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

    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

13. Enforce MFA for google login users

    Our organization needs to enforce MFA for users signing in with google login. Is there any way to do it other than "Require MFA"?

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

    Kafka source connector has an output format option of SimplifiedJson which is easier to parse by the downstream applications. Mongo utilities or any of the Atlas features do not support this as an output format as of now.

    Mongo does have canonical format output for mongo export which can be matched with kafka extended json format but it requires additional translation by the 3rd party applications.

    Is there a feature in place already to have atlas $out or mongo export or dump utilities to output data in Simplified json format? If not can this be looked into?

    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

    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. Change global default compressor setting

    Hello,
    I wanted to request a feature that would enable us to change the global default compressor setting ourselves? Something that could possibly be exposed on the Advanced Configuration settings page in Atlas? We're looking to re-compress our existing collections using zstd from the default snappy option and we want to create future collections using the zstd block compressor automatically.

    Today, we have to create a support ticket and co-ordinate with them. It would be great if we could have this feature on the Atlas portal so that we can monitor the progress and trigger it whenever we want to do this.

    Thanks,
    Sagar Thakur

    Hello,
    I wanted to request a feature that would enable us to change the global default compressor setting ourselves? Something that could possibly be exposed on the Advanced Configuration settings page in Atlas? We're looking to re-compress our existing collections using zstd from the default snappy option and we want to create future collections using the zstd block compressor automatically.

    Today, we have to create a support ticket and co-ordinate with them. It would be great if we could have this feature on the Atlas portal so that we can monitor the progress and trigger it whenever we want to… 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

    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

16. AWS gp3 Decouple IOPs from Disk Size

    With AWS EBS gp3 volumes, IOPs and throughput can be provisioned separately from EBS storage size. While Atlas now uses gp3 volumes and provides a base throughput of 3,000 IOPs, higher throughputs are still directly tied to disk size.

    We run IO-intensive workloads that require high throughput, and we have to severely over-size disks to get the needed throughput. We don't require the extra-low latency of provisioned IOPs (which is much more expensive than over-provisioning storage).

    According to the linked AWS documentation below, if the M60 instance size is running on an ec2 m5.4xlarge instance type, it can support a max EBS bandwidth of 593.75MB/s and 18,750 IOPs. M5.8xlarge can support 800MB/s and 30,000 IOPs. Newer generations support even higher levels. Individual EBS volumes can support up to 1,000 MB/s and 16,000 IOPs each.

    Information on AWS EBS can be found at https://aws.amazon.com/ebs/general-purpose/
    Details of EBS throughput by instance type can be found at https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-optimized.html

    With AWS EBS gp3 volumes, IOPs and throughput can be provisioned separately from EBS storage size. While Atlas now uses gp3 volumes and provides a base throughput of 3,000 IOPs, higher throughputs are still directly tied to disk size.

    We run IO-intensive workloads that require high throughput, and we have to severely over-size disks to get the needed throughput. We don't require the extra-low latency of provisioned IOPs (which is much more expensive than over-provisioning storage).

    According to the linked AWS documentation below, if the M60 instance size is running on an ec2 m5.4xlarge instance type, it can support a… 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

    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. Migrate specific collection / database from a replica set to sharded cluster(not empty) without downtime.

    It would be great if MongoDB has a tool to migrate specific collections/databases from a replica set to sharded cluster and vice versa. Migrating data with this tool should not cause any downtime in both source and destination clusters.

    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

18. Support for GCP Saudi Arabia/Dammam me-central2 for Atlas

    GCP announced availability of services in me-central2. Can MongoDB please support this region in GCP?

    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

19. List user id in access screen, needed for project owner id in when setting up a project inpulumi

    As title. I want to easily find user IDs from teh 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

    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. CORS on the Atlas API

    The Atlas API does not yet support CORS. Without CORS, calling the API from within a browser, using a React Client, for example, fails the 'preflight checks'.

    "...has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource...."

    If the Atlas API could add the 'Access-Control-Allow-Origin: *in the header response, then browsers would permit the API to be called.

    Note: for the pre-flight check, the browsers call the OPTION method.

    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