Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

ADD NEW FEEDBACK

All feedback

Showing 4030 of 4030

Alarm on potential data breach events

Provide capability to raise alarms on specific events like mongodump, mongoexport (eventually mongorestore, mongoimport)
Guest over 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

Removing a connection needs to show you a confirmation dialog

Removing a connection needs to show you a confirmation dialog
Guest over 1 year ago in Compass & Data Explorer 0 Submitted

Use node modules in Functions

As far as I understand currently it is not possible to use node/npm modules is Functions. Would be great to have it.
Guest almost 8 years ago in Atlas Triggers and Functions 1 Started

Safe mode to pause non-essential changes

I'd like to be able to put the cluster into a "Safe Mode" during an incident. For example, I'm responding to an incident or I suspect something's fragile or breaking, and I don't want any scheduled activities to make it worse or distract me. I al...
Guest about 2 years ago in Infra-as-code & APIs 0 Submitted

MongoDB should have a database backup system commit base for large self-management databases, like git commit.

There is already a mongodb backup tool mongodump but it is not a good solution for backing up large databases. We thought of making a CMS Platform with mongodb. Billions of websites can be created there. For such a large platform, the mongodump ba...
Guest over 1 year ago in Backup & Restore 1 Submitted

Ops Manager API - System Alerts

The ops manager api documentation specifies endpoints for polling group alerts and global alerts but is missing system alerts. We should be able to poll for system alerts via the ops manager api as well.
Jacob Bills about 5 years ago in Enterprise Advanced 1 Submitted

Backup persistence after termination should be standard

It is odd that snapshots are tied to clusters and lost/destroyed when clusters are terminated. Snapshots have their own retention policies for a reason. Persistence after cluster termination should be the rule, not the exception.
Guest over 2 years ago in Atlas Backups 0 Submitted

I don't even know what my username is. It displayed briefly, I copied the password, and then both the username and password disappeared!

Fix this mess!!!!
Guest 5 months ago in Atlas 0 Submitted

Identification of unused/less used collections

As a DBA I'd like to identify unused collections so that I can remove them to optimize performance. As of now there doesn’t seem to be a direct way. One option could be to settup auditing or using logging (e.g. set the slow op timer to 0 so we log...
Guest over 4 years ago in Database 1 Submitted

Per-Shard Triggers to improve scalable/performance/resilience

In our geo-sharded cluster, we use Change Streams and Atlas Triggers. Most of our pipelines include an exact match for the shard key - so we can process the data in the same region where the data resides. However, due to the design of change str...
Boris Figovsky 5 months ago in Atlas Triggers and Functions 0 Submitted