Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
4 results found
-
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 votesThe Atlas Query Profiler now retains slow queries for 7 days. By default when you navigate to the Query Profiler, we show 24 hour lookback. However, you can use the "Time Range" dropdown to look back 7 days.
-
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 votesWe've recently launched Query Shape Insights which groups queries by shape. For more information, please see our documentation here.
-
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 voteThe Atlas query profiler now consolidates all slow operations across the cluster on a single page. You can then filter down on individual shards or nodes from the filter sections.
-
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 voteThe Query Profiler and the Performance Advisor is Atlas now consolidate all queries in a single view but also give users the ability to filter down to primary or secondary nodes.
- Don't see your idea?