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

Atlas

131 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 9 months ago in Atlas Monitoring, Alerts & Observability 1 Planned

Title: MongoDB Atlas Mobile Responsiveness Issues — Screenshots and UX Feedback Hello MongoDB Product and Engineering Team, I'm reaching out to share constructive feedback about the mobile browser experience of MongoDB Atlas. While accessing my Atlas project through an Android smartphone, I encountered several responsiveness problems that significantly affected usability. I've included screenshots demonstrating the issues. Observed problems: 1. Horizontal overflow: Important dashboard sections extend beyond the phone's viewport, leaving text and interactive elements clipped. 2. Broken button responsiveness: Buttons such as "Add Current IP Address" and "Do not show me again" become awkwardly positioned, with text wrapping excessively. 3. Unnecessary empty space: Large sections of the screen are unused while essential controls remain difficult to reach. 4. Cluster management layout: Configuration cards, actions, and information panels do not consistently adapt to narrower displays. 5. Navigation friction: Some operations require horizontal movement to access controls that should be visible within the screen. Suggested improvements: - Introduce responsive mobile layouts for dashboard and cluster management screens. - Use vertically stacked cards and actions on narrow screens. - Apply proper text wrapping and prevent viewport overflow. - Improve dialog, notification, and button responsiveness. - Test common Android and iOS viewport sizes. - Prioritize important mobile workflows such as database monitoring, project navigation, and configuration review. I understand that Atlas is a sophisticated developer platform, but I believe its core operations should remain accessible on smartphones, particularly for developers who occasionally work without a desktop computer. I'm sharing this feedback voluntarily, without seeking financial compensation, employment, or any other benefit. I hope the attached screenshots are helpful to your product and engineering teams. Thank you for your consideration.

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...
Samuel Irenikase 4 days ago in Atlas 1 Submitted

Title: Improving MongoDB Atlas responsiveness and usability on mobile browsers Hello MongoDB Product and Engineering Team, I'd like to share some constructive feedback regarding the usability of MongoDB Atlas on mobile devices. Atlas is an important tool for developers, and I believe its browser interface could become more accessible for people working from smartphones and smaller screens. Although Atlas has received significant interface improvements, I would encourage the team to review the complete mobile experience, particularly navigation, Data Explorer, database collections, monitoring dashboards, and project settings. Problem Developers sometimes need to inspect collections, monitor database activity, review alerts, or manage projects when they don't have access to a laptop. A desktop-oriented interface can make these workflows difficult on smaller displays, particularly where layouts require horizontal scrolling or complex navigation. Suggested improvements - Introduce mobile-first layouts for essential Atlas workflows. - Adapt Data Explorer's tables, filters, navigation, and document viewer for smaller screens. - Prioritize cluster health, alerts, and read-only database inspection. - Improve touch targets, menus, dialogs, and form accessibility. - Test Android and iOS browsers at common screen sizes. - Preserve existing functionality while progressively enhancing mobile support. Why this matters Improved mobile accessibility would make Atlas more convenient for developers, students, small teams, and engineers working in environments where mobile devices are sometimes their primary means of accessing online services. I'm sharing this voluntarily as constructive product feedback, without requesting compensation, employment, or any commercial arrangement. Thank you for considering the suggestion.

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...
Samuel Irenikase 4 days ago in Atlas 1 Submitted

Backup Policy based on individual Database Instead of overall cluster backup

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 do have backup policy strategy for the cluster level within the atlas MongoDB however we need to perform the backup bas...
Bathula Sai Reddy 6 months ago in Atlas Backups 1 Will Not Implement

Let mongodbatlas_advanced_cluster resource apply a disk_size_gb increase while auto_scaling.disk_gb_enabled is enabled.

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. With disk autoscaling enabled, changing disk_size_gb in terraform has no effect. The plan shows the change, apply complete...
Gabriel Stein 27 days ago in Infra-as-code & APIs 0 Future Consideration

Feature Request: Expose IOPS Utilization Percentage Metrics in Datadog Integration

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 would like to request the addition of IOPS utilization percentage metrics to the MongoDB Atlas Datadog integration.Curr...
Ariel Fernandez 8 days ago in Atlas Monitoring, Alerts & Observability 0 Submitted
195 VOTE

Autoscaling with custom conditions to scale up( change 1 hour to adjustable time) or down(change fixed 24 hours to adjustable time)

Currently autoscaling is predefined with conditions like scale up: The Average CPU Utilization has exceeded 75% for the past hour. The Memory Utilization has exceeded 75% for the past hour. scale down: The average CPU Utilization and Memory Util...
Guest over 4 years ago in Atlas 9 Submitted
288 VOTE

Ability to stream logs to Cloudwatch Logs/Datadog/Splunk

There's no way to stream logs from MongoDB on Atlas right now. I should be able to stream logs, either to Datadog or Cloudwatch or _something_!
Guest almost 7 years ago in Atlas 55 Started

Hello, I accidentally deleted the cluster around 10:30 today. I hope to help reply to the data. This is very important. Thank you.

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. Hello, I accidentally deleted the cluster around 10:30 today. I hope to help reply to the data. This is very important. Th...
fengyuan si 13 days ago in Online Archive 0 Submitted

Option to get rid of Redundant Indexes - After a cluster restart, the recommendations go away from perf advisor.

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. Performance Advisor’s “Drop Index” recommendations for redundant indexes disappear after a cluster restart (or any mongod ...
RuthvikReddy Anumasu about 1 month ago in Atlas 0 Future Consideration