Docs Menu

Docs HomeDevelop ApplicationsMongoDB Manual

Database Profiler Output

On this page

  • Example system.profile Document
  • Output Reference

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.

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).

Starting in MongoDB 4.4, it is no longer possible to perform any operation, including reads, on the system.profile collection from within a transaction.

The following presents some sample documents found in the system.profile collection for operations on a standalone:

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.

Starting in MongoDB 4.2 (and in 4.0.9), for slow operations, the profiler entries and diagnostic log messages include storage information.


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.


A document containing the full command object associated with this operation.

For example, the following output contains the command object for a find operation on a collection named items in a database named test:

"command" : {
"find" : "items",
"filter" : {
"sku" : 1403978
"$db" : "test"

The following example output contains the command object for a getMore operation generated by a command with cursor ID 19234103609 on a collection named items in a database named test:

"command" : {
"getMore" : NumberLong("19234103609"),
"collection" : "items",
"batchSize" : 10,
"$db" : "test"

If the command document exceeds 50 kilobytes, the document has the following form:

"command" : {
"$truncated": <string>,
"comment": <string>

The $truncated field contains a string summary of the document excluding the document's comment field if present. If the summary still exceeds 50 kilobytes then it is further truncated, denoted by an ellipsis (...) at the end of the string.

The comment field is present if a comment was passed to the operation. Starting in MongoDB 4.4, a comment may be attached to any database command.


Changed in version 3.6.

For "getmore" operations which retrieve the next batch of results from a cursor, the originatingCommand field contains the full command object (e.g. find or aggregate) which originally created that cursor.


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:


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:


New in version 4.2.

A boolean that indicates whether any aggregation stage wrote data to temporary files due to memory restrictions.

Only appears if usedDisk is true.


The number of documents deleted by the operation.


The number of documents inserted by the operation.


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


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.


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.


New in version 4.4.

A string that indicates the specific reason a cached plan was evicted.

Only present when value for replanned 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.


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.


A hexadecimal string that represents a hash of the query shape and is dependent only on the query shape. queryHash can help identify slow queries (including the query filter of write operations) with the same query shape.


As with any hash function, two different query shapes may result in the same hash value. However, the occurrence of hash collisions between different query shapes is unlikely.

For more information on queryHash and planCacheKey, see queryHash and planCacheKey.

New in version 4.2.


A hash of the key for the plan cache entry associated with the query.

Unlike the queryHash, the planCacheKey is a function of both the query shape and the currently available indexes for that shape. That is, if indexes that can support the query shape are added/dropped, the planCacheKey value may change whereas the queryHash value would not change.

For more information on queryHash and planCacheKey, see queryHash and planCacheKey.

New in version 4.2.


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

The possible lock types are:

Lock Type

Represents a lock for parallel batch writer mode.

In earlier versions, PBWM information was reported as part of the Global lock information.

New in version 4.2.


Represents lock taken for replica set member state transitions.

New in version 4.2.

Represents global lock.
Represents database lock.
Represents collection lock.
Represents mutex.
Represents metadata lock.
Represents lock on the oplog.

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

Lock Mode
Represents Shared (S) lock.
Represents Exclusive (X) lock.
Represents Intent Shared (IS) lock.
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?.

New in version 4.2: (Also available starting in 4.0.9)

The information provides metrics on the storage engine data and wait time for the operation.

Specific storage metrics are returned only if the values are greater than zero.

New in version 4.2: (Also available starting in 4.0.9)

Number of bytes read by the operation from the disk to the cache.

Data read from disk into the cache includes everything needed to execute the query. If the data is already in the cache, then the number of bytes read from disk could be 0.

The number of bytes read from disk includes more than the queried documents:

  • WiredTiger reads in units of pages and a page may contain one or several documents. If a document is in a page, all documents in that page are read into the cache and included in the bytesRead value.

  • If the cache requires page management (such as eviction or rereads), the bytesRead value includes data read from disk in these operations.

  • If the index is not in the cache or the index in the cache is stale, WiredTiger reads several internal and leaf pages from disk to reconstruct the index in cache.

New in version 4.2: (Also available starting in 4.0.9)

Time in microseconds that the operation had to spend to read from the disk.

New in version 4.2: (Also available starting in 4.0.9)

Number of bytes written by the operation from the cache to the disk.

WiredTiger typically doesn't require the query to write to disk. Data modified by the query is written to an in-memory cache that WiredTiger flushes to disk as part an eviction or checkpoint operation. In such cases, bytesWritten shows as 0.

If the thread running the query requires forced page management (such as eviction), WiredTiger writes the page contents to disk. This flush likely includes data unrelated to changes made by the query itself, which can cause bytesWritten to show a higher value than expected.

New in version 4.2: (Also available starting in 4.0.9)

Time in microseconds that the operation had to spend to write to the disk.

New in version 4.2: (Also available starting in 4.0.9)

Time in microseconds that the operation had to wait for space in the cache.

New in version 4.2: (Also available starting in 4.0.9)

Time in microseconds that the operation (if modifying the schema) had to wait to acquire a schema lock.

New in version 4.2: (Also available starting in 4.0.9)

Time in microseconds that the operation had to wait to acquire the a lock on the needed data handles.


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.


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.


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


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.


New in version 3.4.

The identifier of the client application which ran the operation. Use the appName connection string option to set a custom value for the appName field.


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.

← Database Profiler