Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
30 results found
-
Tuning of Performance Advisor
Give users the option to modify the guidelines by which Performance Advisor provides its suggestion. A way for customers to input context so that Performance Advisor can give better suggestions
Customers have been commenting that Performance Advisor suggestions are too aggressive at times for things such as creating/dropping indexes. They note that the frequency that they query something Performance Advisor suggests creating doesn't warrant the memory usage it would take to create that index. On the other hand, they may not use an index frequently, so Performance Advisor suggests dropping the index, but that item is critical to their application…
1 vote -
better index usage
Currently most of our indexes show a usage of <1/min which isn't very useful. If I hover over them I can see the usage which might say 20/day but I would prefer to not have to hover.
1 vote -
1 vote
-
Always show shard name on cluster's profiler page
On a cluster’s detail page, there is the Profiler tab. If you click on that, you are brought to the slow query profiler page. What’s not apparent from this view is that this page is not scoped to be cluster wide, but instead is scoped just to the primary mongo node. If you go back to the Overview tab, click on a specific shard on the left and then go to the profiler tab, you see how now, the title is shard specific and truly shows what you’re looking at? Please always display this shard name regardless of the breadcrumb…
1 vote -
Applying an index suggestion should remove redundant indices automatically
An index suggestion for a compound index should check if it makes an existing index redundant. If so, it should remove it automatically after adding the compound index, or at least add the option to do so.
1 vote -
profiler - allow for separation of primary vs. secondary queries
We have our production applications using the primary connection. Our support and ad-hoc queries are going against the secondary connection. I would like for these secondary queries to not interfere with or be able to selectively exclude these queries from the profile. Same goes for performance advisor. Performance Advisor will indicate queries are needed do to some support queries when they are not needed or only needed for a short time.
1 vote -
Provide insight to slow queries on shared instances (like M5)
Currently, features to give insight to slow/optimisable queries are only supported on non-shared instances (i.e. M10+). Would like to see this for shared instances too.
On a side note, this was possible in the cheaper mlab.com setup, which was forced into Atlas.
1 vote -
code
can you make it so that you can connect from mongodb like you would in mongoose
1 vote -
Allow adjustable sensitivity
Currently I see many queries in Profiler that the Performance Advisor is not recommending to fix.
1 vote -
Auto-build indexes for slow-queries
Add an option for Atlas to automatically build indexes for slow queries instead of having to manually check slow queries and build the indexes.
1 vote
- Don't see your idea?