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

Feedback

Show driver/application/user metadata in Query Profiler query summaries

It would be helpful if the Query Profiler showed the driver and user metadata associated with the connection over which a particular query was run. After clicking on a particular plotted operation in the Query Profiler, the sidebar pops up and s...
Marie Atterbury almost 6 years ago in Atlas Monitoring, Alerts & Observability 3 Submitted

Allow Pinning Query Plan Cache Key to a Fixed Plan for a Given Query Shape Hash

Allow Pinning Query Plan Cache Key to a Fixed Plan for a Given Query Shape Hash n MongoDB 8.0, the new setQuerySettings command allows administrators to enforce index hints and other behavior based on the query shape hash. This gives users partia...
Vinicius Grippa 8 months ago in Querying & Aggregations 0 Submitted

Allow configuration of 100mb memory limit per aggregation pipeline stage

In this old thread from 2016 (https://groups.google.com/forum/#!topic/mongodb-user/LCeFZZRz5EY) it was asked whether there was a way to increase the 100mb in memory limit of each stage of an aggregation pipeline. The responses centered around two ...
Guest about 6 years ago in Querying & Aggregations 2 Submitted

Add operator that would calculate distance between 2 geolocation points

It would be great to have operator that would calculate distance between 2 geolocation points, and not to do it manually with big aggregate queries. I suggest to add 2 new operators that would calculate distance in two different ways, as discuss...
Guest almost 4 years ago in Querying & Aggregations 3 Submitted

Export Aggregation Results as Metrics to Prometheus

Add support for exporting MongoDB aggregation results as Prometheus metrics. This would allow users to track custom queries and dynamic data, enabling more granular and meaningful monitoring and alerting in Prometheus and Grafana.
Guest over 1 year ago in Atlas Monitoring, Alerts & Observability 0 Submitted

Implement a $hash operator for queries

Current State: MongoDB currently lacks a native $hash operator in the aggregation/query language. While certain helpers like convertShardKeyToHashed or $toHashedIndexKey exist, they are limited in scope: Not available as true query operators (e....
Guest 9 months ago in Querying & Aggregations 0 Submitted

Improve "Host has index suggestions" alert by including the database name and collection name

The "Host has index suggestions" alert notification does not contain any reference to the database or collection that triggered it making it hard to figure out where it came from. A hostname reference would be very helpful. https://www.mongodb.co...
Guest about 1 year ago in Atlas Monitoring, Alerts & Observability 0 Submitted

show aggregate cpu utilization on the cluster metrics "Normalized System CPU" chart

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. Aggregate CPU utilization % is the most important CPU metric, because it determines if/when you've exhausted your CPU capa...
Alex T 5 months ago in Atlas Monitoring, Alerts & Observability 1 Future Consideration

Generative AI and Smart Automation should be a key priority. MongoDB Atlas could significantly improve developer productivity by introducing AI-assisted query optimization that doesn’t just flag inefficient queries, but actively rewrites them into optimized alternatives. Automated index recommendations based on real workload telemetry would help teams make better performance decisions without deep manual analysis. Additionally, bot-assisted support workflows could speed up issue resolution by guiding users through diagnostics and common fixes more efficiently. Together, these capabilities would provide strong competitive differentiation while improving operational efficiency for both developers and platform teams.

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. Teams struggle to proactively identify and fix performance issues in MongoDB workloads. Query inefficiencies, missing or s...
Spideyyy N/A 2 months ago in Atlas Monitoring, Alerts & Observability / Data Modeling & Indexing / Performance & Optimization 1 Future Consideration

Show latest document first instead of first document, in list

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...
Profit Buddy AI 2 months ago in Performance & Optimization / Querying & Aggregations 1 Future Consideration