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.

update the course videos the setting up video is completely different from the current atlas environment

Using the profiler to narrow-down slow operations is great. One thing sorely missing is the ability to filter by "appName" - some of our top slow queries are from dev team working with compass or running experimental code vs the database as opposed to our main production app. We want to be able to ignore these when we perform the analysis - should be simple to implement as the metadata in the profile statistics already has a field with the desired information - "appName"

Currently the Performance Advisor features suggestions for two distinct situations:
* Queries Using regex With Case Insensitivity.
* Queries Using $lookup.

Currently the query or queries that triggered the suggestions are not shared within the Performance Advisor message which requires an extra effort in finding them either in the MongoDB Logs or using the Performance Advisor. As such, it would be useful to attach the relevant query or queries that triggered the suggestions to the Performance Advisor details.

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.

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.

can you make it so that you can connect from mongodb like you would in mongoose

Having the ability to extract/export the Performance Advisor report. This would allow users to share a file with others who may not have access to Mongo Atlas.

Currently in Atlas there is no way to test an index's performance before creation. Performance advisor provides an index impact score for suggested indexes. Requesting a feature where you can upload a proposed index and performance advisor can determine the index's impact score. This would help test an index performance before committing to a build

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/

Currently I see many queries in Profiler that the Performance Advisor is not recommending to fix.

Add an option for Atlas to automatically build indexes for slow queries instead of having to manually check slow queries and build the indexes.