{"id":11093,"date":"2019-03-27T06:14:09","date_gmt":"2019-03-27T06:14:09","guid":{"rendered":"https:\/\/dbtut.com\/?p=11093"},"modified":"2019-03-27T06:35:31","modified_gmt":"2019-03-27T06:35:31","slug":"enabling-profiling-in-mongodb","status":"publish","type":"post","link":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/","title":{"rendered":"Enabling Profiling in MongoDB"},"content":{"rendered":"<p><span style=\"font-family: arial, helvetica, sans-serif\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0 \u00a0Database should have very good performance for the better production.To have better performance its necessary to optimize the long running queries which degrade the database.Is it possible to trace slow queries in MongoDB?How can we trace out the long running queries? Similar to the slow query log in the mysql,the mongodb supports a feature called Profiling.The database profiler collects fine grained data about MongoDB write operations, cursors, database commands on a running mongod instance.There are different levels in Profiling each serving a unique pattern.<\/span><\/p>\n<p><span style=\"font-family: arial, helvetica, sans-serif\"><strong>Database Profiling Levels:<\/strong><\/span><\/p>\n<p><span style=\"font-family: arial, helvetica, sans-serif\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 The mongodb database profiling mainly involves three levels such as Level 0,Level 1,Level 2.<\/span><\/p>\n<ul style=\"list-style-type: disc\">\n<li><span style=\"font-family: arial, helvetica, sans-serif\"><strong>Level 0\u00a0:<\/strong> This is the first level in database profiling which means that the profiler is set off.It does not contain any data.<\/span><\/li>\n<li><strong style=\"font-family: arial, helvetica, sans-serif;font-size: 1.125rem\">Level 1:<\/strong><span style=\"font-family: arial, helvetica, sans-serif;font-size: 1.125rem\"> This level means that it is meant to trace the slow queries.It has a default value of tracing queries running more than 100 milliseconds.<\/span><\/li>\n<li><strong style=\"font-family: arial, helvetica, sans-serif;font-size: 1.125rem\">Level 2:<\/strong><span style=\"font-family: arial, helvetica, sans-serif;font-size: 1.125rem\"> This level means that it will trace all the database queries.In the production it will surely affect the performance.So based on your requirement you can choose the level of profiling that is to be initiated in the database.<\/span><\/li>\n<\/ul>\n<p><strong><span style=\"font-family: arial, helvetica, sans-serif\">Enabling Database Profiling:<\/span><\/strong><\/p>\n<p><span style=\"font-family: arial, helvetica, sans-serif\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 By default the profiler will be disabled in the system.To set the profiler in the database make sure that you login as the root user with required privileges.Now issue the below command with the profiling level:<\/span><\/p>\n<pre class=\"lang:js decode:true\">db.setProfilingLevel(1)<\/pre>\n<p><span style=\"font-family: arial, helvetica, sans-serif\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 The above command will enable the database profiling and trace only the slow queries more than 100 milliseconds since its defined for Level 1.<\/span><\/p>\n<pre class=\"lang:js decode:true\">db.setProfilingLevel(2)<\/pre>\n<p><span style=\"font-family: arial, helvetica, sans-serif\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 This command will tend to log all the queries that are involved in the operation.Yeah,its also possible to trace the queries running more than some \u2018x\u2019 seconds.To trace the slow queries that running more than 500 milliseconds then follow the below command:<\/span><\/p>\n<pre class=\"lang:js decode:true\">db.setProfilingLevel(1,500)<\/pre>\n<p><span style=\"font-family: arial, helvetica, sans-serif\">\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Similarly the seconds can be varied based on the user input.Once the database profiler is enabled then there will be automatic creation of a collection named system.profile in the admin database.You can also view the slow queries by issuing the below query in the admin database:<\/span><\/p>\n<pre class=\"lang:js decode:true\">db.system.profile.find()<\/pre>\n<p><span style=\"font-family: arial, helvetica, sans-serif\">To sort by natural order (time in) then fire the below query:<\/span><\/p>\n<pre class=\"lang:js decode:true\">db.system.profile.find({}).sort({$natural:-1})<\/pre>\n<p><span style=\"font-family: arial, helvetica, sans-serif\">So in order to sort by slow queries first fire the below query:<\/span><\/p>\n<pre class=\"lang:js decode:true\">db.system.profile.find({}).sort({$millis:-1})Alimit(10);<\/pre>\n<p><span style=\"font-family: arial, helvetica, sans-serif\">To view queries running greater than \u2018x seconds try:<\/span><\/p>\n<pre class=\"lang:js decode:true\">db.system.profile.find({\"millis\":{$gt:x}})\u2019<\/pre>\n<p><span style=\"font-family: arial, helvetica, sans-serif\">To trace slow queries with specific namespace fire the below query:<\/span><\/p>\n<pre class=\"lang:js decode:true\">db.system.profile.find( { \"ns\": \/db.coll\/ } ).sort({millis:-1,$ts:-1})<\/pre>\n<p><strong><span style=\"font-family: arial, helvetica, sans-serif\">Checking current profiler level:<\/span><\/strong><\/p>\n<p><span style=\"font-family: arial, helvetica, sans-serif\">Its also easy to check the current database profiling level by issuing the below command:<\/span><\/p>\n<pre class=\"lang:js decode:true \">db.getProfilingLevel()<\/pre>\n<p><span style=\"font-family: arial, helvetica, sans-serif\">Yeah we are done in tracing the slow queries.Go ahead, it\u2019s now time to hunt the poor performing queries and optimise them.<\/span><\/p>\n<div class=\"pvc_clear\"><\/div>\n<p id=\"pvc_stats_11093\" class=\"pvc_stats all  \" data-element-id=\"11093\" style=\"\"><i class=\"pvc-stats-icon medium\" aria-hidden=\"true\"><svg aria-hidden=\"true\" focusable=\"false\" data-prefix=\"far\" data-icon=\"chart-bar\" role=\"img\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 512 512\" class=\"svg-inline--fa fa-chart-bar fa-w-16 fa-2x\"><path fill=\"currentColor\" d=\"M396.8 352h22.4c6.4 0 12.8-6.4 12.8-12.8V108.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v230.4c0 6.4 6.4 12.8 12.8 12.8zm-192 0h22.4c6.4 0 12.8-6.4 12.8-12.8V140.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v198.4c0 6.4 6.4 12.8 12.8 12.8zm96 0h22.4c6.4 0 12.8-6.4 12.8-12.8V204.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v134.4c0 6.4 6.4 12.8 12.8 12.8zM496 400H48V80c0-8.84-7.16-16-16-16H16C7.16 64 0 71.16 0 80v336c0 17.67 14.33 32 32 32h464c8.84 0 16-7.16 16-16v-16c0-8.84-7.16-16-16-16zm-387.2-48h22.4c6.4 0 12.8-6.4 12.8-12.8v-70.4c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v70.4c0 6.4 6.4 12.8 12.8 12.8z\" class=\"\"><\/path><\/svg><\/i> <img loading=\"lazy\" decoding=\"async\" width=\"16\" height=\"16\" alt=\"Loading\" src=\"https:\/\/dbtut.com\/wp-content\/plugins\/page-views-count\/ajax-loader-2x.gif\" border=0 \/><\/p>\n<div class=\"pvc_clear\"><\/div>\n","protected":false},"excerpt":{"rendered":"<p>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0 \u00a0Database should have very good performance for the better production.To have better performance its necessary to optimize the long running queries which degrade the database.Is it possible to trace slow queries in MongoDB?How can we trace out the long running queries? Similar to the slow query log in the mysql,the mongodb supports a &hellip;<\/p>\n<div class=\"pvc_clear\"><\/div>\n<p id=\"pvc_stats_11093\" class=\"pvc_stats all  \" data-element-id=\"11093\" style=\"\"><i class=\"pvc-stats-icon medium\" aria-hidden=\"true\"><svg aria-hidden=\"true\" focusable=\"false\" data-prefix=\"far\" data-icon=\"chart-bar\" role=\"img\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 512 512\" class=\"svg-inline--fa fa-chart-bar fa-w-16 fa-2x\"><path fill=\"currentColor\" d=\"M396.8 352h22.4c6.4 0 12.8-6.4 12.8-12.8V108.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v230.4c0 6.4 6.4 12.8 12.8 12.8zm-192 0h22.4c6.4 0 12.8-6.4 12.8-12.8V140.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v198.4c0 6.4 6.4 12.8 12.8 12.8zm96 0h22.4c6.4 0 12.8-6.4 12.8-12.8V204.8c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v134.4c0 6.4 6.4 12.8 12.8 12.8zM496 400H48V80c0-8.84-7.16-16-16-16H16C7.16 64 0 71.16 0 80v336c0 17.67 14.33 32 32 32h464c8.84 0 16-7.16 16-16v-16c0-8.84-7.16-16-16-16zm-387.2-48h22.4c6.4 0 12.8-6.4 12.8-12.8v-70.4c0-6.4-6.4-12.8-12.8-12.8h-22.4c-6.4 0-12.8 6.4-12.8 12.8v70.4c0 6.4 6.4 12.8 12.8 12.8z\" class=\"\"><\/path><\/svg><\/i> <img loading=\"lazy\" decoding=\"async\" width=\"16\" height=\"16\" alt=\"Loading\" src=\"https:\/\/dbtut.com\/wp-content\/plugins\/page-views-count\/ajax-loader-2x.gif\" border=0 \/><\/p>\n<div class=\"pvc_clear\"><\/div>\n","protected":false},"author":98,"featured_media":11094,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[1324,1306,1388],"tags":[1371,2766,1380],"class_list":["post-11093","post","type-post","status-publish","format-standard","has-post-thumbnail","","category-big-data","category-mongodb","category-nosql","tag-mongodb","tag-mongodb-features","tag-mongodb-performance"],"aioseo_notices":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v24.9 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Enabling Profiling in MongoDB - Database Tutorials<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Enabling Profiling in MongoDB - Database Tutorials\" \/>\n<meta property=\"og:description\" content=\"\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0 \u00a0Database should have very good performance for the better production.To have better performance its necessary to optimize the long running queries which degrade the database.Is it possible to trace slow queries in MongoDB?How can we trace out the long running queries? Similar to the slow query log in the mysql,the mongodb supports a &hellip;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/\" \/>\n<meta property=\"og:site_name\" content=\"Database Tutorials\" \/>\n<meta property=\"article:author\" content=\"http:\/\/in.linkedin.com\/in\/jerwinroy\/\" \/>\n<meta property=\"article:published_time\" content=\"2019-03-27T06:14:09+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2019-03-27T06:35:31+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/03\/mongo-slow.png\" \/>\n\t<meta property=\"og:image:width\" content=\"491\" \/>\n\t<meta property=\"og:image:height\" content=\"270\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Jerwin Roy\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@https:\/\/twitter.com\/JerwinRoy\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jerwin Roy\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/\"},\"author\":{\"name\":\"Jerwin Roy\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/1392289282fd1b53969104d8b35e8ff3\"},\"headline\":\"Enabling Profiling in MongoDB\",\"datePublished\":\"2019-03-27T06:14:09+00:00\",\"dateModified\":\"2019-03-27T06:35:31+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/\"},\"wordCount\":443,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/03\/mongo-slow.png\",\"keywords\":[\"MongoDB\",\"MongoDB features\",\"MongoDB performance\"],\"articleSection\":[\"Big Data\",\"MongoDB\",\"NoSQL\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/\",\"url\":\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/\",\"name\":\"Enabling Profiling in MongoDB - Database Tutorials\",\"isPartOf\":{\"@id\":\"https:\/\/dbtut.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/03\/mongo-slow.png\",\"datePublished\":\"2019-03-27T06:14:09+00:00\",\"dateModified\":\"2019-03-27T06:35:31+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#primaryimage\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/03\/mongo-slow.png\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/03\/mongo-slow.png\",\"width\":491,\"height\":270},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/dbtut.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Enabling Profiling in MongoDB\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/dbtut.com\/#website\",\"url\":\"https:\/\/dbtut.com\/\",\"name\":\"Database Tutorials\",\"description\":\"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux\",\"publisher\":{\"@id\":\"https:\/\/dbtut.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/dbtut.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/dbtut.com\/#organization\",\"name\":\"dbtut\",\"url\":\"https:\/\/dbtut.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"contentUrl\":\"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg\",\"width\":223,\"height\":36,\"caption\":\"dbtut\"},\"image\":{\"@id\":\"https:\/\/dbtut.com\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/1392289282fd1b53969104d8b35e8ff3\",\"name\":\"Jerwin Roy\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/dbtut.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/d362cb6ec946a7bccb4b53862e8f9ca8ba82af0fd90473fd743597321ce62e6e?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/d362cb6ec946a7bccb4b53862e8f9ca8ba82af0fd90473fd743597321ce62e6e?s=96&d=mm&r=g\",\"caption\":\"Jerwin Roy\"},\"description\":\"Aspiring DBA\",\"sameAs\":[\"http:\/\/in.linkedin.com\/in\/jerwinroy\/\",\"https:\/\/x.com\/https:\/\/twitter.com\/JerwinRoy\"],\"url\":\"https:\/\/dbtut.com\/index.php\/author\/jerwinroy\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Enabling Profiling in MongoDB - Database Tutorials","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/","og_locale":"en_US","og_type":"article","og_title":"Enabling Profiling in MongoDB - Database Tutorials","og_description":"\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0 \u00a0Database should have very good performance for the better production.To have better performance its necessary to optimize the long running queries which degrade the database.Is it possible to trace slow queries in MongoDB?How can we trace out the long running queries? Similar to the slow query log in the mysql,the mongodb supports a &hellip;","og_url":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/","og_site_name":"Database Tutorials","article_author":"http:\/\/in.linkedin.com\/in\/jerwinroy\/","article_published_time":"2019-03-27T06:14:09+00:00","article_modified_time":"2019-03-27T06:35:31+00:00","og_image":[{"width":491,"height":270,"url":"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/03\/mongo-slow.png","type":"image\/png"}],"author":"Jerwin Roy","twitter_card":"summary_large_image","twitter_creator":"@https:\/\/twitter.com\/JerwinRoy","twitter_misc":{"Written by":"Jerwin Roy","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#article","isPartOf":{"@id":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/"},"author":{"name":"Jerwin Roy","@id":"https:\/\/dbtut.com\/#\/schema\/person\/1392289282fd1b53969104d8b35e8ff3"},"headline":"Enabling Profiling in MongoDB","datePublished":"2019-03-27T06:14:09+00:00","dateModified":"2019-03-27T06:35:31+00:00","mainEntityOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/"},"wordCount":443,"commentCount":0,"publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/03\/mongo-slow.png","keywords":["MongoDB","MongoDB features","MongoDB performance"],"articleSection":["Big Data","MongoDB","NoSQL"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/","url":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/","name":"Enabling Profiling in MongoDB - Database Tutorials","isPartOf":{"@id":"https:\/\/dbtut.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#primaryimage"},"image":{"@id":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#primaryimage"},"thumbnailUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/03\/mongo-slow.png","datePublished":"2019-03-27T06:14:09+00:00","dateModified":"2019-03-27T06:35:31+00:00","breadcrumb":{"@id":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#primaryimage","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/03\/mongo-slow.png","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2019\/03\/mongo-slow.png","width":491,"height":270},{"@type":"BreadcrumbList","@id":"https:\/\/dbtut.com\/index.php\/2019\/03\/27\/enabling-profiling-in-mongodb\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/dbtut.com\/"},{"@type":"ListItem","position":2,"name":"Enabling Profiling in MongoDB"}]},{"@type":"WebSite","@id":"https:\/\/dbtut.com\/#website","url":"https:\/\/dbtut.com\/","name":"Database Tutorials","description":"MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux","publisher":{"@id":"https:\/\/dbtut.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/dbtut.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/dbtut.com\/#organization","name":"dbtut","url":"https:\/\/dbtut.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/","url":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","contentUrl":"https:\/\/dbtut.com\/wp-content\/uploads\/2021\/02\/dbtutlogo.jpg","width":223,"height":36,"caption":"dbtut"},"image":{"@id":"https:\/\/dbtut.com\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/dbtut.com\/#\/schema\/person\/1392289282fd1b53969104d8b35e8ff3","name":"Jerwin Roy","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dbtut.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/d362cb6ec946a7bccb4b53862e8f9ca8ba82af0fd90473fd743597321ce62e6e?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d362cb6ec946a7bccb4b53862e8f9ca8ba82af0fd90473fd743597321ce62e6e?s=96&d=mm&r=g","caption":"Jerwin Roy"},"description":"Aspiring DBA","sameAs":["http:\/\/in.linkedin.com\/in\/jerwinroy\/","https:\/\/x.com\/https:\/\/twitter.com\/JerwinRoy"],"url":"https:\/\/dbtut.com\/index.php\/author\/jerwinroy\/"}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/11093","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/users\/98"}],"replies":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/comments?post=11093"}],"version-history":[{"count":0,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/posts\/11093\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media\/11094"}],"wp:attachment":[{"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/media?parent=11093"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/categories?post=11093"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dbtut.com\/index.php\/wp-json\/wp\/v2\/tags?post=11093"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}