All feedback

Showing 3945 of 3945

Add line number to function call error messages

A simple line number of where a function fails would be incredibly useful. And a function name would be important too for when a function calls another function.

Guest about 5 years ago in Atlas Triggers and Functions 3 Submitted

14 VOTE

More detail and lead time around maintenance notifications

When we get email notifications of upcoming maintenances, it doesn't specify if the update is "urgent" or "low". When we received our last notice, it was 3 days out. If it's urgent, then we understand the short time frame around the notice. Howeve...

Guest about 6 years ago in Atlas 5 Submitted

13 VOTE

Burstable IOPS for MongoDB Atlas on Azure

According to Azure documentation, bursting is enabled by default for all VMs that using Premium SSD (https://docs.microsoft.com/en-us/azure/virtual-machines/linux/disks-types#bursting). It would be great if MongoDB Atlas on Azure can get benefit f...

Guest over 5 years ago in Database 0 Submitted

2 VOTE

Rename Database function

Subject: Feature Request: Add Support for Renaming a Database Dear MongoDB Team, I appreciate the great work you’ve done with MongoDB—it’s a fantastic database solution that continues to evolve and improve. However, I would like to suggest a fea...

Guest 11 months ago in IDEs 0 Submitted

9 VOTE

Remove user data from survey

You ask for personal data on both the testimonial and the group at the end of each survey. We are not allowed to provide feedback by corporate. Having the name and email link is worrisome. If a person selects no you need to not ask for that data. ...

Guest almost 4 years ago in Education 1 Future Consideration

2 VOTE

Enhance MongoDB Documentation on Schema Validation Impact on Write Operations

MongoDB documentation should clearly explain how schema validation affects write operations, including bulkWrite, insertOne, insertMany, updateOne, and updateMany. Key improvements: Performance Impact – Detail validation overhead on write latency...

Guest 11 months ago in Documentation 0 Future Consideration

8 VOTE

Support Azure Blob Storage in addition to AWS S3 for Online Archive

Currently, there is only one option to store the archive data and that is in AWS S3 buckets. We have contractual obligations with clients to store data in Azure. It would be great if MongoDB gave an Azure alternative to AWS S3 like Azure Blob Stor...

Guest over 3 years ago in Atlas Backups 4 Submitted

13 VOTE

billing

The billing invoice is split by project. If we have multiple team in the same project, it a puzzle. We need to bill by cluster in this case.

Guest over 5 years ago in Billing & Account Management 4 Submitted

12 VOTE

Live Migrate modal: Allow users to point and click to select another Atlas source cluster

It is often practical to Live Migrate from one Atlas cluster to another Atlas cluster (e.g. to create another staging environment if backups are not enabled on the source, or migrate a production/staging environment to another dedicated project wi...

Marie Atterbury about 5 years ago in Atlas 0 Submitted

2 VOTE

Expose hourly cost data as a metric for monitoring cluster cost

The hourly cost of a cluster is already availble in the Atlas UI. Expose this same data as a metric for monitoring cluster cost. We understand it may not include the data transfer and some other costs but monitoring the spike or valleys in the mon...

Guest 11 months ago in Atlas Monitoring, Alerts & Observability 0 Submitted

Please enter your email address

FILTER BY CATEGORY