Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
35 results found
-
profiler - add filter by "appName"
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"
16 votes -
Enhancing Performance Advisor
Identify MongoDB Connection Users: Display which MongoDB connection users generated the queries listed in the index proposals. For instance, avoid creating indexes for queries originating from Atlas UI and MongoDB Compass.
Respect Custom Collation: Ensure that Performance Advisor respects custom collation settings. When creating an index from Performance Advisor, it should automatically include the custom collation options. Currently, these options are left empty, leading to potential negative impacts rather than improvements.
8 votes -
Performanse advisor node type filter (to exclude analytics)
Performance Advisor should allow selecting node types to exclude analytics nodes.
In most cases, analytics queries don't require indexes as queries are very different and might be filtered by any field.
6 votes -
Rejecting Index Suggestions
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.
6 votes -
Global overview of Index Suggestions
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.
5 votes -
Allow Performance Advisor reporting export
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.
5 votes -
kill process for rolling index build from atlas
If index builds are rolling, then the Atlas console does not have the functionality to kill them if they take a longer time on a node. Is it possible to kill it like regular index creation from atlas UI instead raising a ticket to mongo
4 votes -
Should give download CSV option for getting all the slow queries details
It will be better if a have an option to download all the slow query related information as whatever we see in the Atlas UI.
4 votes -
Recommendation to the change the tier cluster
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.
4 votes -
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.
4 votes -
Determine index's impact score before creating
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
4 votes -
increasing the data retention of slow queries to a week.
Currently atlas storing only 24 hours data for slow queries in Profiler. If it enable for a week atleast it will be very helpful for users to track the slow queries in the last week by sorting the query execution time.
3 votes -
View TOP N queries per CPU / memory / disk and number of execution for each query.
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.
3 votes -
Performance Advisor Case Insensitive Queries and $lookup Recommendations - Include Relevant Queries
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.
3 votes -
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 -
Order the slow queries by shape
We are trying to use the API to get slow queries from a given cluster. Today, each line represents a single command, but it would be very usefull if we could group it by command shape. This way we could for example group it and filter by average running time, so we could simply get the most expensive queries despite the query data.
2 votes -
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…
2 votes -
Improve Atlas suggested indexes
Suggested indexes
- Currently it will suggest indexes that can't be created, such as with multiple array fields.
-- This should be detectable before suggesting an index.
-- Highlight array fields in the suggested index
- Include partial index expressions
- Make more than one suggestion for queriesTrying to create an index that contains multiple array fields (for some documents being indexed) won't fail until it hits one such document.
- Pre-parse to first confirm the fields being indexed don't include more than 1 array for the index?
- Pre-parse and inform the user if any of the fields…2 votes -
API for slowQueryLogs should give response in a proper json format like in UI
API for slowQueryLogs should give response in a proper json format like in UI rather than giving raw logs
2 votes -
Show queries that exceeded maxTimeMs in the Atlas Profiler
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!
2 votes
- Don't see your idea?