Glad you found it helpful. Thanks for your comment.
@kirangelli9 ай бұрын
Thank you for this Informative session on MongoDB Atlas. Couple of questions... How will the Atlas know the slow running queries? Will the Profiling be enabled by default in Atlas? Also, in PMM-QAN we can't get the execution plan for the queries that use aggregation pipeline (limitation of PMM) In Atlas, is there a option to get the execution plans for the slow queries? Only 48 hours data retention is a limitation here.
@Mydbops9 ай бұрын
Thrilled to know that you have enjoyed our database contents. Here is the reply from MongoDB Expert Manosh Malai. How will the Atlas know the slow-running queries? MongoDB Atlas detects slow-running queries using MongoDB's database profiler, which tracks queries exceeding a specific execution time threshold, typically set to 100 milliseconds by default. Will the Profiling be enabled by default in Atlas? Yes, For M0, M2, and M5 clusters and serverless instances, Atlas disables the Atlas-managed slow query operation threshold by default and you can't enable it. Also, in PMM-QAN we can't get the execution plan for the queries that use aggregation pipeline (limitation of PMM) In Atlas, is there an option to get the execution plans for the slow queries? By default, MongoDB Atlas will share the execution plans for the slow query. How far can we check the metrics? The snapshots on metrics retention were made pictorially on the recording. kzbin.info/www/bejne/h5bGpWiweNmjrZIfeature=shared&t=1967 Is there an option to store the data for the past 1 month? We can Integrate with Prometheus to store the metrics longer time www.mongodb.com/docs/atlas/tutorial/prometheus-integration/#:~:text=Prometheus%20collects%20metrics%20from%20configured,deployment%20to%20your%20Prometheus%20instance