This version of the documentation is archived and no longer supported.

Database Profiler Output

The database profiler captures data information about read and write operations, cursor operations, and database commands. To configure the database profile and set the thresholds for capturing profile data, see the Database Profiler section.

The database profiler writes data in the system.profile collection, which is a capped collection. To view the profiler’s output, use normal MongoDB queries on the system.profile collection.


Because the database profiler writes data to the system.profile collection in a database, the profiler will profile some write activity, even for databases that are otherwise read-only.

Changed in version 3.4.

currentOp and the database profiler report the same basic diagnostic information for all CRUD operations, including the following:

These operations are also included in the logging of slow queries (see slowOpThresholdMs for more information about slow query logging).

Example system.profile Document

The documents in the system.profile collection have the following form. This example document reflects a find operation on a standalone mongod:

   "op" : "query",
   "ns" : "test.c",
   "query" : {
      "find" : "c",
      "filter" : {
         "a" : 1
   "keysExamined" : 2,
   "docsExamined" : 2,
   "cursorExhausted" : true,
   "numYield" : 0,
   "locks" : {
      "Global" : {
         "acquireCount" : {
            "r" : NumberLong(2)
      "Database" : {
         "acquireCount" : {
            "r" : NumberLong(1)
      "Collection" : {
         "acquireCount" : {
            "r" : NumberLong(1)
   "nreturned" : 2,
   "responseLength" : 108,
   "protocol" : "op_command",
   "millis" : 0,
   "planSummary" : "IXSCAN { a: 1 }",
   "execStats" : {
      "stage" : "FETCH",
      "nReturned" : 2,
      "executionTimeMillisEstimate" : 0,
      "works" : 3,
      "advanced" : 2,
      "needTime" : 0,
      "needYield" : 0,
      "saveState" : 0,
      "restoreState" : 0,
      "isEOF" : 1,
      "invalidates" : 0,
      "docsExamined" : 2,
      "alreadyHasObj" : 0,
      "inputStage" : {
         "stage" : "IXSCAN",
         "nReturned" : 2,
         "executionTimeMillisEstimate" : 0,
         "works" : 3,
         "advanced" : 2,
         "needTime" : 0,
         "needYield" : 0,
         "saveState" : 0,
         "restoreState" : 0,
         "isEOF" : 1,
         "invalidates" : 0,
         "keyPattern" : {
            "a" : 1
         "indexName" : "a_1",
         "isMultiKey" : false,
         "multiKeyPaths" : {
            "a" : [ ]
         "isUnique" : false,
         "isSparse" : false,
         "isPartial" : false,
         "indexVersion" : 1,
         "direction" : "forward",
         "indexBounds" : {
            "a" : [
               "[1.0, 1.0]"
         "keysExamined" : 2,
         "seeks" : 1,
         "dupsTested" : 0,
         "dupsDropped" : 0,
         "seenInvalidated" : 0
   "ts" : ISODate("2015-09-03T15:26:14.948Z"),
   "client" : "",
   "appName" : "MongoDB Shell",
   "allUsers" : [
            "user" : "report1",
            "db" : "test"
      "user" : "report1@test"

Output Reference

For any single operation, the documents created by the database profiler will include a subset of the following fields. The precise selection of fields in these documents depends on the type of operation.

Changed in version 3.2.0: system.profile.query.skip replaces the system.profile.ntoskip field.

Changed in version 3.2.0: The information in the system.profile.ntoreturn field has been replaced by two separate fields, system.profile.query.limit and system.profile.query.batchSize. Older drivers or older versions of the mongo shell may still use ntoreturn; this will appear as system.profile.query.ntoreturn.


For the output specific to the version of your MongoDB, refer to the appropriate version of the MongoDB Manual.


The type of operation. The possible values are:

  • command
  • count
  • distinct
  • geoNear
  • getMore
  • group
  • insert
  • mapReduce
  • query
  • remove
  • update

The namespace the operation targets. Namespaces in MongoDB take the form of the database, followed by a dot (.), followed by the name of the collection.


The query document used, or for an insert operation, the inserted document. If the document exceeds 50 kilobytes, the value is a string summary of the object. If the string summary exceeds 50 kilobytes, the string summary is truncated, denoted with an ellipsis (...) at the end of the string.

Changed in version 3.0.4: For "getmore" operations on cursors returned from a db.collection.find() or a db.collection.aggregate(), the query field contains respectively the query predicate or the issued aggregate command document. For details on the aggregate command document, see the aggregate reference page.


The command operation. If the command document exceeds 50 kilobytes, the value is a string summary of the object. If the string summary exceeds 50 kilobytes, the string summary is truncated, denoted with an ellipsis (...) at the end of the string.


The <update> document passed in during an update operation. If the document exceeds 50 kilobytes, the value is a string summary of the object. If the string summary exceeds 50 kilobytes, the string summary is truncated, denoted with an ellipsis (...) at the end of the string.


The ID of the cursor accessed by a query and getmore operations.


Changed in version 3.2.0.

Renamed from system.profile.nscanned. The number of index keys that MongoDB scanned in order to carry out the operation.

In general, if keysExamined is much higher than nreturned, the database is scanning many index keys to find the result documents. Consider creating or adjusting indexes to improve query performance..

Changed in version 3.4.

keysExamined is available for the following commands and operations:


Changed in version 3.2.0: Renamed from system.profile.nscannedObjects.

The number of documents in the collection that MongoDB scanned in order to carry out the operation.

Changed in version 3.4.

docsExamined is available for the following commands and operations:


Removed in 3.4.

Changed in version 3.0.0: Only appears when using the MMAPv1 storage engine.

This field appears with a value of true when an update operation moved one or more documents to a new location on disk. If the operation did not result in a move, this field does not appear. Operations that result in a move take more time than in-place updates and typically occur as a result of document growth.


Changed in version 3.0.0: Only appears when using the MMAPv1 storage engine.

The number of documents the operation moved on disk. This field appears only if the operation resulted in a move. The field’s implicit value is zero, and the field is present only when non-zero.


Changed in version 3.2.0: Renamed from system.profile.scanAndOrder.

hasSortStage is a boolean that is true when a query cannot use the ordering in the index to return the requested sorted results; i.e. MongoDB must sort the documents after it receives the documents from a cursor. The field only appears when the value is true.

Changed in version 3.4.

hasSortStage is available for the following commands and operations:


The number of documents deleted by the operation.


The number of documents inserted by the operation.


New in version 2.6.

The number of documents that match the system.profile.query condition for the update operation.


New in version 2.6.

The number of documents modified by the update operation.


A boolean that indicates the update operation’s upsert option value. Only appears if upsert is true.


Deprecated since version 3.4.

Records the number of update operations that match all of the following criteria:

  • Are upserts (that result in an insert)
  • Do not use a modifier operation such as $set

New in version 3.2.5.

A boolean that indicates whether the query planner evaluated multiple plans before choosing the winning execution plan for the query.

Only present when value is true.


New in version 3.2.5.

A boolean that indicates whether the query system evicted a cached plan and re-evaluated all candidate plans.

Only present when value is true.


The number of index keys inserted for a given write operation.


Removed in 3.4.

The number of index keys the update changed in the operation. Changing an index key carries a small performance cost because the database must remove the old key and inserts a new key into the B-tree index.


New in version 3.0.0.

The number of conflicts encountered during the write operation; e.g. an update operation attempts to modify the same document as another update operation. See also write conflict.


The number of times the operation yielded to allow other operations to complete. Typically, operations yield when they need access to data that MongoDB has not yet fully read into memory. This allows other operations that have data in memory to complete while MongoDB reads in data for the yielding operation. For more information, see the FAQ on when operations yield.


New in version 3.0.0: locks replaces the lockStats field.

The system.profile.locks provides information for various lock types and lock modes held during the operation.

The possible lock types are:

Lock Type Description
Global Represents global lock.
MMAPV1Journal Represents MMAPv1 storage engine specific lock to synchronize journal writes; for non-MMAPv1 storage engines, the mode for MMAPV1Journal is empty.
Database Represents database lock.
Collection Represents collection lock.
Metadata Represents metadata lock.
oplog Represents lock on the oplog.

The possible locking modes for the lock types are as follows:

Lock Mode Description
R Represents Shared (S) lock.
W Represents Exclusive (X) lock.
r Represents Intent Shared (IS) lock.
w Represents Intent Exclusive (IX) lock.

The returned lock information for the various lock types include:


Number of times the operation acquired the lock in the specified mode.


Number of times the operation had to wait for the acquireCount lock acquisitions because the locks were held in a conflicting mode. acquireWaitCount is less than or equal to acquireCount.


Cumulative time in microseconds that the operation had to wait to acquire the locks.

timeAcquiringMicros divided by acquireWaitCount gives an approximate average wait time for the particular lock mode.


Number of times the operation encountered deadlocks while waiting for lock acquisitions.

For more information on lock modes, see What type of locking does MongoDB use?.


The number of documents returned by the operation.


The length in bytes of the operation’s result document. A large responseLength can affect performance. To limit the size of the result document for a query operation, you can use any of the following:


When MongoDB writes query profile information to the log, the responseLength value is in a field named reslen.


The MongoDB Wire Protocol request message format.


The time in milliseconds from the perspective of the mongod from the beginning of the operation to the end of the operation.


New in version 3.4.

A summary of the execution plan.


Changed in version 3.0.

A document that contains the execution statistics of the query operation. For other operations, the value is an empty document.

The system.profile.execStats presents the statistics as a tree; each node provides the statistics for the operation executed during that stage of the query operation.


The following fields list for execStats is not meant to be exhaustive as the returned fields vary per stage.


New in version 3.0: stage replaces the type field.

The descriptive name for the operation performed as part of the query execution; e.g.

  • COLLSCAN for a collection scan
  • IXSCAN for scanning index keys
  • FETCH for retrieving documents

New in version 3.0: inputStages replaces the children field.

An array that contains statistics for the operations that are the input stages of the current stage.


The timestamp of the operation.


The IP address or hostname of the client connection where the operation originates.

For some operations, such as db.eval(), the client is instead of an actual client.


New in version 3.4.

The identifier of the client application which ran the operation. If the operation was run in the MongoDB shell, the appName is always "MongoDB Shell". If the operation originated from a driver, appName may be set to a custom string.


An array of authenticated user information (user name and database) for the session. See also Users.


The authenticated user who ran the operation. If the operation was not run by an authenticated user, this field’s value is an empty string.