Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
27 results found
-
Increase # of Collections in Performance Advisor
Currently the recommendations are for the 20 most active collections. It would be helpful if there was an option to run this for all collections or to set a larger number of collections.
3 votes -
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 -
Use rolling index build by default
We added a few indexes and support mentioned it is not advisable to use the backgroud option when adding an index yet this isthe default setting iwhen adding an index in the performance advisor
https://docs.mongodb.com/manual/tutorial/build-indexes-on-replica-sets/3 votes -
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 -
Allow adjustable sensitivity
Currently I see many queries in Profiler that the Performance Advisor is not recommending to fix.
1 vote
- Don't see your idea?