Some Index Suggestions don't work. The Performance Advisor doesn't sample data, and therefore can not predict if some field is worthwhile in an index or not (e.g. some fields may contain the same value for all documents).

If we decide to not apply the Index Suggestion, or we apply it, test it, and remove the Index again because it's not being used by MongoDB, the Index Suggestion is still showing up. It can also trigger alerts.

Please add the possibility to reject an index suggestion, so that it's hidden from the UI and can not trigger alerts.

We run more than 60 clusters today on Atlas, and will probably hit 100 clusters in the foreseeable future.

The Index Suggestion alerts are not dependable for us (see https://feedback.mongodb.com/forums/924145-atlas/suggestions/44243568-better-alert-trigger-for-index-suggestions ).

Going through many clusters manually to check them for Index Suggestions is an extremely time-consuming process. We would like to have a global overview of all open Index Suggestions, or at least an overview on a project-basis.

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 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

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.

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.

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/

Based on CPU and memory usage metrics over a certain period of time, a recommendation could be made to change the cluster tier to a higher or lower one (inform which cluster it would be recommended to change to) and notify through some channel, such as eg email/slack.

This type of metric is common in relational databases and I think it's important to deploy in the Atlas interface.

Top queries by CPU/memory and disk over a period of time or real time. It is important to have this visibility and improve the respective query(s).

It is good to know how many times each query was executed during the respective analyzed period.

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

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.

We had some queries hit the maxTimeMS and fail. We had to download the log files for visibility into those errors. That is info that we would love to see in the Profiler!

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.

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.

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

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.