Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
36 results found
-
Allow user to be able to download queries in Query Insights. Also a search bar in Query Insights to find certain queries
Allow user to be able to download queries in Query Insights would be nice. Also a search bar in Query Insights to find certain queries. Clicking through each operation to look at each query takes too much time. I want to be able to search any queries with any specific criteria so I don't have to click on each one to check for collection or index scan or duration time etc.
1 vote -
AI Driven recommendations & chatbot
My customer is requesting if it is possible to add AI chatbot or AI generated cluster sizing recommendations, similar to what GCP has in their logging tools. They provided the feedback that looking at metrics can be tedious and they want the ability to ask a chatbot what it means and have the chatbot make sizing recommendations based on this.
1 vote -
Atlas Profiler could add readConcern and greater granularity for Commands such as say, FIND or INSERT etc.
It would be nice to be able to filter the content of the profiler in the Atlas GUI.
The profiler has proved to be very useful and maybe it could be even better.Currently you can only filter by "Top namespace operations"; and it would be nice to also filter by:
readConcern: this is because the ones hitting a secondary node are usually not a concern to me. They tend to be ad hoc queries which do not always have a supporting index and that is ok.
Also, when Operation = command, it could actually be many things. It might…1 vote -
Allow entering the time values directly by editing the text instead of keyboard arrows
When you want to filter a custom date and time range, you need to use the arrow keys on the keyboard to scroll through the hours, and minutes. This is annoying and inefficient. Let me type it in please. Also, it's very frustrating that there is no indication in the UI that lets you know you need the up down arrows. I had to connect with a support person to find this out.
Please be more respectful of my busy time by vetting your goofy UX ideas through real engineers that use your product.
1 vote -
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.
9 votes -
Atlas should have availability report
Hi Team,
If Atlas generate availability report which show overall all cluster and project heath status on the one page then it will be nice to present in-front of the non-technical member.
Thanks
Sonu0 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.
7 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 -
Profiler: expose the dashboard ID and chart ID from which the query is originating
My MongoDB analytics node performance is decreasing.
Looking at the profiler it seems that some specific queries are super slow.
I can see the full query, I can see that they originate from MongoDB charts ("appName": "atlas-data-federation|app-services|xxxxx").
But I cannot see which dashboard ID and which specific chart ID this query is originating from.
So I cannot, for example, easily find which chart to delete.Is this something you could help with? or any work around?
thanks!1 vote -
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 -
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 -
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
5 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 -
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.
5 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 -
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 -
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 -
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 -
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.
5 votes
- Don't see your idea?