serverStatus.txt

============
serverStatus
============

.. default-domain:: mongodb

.. contents:: On this page
   :local:
   :backlinks: none
   :depth: 1
   :class: singlecol


.. |mongod-only| replace:: *Available on mongod only.*

.. |mongos-only| replace:: *Available on mongos only.*

Definition
----------

.. dbcommand:: serverStatus

   The :dbcommand:`serverStatus` command returns a document that
   provides an overview of the database's state. Monitoring
   applications can run this command at a regular interval to
   collect statistics about the instance.

Syntax
------

The command has the following syntax:

.. code-block:: javascript

   db.runCommand( { serverStatus: 1 } )

The value (i.e. ``1`` above) does not affect the operation of the
command. The ``db.serverStatus()`` command returns a large amount of
data. To return a specific object or field from the output append the
object or field name to the command.

For example:

.. code-block:: javascript

   db.runCommand({ serverStatus: 1}).metrics
   db.runCommand({ serverStatus: 1}).metrics.commands
   db.runCommand({ serverStatus: 1}).metrics.commands.update

:binary:`~bin.mongosh` provides the :method:`db.serverStatus()`
wrapper for the :dbcommand:`serverStatus` command.

.. seealso::

   Much of the output of :dbcommand:`serverStatus` is also displayed
   dynamically by :binary:`~bin.mongostat`. See the
   :binary:`~bin.mongostat` command for more information.

Behavior
--------

.. include:: /includes/extracts/serverStatus-command-projection.rst

For example, the following operation suppresses the ``repl``,
``metrics`` and ``locks`` information in the output.

.. code-block:: javascript

   db.runCommand( { serverStatus: 1, repl: 0, metrics: 0, locks: 0 } )

The following example includes
all :ref:`server-status-repl` information in the output:

.. code-block:: javascript

   db.runCommand( { serverStatus: 1,  repl: 1 } )

Initialization
~~~~~~~~~~~~~~

The statistics reported by :dbcommand:`serverStatus` are reset when the
:binary:`~bin.mongod` server is restarted.

This command will always return a value, even on a fresh database. The
related command :method:`db.serverStatus()` does not always return a
value unless a counter has started to increment for a particular
metric.

After you run an update query, ``db.serverStatus()`` and
``db.runCommand({ serverStatus: 1})`` both return the same values.

.. code-block:: javascript
   :copyable: false

   {
      "arrayFilters" : NumberLong(0),
      "failed" : NumberLong(0),
      "pipeline" : NumberLong(0),
      "total" : NumberLong(1)
   }

Include ``mirroredReads``
~~~~~~~~~~~~~~~~~~~~~~~~~

By default, the :serverstatus:`mirroredReads` information (available
starting in version 4.4) is not included in the output. To return
:serverstatus:`mirroredReads` information, you must explicitly specify
the inclusion:

.. code-block:: javascript

   db.runCommand( { serverStatus: 1, mirroredReads: 1 } )

Include ``latchAnalysis``
~~~~~~~~~~~~~~~~~~~~~~~~~

By default, the :serverstatus:`latchAnalysis` information (available
starting in version 4.4) is not included in the output. To return
:serverstatus:`latchAnalysis` information, you must explicitly specify
the inclusion:

.. code-block:: javascript

   db.runCommand( { serverStatus: 1, latchAnalysis: 1 } )

.. _server-status-output:

Output
------

.. note::

   The output fields vary depending on the version of MongoDB,
   underlying operating system platform, the storage engine, and the
   kind of node, including :binary:`~bin.mongos`, :binary:`~bin.mongod` or
   :term:`replica set` member.

   For the :dbcommand:`serverStatus` output specific to the version of
   your MongoDB, refer to the appropriate version of the MongoDB Manual.

.. _server-status-instance-information:

Instance Information
~~~~~~~~~~~~~~~~~~~~

.. code-block:: javascript

   "host" : <string>,
   "advisoryHostFQDNs" : <array>,
   "version" : <string>,
   "process" : <"mongod"|"mongos">,
   "pid" : NumberLong(<num>),
   "uptime" : <num>,
   "uptimeMillis" : NumberLong(<num>),
   "uptimeEstimate" : NumberLong(<num>),
   "localTime" : ISODate(""),

.. serverstatus:: host

   The system's hostname. In Unix/Linux systems, this should be the
   same as the output of the ``hostname`` command.

.. serverstatus:: advisoryHostFQDNs

   .. versionadded:: 3.2

   An array of the system's fully qualified domain names (FQDNs).

.. serverstatus:: version

   The MongoDB version of the current MongoDB process.

.. serverstatus:: process

   The current MongoDB process. Possible values are: :binary:`~bin.mongos` or
   :binary:`~bin.mongod`.

.. serverstatus:: pid

   The process id number.

.. serverstatus:: uptime

   The number of seconds that the current MongoDB process has been
   active.

.. serverstatus:: uptimeMillis

   The number of milliseconds that the current MongoDB process has been
   active.

.. serverstatus:: uptimeEstimate

   The uptime in seconds as calculated from MongoDB's internal
   course-grained time keeping system.

.. serverstatus:: localTime

   The ISODate representing the current time, according to the server,
   in UTC.

.. _server-status-asserts:

asserts
~~~~~~~

.. code-block:: javascript

   "asserts" : {
      "regular" : <num>,
      "warning" : <num>,
      "msg" : <num>,
      "user" : <num>,
      "rollovers" : <num>
   },

.. serverstatus:: asserts

   A document that reports on the number of assertions raised since the
   MongoDB process started. While assert errors are typically uncommon,
   if there are non-zero values for the :serverstatus:`asserts`, you
   should examine the log file for more information. In many cases,
   these errors are trivial, but are worth investigating.

.. serverstatus:: asserts.regular

   The number of regular assertions raised since the MongoDB process
   started. Examine the log file for more information about these
   messages.

.. serverstatus:: asserts.warning

   .. versionchanged:: 4.0

   Starting in MongoDB 4.0, the field returns zero ``0``.

   In earlier versions, the field returns the number of warnings raised
   since the MongoDB process started.

.. serverstatus:: asserts.msg

   The number of message assertions raised since the MongoDB process
   started. Examine the log file for more information about these
   messages.

.. serverstatus:: asserts.user

   The number of "user asserts" that have occurred since the last time
   the MongoDB process started. These are errors that user may
   generate, such as out of disk space or duplicate key. You can
   prevent these assertions by fixing a problem with your application
   or deployment. Examine the MongoDB log for more information.

.. serverstatus:: asserts.rollovers

   The number of times that the rollover counters have rolled over
   since the last time the MongoDB process started. The counters will
   rollover to zero after 2\ :superscript:`30` assertions. Use this
   value to provide context to the other values in the
   :serverstatus:`asserts` data structure.

.. _server-status-bucketcatalog:

bucketCatalog
~~~~~~~~~~~~~

.. code-block:: javascript

  "bucketCatalog" : {
      "numBuckets" : <num>,
      "numOpenBuckets" : <num>,
      "numIdleBuckets" : <num>,
      "memoryUsage" : <num>
   }

.. versionadded:: 5.0

A document that reports metrics related to the internal storage of
time series collections.

The ``bucketCatalog`` returns the following metrics:

.. list-table::
  :header-rows: 1
  :widths: 30 70

  * - Metric
    - Description

  * - ``numBuckets``

    - The number of buckets that store time series data internally.

  * - ``numOpenBuckets``

    - The number of active, uncommitted writes to buckets.

  * - ``numIdleBuckets``

    - The number of buckets that are not full and can store incoming
      time series data.

  * - ``memoryUsage``

    - The number of bytes used by internal bucketing data structures.

.. versionadded:: 5.0

.. _server-status-connections:

connections
~~~~~~~~~~~

.. code-block:: javascript

   "connections" : {
      "current" : <num>,
      "available" : <num>,
      "totalCreated" : <num>,
      "active" : <num>,
      "threaded" : <num>,
      "exhaustIsMaster" : <num>,
      "exhaustHello" : <num>,
      "awaitingTopologyChanges" : <num>
   },

.. serverstatus:: connections

   A document that reports on the status of the connections. Use these
   values to assess the current load and capacity requirements of the
   server.

.. serverstatus:: connections.current

   The number of incoming connections from clients to the database
   server. This number includes the current shell session. Consider
   the value of :serverstatus:`connections.available` to add more
   context to this datum.

   The value will include all incoming connections including any shell
   connections or connections from other servers, such as
   :term:`replica set` members or :binary:`~bin.mongos` instances.

.. serverstatus:: connections.available

   The number of unused incoming connections available. Consider this
   value in combination with the value of
   :serverstatus:`connections.current` to understand the connection
   load on the database, and the :doc:`/reference/ulimit` document for
   more information about system thresholds on available connections.

.. serverstatus:: connections.totalCreated

   Count of **all** incoming connections created to the server. This
   number includes connections that have since closed.

.. serverstatus:: connections.active

   The number of active client connections to the server. Active client
   connections refers to client connections that currently have
   operations in progress.

   .. versionadded:: 4.0.7

.. serverstatus:: connections.threaded

   The number of incoming connections from clients that are assigned
   to threads that service client requests.

   .. versionadded:: 5.0

.. serverstatus:: connections.exhaustIsMaster

   The number of connections whose last request was an
   ``isMaster`` request with :ref:`exhaustAllowed <wire-msg-flags>`.

   .. note::

      If you are running MongoDB 5.0 or later, do not use the
      ``isMaster`` command. Instead, use :dbcommand:`hello`.

   .. versionadded:: 4.4

.. serverstatus:: connections.exhaustHello

   The number of connections whose last request was a :dbcommand:`hello`
   request with :ref:`exhaustAllowed <wire-msg-flags>`.

   .. versionadded:: 5.0 (and 4.4.2)

.. serverstatus:: connections.awaitingTopologyChanges

   The number of clients currently waiting in a :dbcommand:`hello` or
   ``isMaster`` request for a topology change.

   .. note::

      If you are running MongoDB 5.0 or later, do not use the
      ``isMaster`` command. Instead, use :dbcommand:`hello`.

   .. versionadded:: 4.4

.. _server-status-defaultRWConcern:

defaultRWConcern
~~~~~~~~~~~~~~~~

*Available starting in 4.4*

The ``defaultRWConcern`` section provides information on the local copy
of the global default read or write concern settings. The data may be
stale or out of date. See :dbcommand:`getDefaultRWConcern` for more
information.

.. code-block:: javascript

   "defaultRWConcern" : {
     "defaultReadConcern" : {
       "level" : <string>
     },
     "defaultWriteConcern" : {
       "w" : <string> | <int>,
       "wtimeout" : <int>,
       "j" : <bool>
     },
     "defaultWriteConcernSource": <string>,
     "defaultReadConcernSource": <string>,
     "updateOpTime" : Timestamp,
     "updateWallClockTime" : Date,
     "localUpdateWallClockTime" : Date
   }

.. serverstatus:: defaultRWConcern

   The last known global default read or write concern settings.

   .. versionadded:: 4.4

.. serverstatus:: defaultRWConcern.defaultReadConcern

   The last known global default :ref:`read concern <read-concern>`
   setting.

   If :dbcommand:`serverStatus` does not return this field, the global
   default read concern has either not been set *or* has not yet
   propagated to the instance.

   .. versionadded:: 4.4

.. serverstatus:: defaultRWConcern.defaultReadConcern.level

   The last known global default :ref:`read concern level
   <read-concern-levels>` setting.

   If :dbcommand:`serverStatus` does not return this field, the global
   default for this setting has either not been set *or* has not yet
   propagated to the instance.

   .. versionadded:: 4.4

.. serverstatus:: defaultRWConcern.defaultWriteConcern

   The last known global default :ref:`write concern <write-concern>`
   setting.

   If :dbcommand:`serverStatus` does not return this field, the global
   default write concern has either not been set *or* has not yet
   propagated to the instance. 

   .. versionadded:: 4.4

.. serverstatus:: defaultRWConcern.defaultWriteConcern.w

   The last known global default :ref:`w <wc-w>` setting. 

   If :dbcommand:`serverStatus` does not return this field, the global
   default for this setting has either not been set *or* has not yet
   propagated to the instance.

   .. versionadded:: 4.4

.. serverstatus:: defaultRWConcern.defaultWriteConcern.wtimeout

   The last known global default :ref:`wtimeout <wc-wtimeout>` setting. 

   If :dbcommand:`serverStatus` does not return this field, the global
   default for this setting has either not been set *or* has not yet
   propagated to the instance.

   .. versionadded:: 4.4

.. serverstatus:: defaultRWConcern.defaultWriteConcernSource

   .. include:: /includes/fact-defaultWriteConcernSource-possible-values.rst

   .. versionadded:: 5.0

.. serverstatus:: defaultRWConcern.defaultReadConcernSource

   .. include:: /includes/fact-defaultReadConcernSource-possible-values.rst

   .. versionadded:: 5.0

.. serverstatus:: defaultRWConcern.updateOpTime

   The timestamp when the instance last updated its copy of any global
   read or write concern settings. If the
   :serverstatus:`defaultRWConcern.defaultReadConcern` and
   :serverstatus:`defaultRWConcern.defaultWriteConcern` fields are
   absent, this field indicates the timestamp when the defaults were
   last unset.

   .. versionadded:: 4.4

.. serverstatus:: defaultRWConcern.updateWallClockTime

   The wall clock time when the instance last updated its copy of any
   global read or write concern settings. If the
   :serverstatus:`defaultRWConcern.defaultReadConcern` and
   :serverstatus:`defaultRWConcern.defaultWriteConcern` fields are
   absent, this field indicates the time when the defaults were last
   unset.

   .. versionadded:: 4.4

.. serverstatus:: defaultRWConcern.localUpdateWallClockTime

   The local system wall clock time when the instance last updated its
   copy of any global read or write concern setting. If this field is
   the *only* field under :serverstatus:`defaultRWConcern`, the instance
   has never had knowledge of a global default read or write concern
   setting.

   .. versionadded:: 4.4
   

.. _server-status-electionMetrics:

electionMetrics
~~~~~~~~~~~~~~~

*Available starting in 4.2.1 (and 4.0.13)*

The ``electionMetrics`` section provides information on elections
called by this :binary:`~bin.mongod` instance in a bid to become the
primary:

.. code-block:: javascript

   "electionMetrics" : {
      "stepUpCmd" : {
         "called" : NumberLong(<num>),
         "successful" : NumberLong(<num>)
      },
      "priorityTakeover" : {
         "called" : NumberLong(<num>),
         "successful" : NumberLong(<num>)
      },
      "catchUpTakeover" : {
         "called" : NumberLong(<num>),
         "successful" : NumberLong(<num>)
      },
      "electionTimeout" : {
         "called" : NumberLong(<num>),
         "successful" : NumberLong(<num>)
      },
      "freezeTimeout" : {
         "called" : NumberLong(<num>),
         "successful" : NumberLong(<num>)
      },
      "numStepDownsCausedByHigherTerm" : NumberLong(<num>),
      "numCatchUps" : NumberLong(<num>),
      "numCatchUpsSucceeded" : NumberLong(<num>),
      "numCatchUpsAlreadyCaughtUp" : NumberLong(<num>),
      "numCatchUpsSkipped" : NumberLong(<num>),
      "numCatchUpsTimedOut" : NumberLong(<num>),
      "numCatchUpsFailedWithError" : NumberLong(<num>),
      "numCatchUpsFailedWithNewTerm" : NumberLong(<num>),
      "numCatchUpsFailedWithReplSetAbortPrimaryCatchUpCmd" : NumberLong(<num>),
      "averageCatchUpOps" : <double>
   }

.. serverstatus:: electionMetrics.stepUpCmd

   Metrics on elections that were called by the :binary:`~bin.mongod`
   instance as part of an :parameter:`election handoff
   <enableElectionHandoff>` when the primary stepped down.

   The :serverstatus:`~electionMetrics.stepUpCmd` includes both the number of elections
   called and the number of elections that succeeded.

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.priorityTakeover

   Metrics on elections that were called by the :binary:`~bin.mongod`
   instance because its :rsconf:`~members[n].priority` is higher
   than the primary's.

   The :serverstatus:`electionMetrics.priorityTakeover` includes both the number of
   elections called and the number of elections that succeeded.

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.catchUpTakeover

   Metrics on elections called by the :binary:`~bin.mongod` instance
   because it is more current than the primary.

   The :serverstatus:`~electionMetrics.catchUpTakeover` includes both the number of
   elections called and the number of elections that succeeded.

   .. seealso::

      :rsconf:`settings.catchUpTakeoverDelayMillis`

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.electionTimeout

   Metrics on elections called by the :binary:`~bin.mongod` instance
   because it has not been able to reach the primary within
   :rsconf:`settings.electionTimeoutMillis`.

   The :serverstatus:`~electionMetrics.electionTimeout` includes both the number of
   elections called and the number of elections that succeeded.

   .. seealso:: 
      
      :rsconf:`settings.electionTimeoutMillis`

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.freezeTimeout

   Metrics on elections called by the :binary:`~bin.mongod` instance
   after its :dbcommand:`freeze period <replSetFreeze>` (during which the
   member cannot seek an election) has expired.

   The :serverstatus:`electionMetrics.freezeTimeout` includes both the number of
   elections called and the number of elections that succeeded.

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.numStepDownsCausedByHigherTerm

   Number of times the :binary:`~bin.mongod` instance stepped down
   because it saw a higher term (specifically, other member(s)
   participated in additional elections).

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.numCatchUps

   Number of elections where the :binary:`~bin.mongod` instance as the
   newly-elected primary had to catch up to the highest known oplog
   entry.

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.numCatchUpsSucceeded

   Number of times the :binary:`~bin.mongod` instance as the
   newly-elected primary successfully caught up to the highest known
   oplog entry.

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.numCatchUpsAlreadyCaughtUp

   Number of times the :binary:`~bin.mongod` instance as the
   newly-elected primary concluded its catchup process because it was
   already caught up when elected.

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.numCatchUpsSkipped

   Number of times the :binary:`~bin.mongod` instance as the
   newly-elected primary skipped the catchup process.

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.numCatchUpsTimedOut

   Number of times the :binary:`~bin.mongod` instance as the
   newly-elected primary concluded its catchup process because of the
   :rsconf:`settings.catchUpTimeoutMillis` limit.

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.numCatchUpsFailedWithError

   Number of times the newly-elected primary's catchup process failed
   with an error.

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.numCatchUpsFailedWithNewTerm

   Number of times the newly-elected primary's catchup process concluded
   because another member(s) had a higher term (specifically, other
   member(s) participated in additional elections).

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.numCatchUpsFailedWithReplSetAbortPrimaryCatchUpCmd

   Number of times the newly-elected primary's catchup process
   concluded because the :binary:`~bin.mongod` received the
   :dbcommand:`replSetAbortPrimaryCatchUp` command.

   *Available starting in 4.2.1 (and 4.0.13)*

.. serverstatus:: electionMetrics.averageCatchUpOps

   Average number of operations applied during the newly-elected
   primary's catchup processes.

   *Available starting in 4.2.1*

.. _server-status-extra-info:
.. _server-status-extra_info:
.. _server-status-extrainfo:

extra_info
~~~~~~~~~~

.. code-block:: javascript

   "extra_info" : {
      "note" : "fields vary by platform.",
      "heap_usage_bytes" : <num>,
      "page_faults" : <num>
   },

.. serverstatus:: extra_info

   A document that provides additional information about the underlying
   system.

.. serverstatus:: extra_info.note

   A string with the text ``"fields vary by platform."``

.. serverstatus:: extra_info.heap_usage_bytes

   The total size in bytes of heap space used by the database process.
   Available on Unix/Linux systems only.

.. serverstatus:: extra_info.page_faults

   The total number of page faults. The
   :serverstatus:`extra_info.page_faults` counter may increase
   dramatically during moments of poor performance and may correlate
   with limited memory environments and larger data sets. Limited and
   sporadic page faults do not necessarily indicate an issue.

   Windows differentiates "hard" page faults involving disk I/O from
   "soft" page faults that only require moving pages in memory. MongoDB
   counts both hard and soft page faults in this statistic.

.. _server-status-flowControl:

flowControl
~~~~~~~~~~~

.. versionadded:: 4.2

.. code-block:: javascript

   "flowControl" : {
      "enabled" : <boolean>,
      "targetRateLimit" : <int>,
      "timeAcquiringMicros" : NumberLong(<num>),
      "locksPerKiloOp" : <double>,  // Available in 4.4+. In 4.2, returned locksPerOp instead.
      "sustainerRate" : <int>,
      "isLagged" : <boolean>,
      "isLaggedCount" : <int>,
      "isLaggedTimeMicros" : NumberLong(<num>)
   },

.. serverstatus:: flowControl

   A document that returns statistics on the :ref:`flow-control`. With
   flow control enabled, as the :data:`majority commit
   <replSetGetStatus.optimes.lastCommittedOpTime>` point lag grows
   close to the :parameter:`flowControlTargetLagSeconds`, writes on the
   primary must obtain tickets before taking locks. As such, the
   metrics returned are meaningful when run on the primary.

   .. versionadded:: 4.2

.. serverstatus:: flowControl.enabled

   A boolean that indicates whether :ref:`flow-control` is
   enabled (``true``) or disabled (``false``).
   
   See also :parameter:`enableFlowControl`.

   .. versionadded:: 4.2

.. serverstatus:: flowControl.targetRateLimit

   When run on the primary, the maximum number of tickets that can be
   acquired per second.

   When run on a secondary, the returned number is a placeholder.
   
   .. versionadded:: 4.2

.. serverstatus:: flowControl.timeAcquiringMicros

   When run on the primary, the total time write operations have waited
   to acquire a ticket.

   When run on a secondary, the returned number is a placeholder.

   .. versionadded:: 4.2

.. serverstatus:: flowControl.locksPerKiloOp

   .. note:: Starting in MongoDB 4.4


      :serverstatus:`~flowControl.locksPerKiloOp` replaces
      :serverstatus:`~flowControl.locksPerOp` field.
      :serverstatus:`~flowControl.locksPerOp` field is available only
      on version 4.2.

   When run on the primary, an approximation of the number of locks
   taken per 1000 operations.

   When run on a secondary, the returned number is a placeholder.

   .. versionadded:: 4.4

.. serverstatus:: flowControl.locksPerOp

   .. note:: Available on MongoDB 4.2 only


      MongoDB 4.4 replaces :serverstatus:`~flowControl.locksPerOp` with
      :serverstatus:`flowControl.locksPerKiloOp`.

   When run on the primary, an approximation of the number of locks taken
   per operation.

   When run on a secondary, the returned number is a placeholder.

   .. versionadded:: 4.2

.. serverstatus:: flowControl.sustainerRate

   When run on the primary, an approximation of operations applied per
   second by the secondary that is sustaining the commit point.

   When run on a secondary, the returned number is a placeholder.

   .. versionadded:: 4.2

.. serverstatus:: flowControl.isLagged

   When run on the primary, a boolean that indicates whether flow
   control has engaged. Flow control engages when the majority
   committed lag is greater than some percentage of the configured
   :parameter:`flowControlTargetLagSeconds`.

   When run on a secondary, the returned boolean is a placeholder.

   .. versionadded:: 4.2

.. serverstatus:: flowControl.isLaggedCount

   When run on a primary, the number of times flow control has engaged
   since the last restart. Flow control engages when the majority
   committed lag is greater than some percentage of the
   :parameter:`flowControlTargetLagSeconds`.

   When run on a secondary, the returned number is a placeholder.

   .. versionadded:: 4.2

.. serverstatus:: flowControl.isLaggedTimeMicros

   When run on the primary, the amount of time flow control has spent
   being engaged since the last restart. Flow control engages when the
   majority committed lag is greater than some percentage of the
   :parameter:`flowControlTargetLagSeconds`.

   When run on a secondary, the returned number is a placeholder.

   .. versionadded:: 4.2

.. _server-status-freeMonitoring:

freeMonitoring
~~~~~~~~~~~~~~

.. code-block:: javascript

   "freeMonitoring" : {
      "state" : <string>,
      "retryIntervalSecs" : NumberLong(<num>),
      "lastRunTime" : <string>,
      "registerErrors" : NumberLong(<num>),
      "metricsErrors" : NumberLong(<num>)
   },

.. serverstatus:: freeMonitoring

   A document that reports on the :doc:`free Cloud monitoring
   </administration/free-monitoring>`.

.. serverstatus:: freeMonitoring.state

   The enablement state of free monitoring. The values can be one of
   the following:

   - "enabled"

   - "disabled"

   - "pending" if the enable free monitoring encountered a registeration error.

.. serverstatus:: freeMonitoring.retryIntervalSecs

   The frequency, in seconds, at which data is uploaded.

.. serverstatus:: freeMonitoring.lastRunTime

   The date and time of the last run of the metrics upload.
   
.. serverstatus:: freeMonitoring.registerErrors

   The number of registration errors, incremented on unexpected HTTP
   status or network errors.

.. serverstatus:: freeMonitoring.metricsErrors

   The number of errors encountered when uploading metrics.

.. _globalLock:
.. _globallock:
.. _global-lock:
.. _server-status-globallock:
.. _server-status-global-lock:

globalLock
~~~~~~~~~~

.. code-block:: javascript

   "globalLock" : {
      "totalTime" : NumberLong(<num>),
      "currentQueue" : {
         "total" : <num>,
         "readers" : <num>,
         "writers" : <num>
      },
      "activeClients" : {
         "total" : <num>,
         "readers" : <num>,
         "writers" : <num>
      }
   },

.. serverstatus:: globalLock

   A document that reports on the database's lock state.

   Generally, the :ref:`locks <locks>` document provides more detailed
   data on lock uses.

.. serverstatus:: globalLock.totalTime

   The time, in microseconds, since the database last started and
   created the :serverstatus:`globalLock`. This is approximately
   equivalent to the total server uptime.

.. serverstatus:: globalLock.currentQueue

   A document that provides information concerning the number of
   operations queued because of a lock.

.. serverstatus:: globalLock.currentQueue.total

   The total number of operations queued waiting for the lock (i.e.,
   the sum of :serverstatus:`globalLock.currentQueue.readers` and
   :serverstatus:`globalLock.currentQueue.writers`).

   A consistently small queue, particularly of shorter operations,
   should cause no concern. The
   :serverstatus:`globalLock.activeClients` readers and writers
   information provides context for this data.

.. serverstatus:: globalLock.currentQueue.readers

   The number of operations that are currently queued and waiting for
   the read lock. A consistently small read queue, particularly of
   shorter operations, should cause no concern.

.. serverstatus:: globalLock.currentQueue.writers

   The number of operations that are currently queued and waiting for
   the write lock. A consistently small write queue, particularly of
   shorter operations, is no cause for concern.

.. serverstatus:: globalLock.activeClients

   A document that provides information about the number of connected
   clients and the read and write operations performed by these clients.

   Use this data to provide context for the
   :serverstatus:`globalLock.currentQueue` data.

.. serverstatus:: globalLock.activeClients.total

   The total number of internal client connections to the database
   including system threads as well as queued readers and writers.
   This metric will be higher than the total of ``activeClients.readers``
   and ``activeClients.writers`` due to the inclusion of system threads.

.. serverstatus:: globalLock.activeClients.readers

   The number of the active client connections performing read
   operations.

.. serverstatus:: globalLock.activeClients.writers

   The number of active client connections performing write operations.

.. _server-status-hedgingMetrics:

hedgingMetrics
~~~~~~~~~~~~~~

.. versionadded:: 4.4

   For :binary:`~bin.mongos` instances only.

.. code-block:: javascript

   "hedgingMetrics" : {
      "numTotalOperations" : <num>,
      "numTotalHedgedOperations" : <num>,
      "numAdvantageouslyHedgedOperations" : <num>
   },

.. serverstatus:: hedgingMetrics

   Provides metrics on :ref:`hedged reads <mongos-hedged-reads>` for
   the :binary:`~bin.mongos` instance.

   .. versionadded:: 4.4

      For :binary:`~bin.mongos` instances only.

.. serverstatus:: hedgingMetrics.numTotalOperations

   The total number of the operations issued with the :ref:`hedged read
   option enabled <read-preference-hedged-read>` to this
   :binary:`~bin.mongos` instance.

   .. versionadded:: 4.4

      For :binary:`~bin.mongos` instances only.

.. serverstatus:: hedgingMetrics.numTotalHedgedOperations

   The number of all operations for which the :binary:`~bin.mongos`
   instance :ref:`hedged the read operation <mongos-hedged-reads>`;
   i.e. sent the operation to an additional member of each queried
   shard.

   .. versionadded:: 4.4

      For :binary:`~bin.mongos` instances only.

.. serverstatus:: hedgingMetrics.numAdvantageouslyHedgedOperations

   The total number of the operation where the additional read sent to
   :ref:`hedge the read operation <mongos-hedged-reads>` fulfilled the
   client request.

   .. versionadded:: 4.4

      For :binary:`~bin.mongos` instances only.

.. _server-status-latchAnalysis:

latchAnalysis
~~~~~~~~~~~~~

.. versionadded:: 4.4


.. code-block:: javascript

   "latchAnalysis" : {
      <latch name> : {
         "created" : <num>,
         "destroyed" : <num>,
         "acquired" : <num>,
         "released" : <num>,
         "contended" : <num>,
         "hierarchicalAcquisitionLevelViolations" : {
               "onAcquire" : <num>,
               "onRelease" : <num>
         }
      },
      ...

.. serverstatus:: latchAnalysis

   A document that reports on metrics related to internal locking
   primitives (also known as latches).

   To return :serverstatus:`latchAnalysis` information, you must
   explicitly specify the inclusion:

   .. code-block:: javascript

      db.runCommand( { serverStatus: 1, latchAnalysis: 1 } )

   The ``latchAnalysis`` returns for each latch the ``<latch name>``
   and the following associated metrics:

   .. list-table::
      :header-rows: 1
      :widths: 30 70

      * - Metric
        - Description

      * - ``created``

        - Number of times the latch was created.

      * - ``destroyed``

        - Number of times the latch was destroyed.

      * - ``acquired``

        - Number of times the latch was acquired.

      * - ``released``

        - Number of times the latch was released.

      * - ``contended``
        - Number of times the latch had contention.

      * - ``hierarchicalAcquisitionLevelViolations``

        - *Only returned if violations exist*

          Contains the following fields:

          - ``onAcquire``

            - Number of times the latch hierarchy (i.e. the latch level
              ordering) has been violated during latch acquisition.

          - ``onRelease``

            - Number of times the latch hierarchy (i.e. the latch level
              ordering) has been violated during latch release.

   .. versionadded:: 4.4

.. _server-status-logicalSessions:

logicalSessionRecordCache
~~~~~~~~~~~~~~~~~~~~~~~~~

.. versionadded:: 3.6

.. code-block:: javascript

   "logicalSessionRecordCache" : {
      "activeSessionsCount" : <num>,
      "sessionsCollectionJobCount" : <num>,
      "lastSessionsCollectionJobDurationMillis" : <num>,
      "lastSessionsCollectionJobTimestamp" : <Date>,
      "lastSessionsCollectionJobEntriesRefreshed" : <num>,
      "lastSessionsCollectionJobEntriesEnded" : <num>,
      "lastSessionsCollectionJobCursorsClosed" : <num>,
      "transactionReaperJobCount" : <num>,
      "lastTransactionReaperJobDurationMillis" : <num>,
      "lastTransactionReaperJobTimestamp" : <Date>,
      "lastTransactionReaperJobEntriesCleanedUp" : <num>,
      "sessionCatalogSize" : <num>   // Starting in MongoDB 4.2
   },

.. serverstatus:: logicalSessionRecordCache

   Provides metrics around the caching of :doc:`server sessions
   </reference/server-sessions/>`.

.. serverstatus:: logicalSessionRecordCache.activeSessionsCount

   The number of all active local sessions cached in memory by the
   :binary:`~bin.mongod` or :binary:`~bin.mongos` instance since the last
   refresh period.

   .. seealso::

      - :pipeline:`$listLocalSessions`
      - :parameter:`logicalSessionRefreshMillis`

.. serverstatus:: logicalSessionRecordCache.sessionsCollectionJobCount

   The number that tracks the number of times the refresh process has
   run on the :data:`config.system.sessions` collection.

   .. seealso::

      :parameter:`logicalSessionRefreshMillis`

.. serverstatus:: logicalSessionRecordCache.lastSessionsCollectionJobDurationMillis

   The length in milliseconds of the last refresh.

.. serverstatus:: logicalSessionRecordCache.lastSessionsCollectionJobTimestamp

   The time at which the last refresh occurred.

.. serverstatus:: logicalSessionRecordCache.lastSessionsCollectionJobEntriesRefreshed

   The number of sessions that were refreshed during the last refresh.

.. serverstatus:: logicalSessionRecordCache.lastSessionsCollectionJobEntriesEnded

   The number of sessions that ended during the last refresh.

.. serverstatus:: logicalSessionRecordCache.lastSessionsCollectionJobCursorsClosed

   The number of cursors that were closed during the last
   :data:`config.system.sessions` collection refresh.

.. serverstatus:: logicalSessionRecordCache.transactionReaperJobCount

   The number that tracks the number of times the transaction record
   cleanup process has run on the :data:`config.transactions`
   collection.

.. serverstatus:: logicalSessionRecordCache.lastTransactionReaperJobDurationMillis

   The length (in milliseconds) of the last transaction record cleanup.

.. serverstatus:: logicalSessionRecordCache.lastTransactionReaperJobTimestamp

   The time of the last transaction record cleanup.

.. serverstatus:: logicalSessionRecordCache.lastTransactionReaperJobEntriesCleanedUp

   The number of entries in the :data:`config.transactions` collection
   that were deleted during the last transaction record cleanup.

.. serverstatus:: logicalSessionRecordCache.sessionCatalogSize

   - For a :binary:`~bin.mongod` instance, 
        The size of its in-memory cache of the ``config.transactions``
        entries. This corresponds to retryable writes
        or transactions whose sessions have not expired within the
        :parameter:`localLogicalSessionTimeoutMinutes`.

   - For a :binary:`~bin.mongos` instance, 
        The number of the in-memory cache of its sessions that have had
        transactions within the most recent
        :parameter:`localLogicalSessionTimeoutMinutes` interval.

   .. versionadded:: 4.2

.. _locks:
.. _server-status-locks:

locks
~~~~~

.. code-block:: javascript

   "locks" : {
      <type> : {
            "acquireCount" : {
               <mode> : NumberLong(<num>),
               ...
            },
            "acquireWaitCount" : {
               <mode> : NumberLong(<num>),
               ...
            },
            "timeAcquiringMicros" : {
               <mode> : NumberLong(<num>),
               ...
            },
            "deadlockCount" : {
               <mode> : NumberLong(<num>),
               ...
            }
      },
      ...


.. serverstatus:: locks

   A document that reports for each lock ``<type>``, data on lock
   ``<modes>``.

   The possible lock ``<types>`` are:

   .. include:: /includes/fact-lock-types.rst

   The possible ``<modes>`` are:

   .. include:: /includes/fact-lock-modes.rst

   All values are of the ``NumberLong()`` type.

   .. COMMENT

      these definitions are for the servers and not per operations;
      as such, they differ from those in db.currentOp.txt

.. serverstatus:: locks.<type>.acquireCount

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

.. serverstatus:: locks.<type>.acquireWaitCount

   Number of times the :serverstatus:`locks.<type>.acquireCount` lock
   acquisitions encountered waits because the locks were held in a
   conflicting mode.

.. serverstatus:: locks.<type>.timeAcquiringMicros

   Cumulative wait time in microseconds for the lock acquisitions.

   :serverstatus:`locks.<type>.timeAcquiringMicros` divided by
   :serverstatus:`locks.<type>.acquireWaitCount` gives an
   approximate average wait time for the particular lock mode.

.. serverstatus:: locks.<type>.deadlockCount

   Number of times the lock acquisitions encountered deadlocks.

.. _server-status-mirroredReads:

mirroredReads
~~~~~~~~~~~~~

|mongod-only|

.. code-block:: javascript

   "mirroredReads" : {
         "seen" : <num>,
         "sent" : <num>
   },

.. serverstatus:: mirroredReads

   |mongod-only|

   A document that reports on :ref:`mirrored reads <mirrored-reads>`.
   To return :serverstatus:`mirroredReads` information, you must
   explicitly specify the inclusion:

   .. code-block:: javascript

      db.runCommand( { serverStatus: 1, mirroredReads: 1 } )

   .. serverstatus:: mirroredReads.seen

      .. versionadded:: 4.4

      The number of :ref:`operations that support mirroring
      <mirrored-reads-supported-operations>` received by this member.

      .. seealso::

         :parameter:`mirrorReads` Parameter

   .. serverstatus:: mirroredReads.sent

      .. versionadded:: 4.4

      The number of mirrored reads sent by this member when primary.
      For example, if a read is mirrored and sent to two secondaries,
      the number of mirrored reads is ``2``.

      .. seealso:: 
         
         :parameter:`mirrorReads` Parameter


.. _server-status-network:

network
~~~~~~~

.. code-block:: javascript

   "network" : {
      "bytesIn" : NumberLong(<num>),
      "bytesOut" : NumberLong(<num>),
      "numSlowDNSOperations" : NumberLong(<num>),
      "numSlowSSLOperations" : NumberLong(<num>),
      "numRequests" : NumberLong(<num>),
      "tcpFastOpen" : {
         "kernelSetting" : NumberLong(<num>),
         "serverSupported" : <bool>,
         "clientSupported" : <bool>,
         "accepted" : NumberLong(<num>)
      },
      "serviceExecutors" : {
         "passthrough" : {
            "threadsRunning" : <num>,
            "clientsInTotal" : <num>,
            "clientsRunning" : <num>,
            "clientsWaitingForData" : <num>
         },
         "fixed" : {
            "threadsRunning" : <num>,
            "clientsInTotal" : <num>,
            "clientsRunning" : <num>,
            "clientsWaitingForData" : <num>
         }
      }
   },

.. serverstatus:: network

   A document that reports data on MongoDB's network use. These
   statistics measure *ingress connections* only, specifically the
   traffic seen by the :binary:`~bin.mongod` or :binary:`~bin.mongos`
   over network connections initiated by clients or other
   :binary:`~bin.mongod` or :binary:`~bin.mongos` instances. Traffic
   from network connections initiated by this :binary:`~bin.mongod` or
   :binary:`~bin.mongos` instance (specifically, *egress connections*)
   is *not* measured in these statistics.

.. serverstatus:: network.bytesIn

   The total number of bytes that the server has *received* over network
   connections initiated by clients or other :binary:`~bin.mongod` or
   :binary:`~bin.mongos` instances.

.. serverstatus:: network.bytesOut

   The total number of bytes that the server has *sent* over network
   connections initiated by clients or other :binary:`~bin.mongod` or
   :binary:`~bin.mongos` instances.

.. serverstatus:: network.numSlowDNSOperations

   .. versionadded:: 4.4

   The total number of DNS resolution operations which took longer than
   1 second.
  
.. serverstatus:: network.numSlowSSLOperations

   .. versionadded:: 4.4

   The total number of SSL handshake operations which took longer than
   1 second.

.. serverstatus:: network.numRequests

   The total number of distinct requests that the server has received.
   Use this value to provide context for the
   :serverstatus:`network.bytesIn` and :serverstatus:`network.bytesOut`
   values to ensure that MongoDB's network utilization is consistent
   with expectations and application use.

.. serverstatus:: network.tcpFastOpen
   
   .. versionadded:: 4.4

   A document that reports data on MongoDB's support and use of 
   TCP Fast Open (TFO) connections.

.. serverstatus:: network.tcpFastOpen.kernelSetting

   .. versionadded:: 4.4

   *Linux only* 

   Returns the value of ``/proc/sys/net/ipv4/tcp_fastopen``:

   - ``0`` - TCP Fast Open is disabled on the system.

   - ``1`` - TCP Fast Open is enabled for outgoing connections.

   - ``2`` - TCP Fast Open is enabled for incoming connections.

   - ``3`` - TCP Fast Open is enabled for incoming and outgoing 
     connections. 

.. serverstatus:: network.tcpFastOpen.serverSupported

   .. versionadded:: 4.4

   - Returns ``true`` if the host operating system supports inbound
     TCP Fast Open (TFO) connections.

   - Returns ``false`` if the host operating system does *not* support
     inbound TCP Fast Open (TFO) connections.

.. serverstatus:: network.tcpFastOpen.clientSupported

   .. versionadded:: 4.4

   - Returns ``true`` if the host operating system supports outbound
     TCP Fast Open (TFO) connections.

   - Returns ``false`` if the host operating system does *not* support
     outbound TCP Fast Open (TFO) connections.

.. serverstatus:: network.tcpFastOpen.accepted

   .. versionadded:: 4.4

   The total number of accepted incoming TCP Fast Open (TFO) connections
   to the :binary:`~bin.mongod` or :binary:`~bin.mongos` since the 
   ``mongod`` or ``mongos`` last started.

.. serverstatus:: network.serviceExecutors

   .. versionadded:: 5.0

   A document that reports data on the service executors, which run
   operations for client requests.

.. serverstatus:: network.serviceExecutors.passthrough

   .. versionadded:: 5.0

   A document that reports data about the threads and clients for the
   ``passthrough`` service executor. The ``passthrough`` service
   executor creates a new thread for each client and destroys the thread
   after the client ends.

.. serverstatus:: network.serviceExecutors.passthrough.threadsRunning

   .. versionadded:: 5.0

   Number of threads running in the ``passthrough`` service executor.

.. serverstatus:: network.serviceExecutors.passthrough.clientsInTotal

   .. versionadded:: 5.0

   Total number of clients allocated to the ``passthrough`` service
   executor. A client can be allocated to the ``passthrough`` service
   executor and not currently running requests.

.. serverstatus:: network.serviceExecutors.passthrough.clientsRunning

   .. versionadded:: 5.0

   Number of clients currently using the ``passthrough`` service
   executor to run requests.

.. serverstatus:: network.serviceExecutors.passthrough.clientsWaitingForData

   .. versionadded:: 5.0

   Number of clients using the ``passthrough`` service executor that are
   waiting for incoming data from the network.

.. serverstatus:: network.serviceExecutors.fixed

   .. versionadded:: 5.0

   A document that reports data about the threads and clients for the
   ``fixed`` service executor. The ``fixed`` service executor has a
   fixed number of threads. A thread is temporarily assigned to a client
   and the thread is preserved after the client ends.

.. serverstatus:: network.serviceExecutors.fixed.threadsRunning

   .. versionadded:: 5.0

   Number of threads running in the ``fixed`` service executor.

.. serverstatus:: network.serviceExecutors.fixed.clientsInTotal

   .. versionadded:: 5.0

   Total number of clients allocated to the ``fixed`` service executor.
   A client can be allocated to the ``fixed`` service executor and not
   currently running requests.

.. serverstatus:: network.serviceExecutors.fixed.clientsRunning

   .. versionadded:: 5.0

   Number of clients currently using the ``fixed`` service executor to
   run requests.

.. serverstatus:: network.serviceExecutors.fixed.clientsWaitingForData

   .. versionadded:: 5.0

   Number of clients using the ``fixed`` service executor that are
   waiting for incoming data from the network.

opLatencies
~~~~~~~~~~~

*Only for ``mongod`` instances*

.. code-block:: javascript

   "opLatencies" : {
      "reads" : <document>,
      "writes" : <document>,
      "commands" : <document>
   },

.. serverstatus:: opLatencies

   A document containing operation latencies for the instance as a whole.
   See :ref:`latency-stats-document` for an description of this document.

   Only :binary:`~bin.mongod` instances report
   :serverstatus:`opLatencies`.

.. serverstatus:: opLatencies.reads

   Latency statistics for read requests.

.. serverstatus:: opLatencies.writes

   Latency statistics for write operations.

.. serverstatus:: opLatencies.commands

   Latency statistics for database commands.

.. _server-status-opReadConcernCounters:

opReadConcernCounters
~~~~~~~~~~~~~~~~~~~~~

.. warning:: Removed

   Starting in version 5.0, :serverstatus:`opReadConcernCounters` is
   replaced by :serverstatus:`readConcernCounters`.

*Only for mongod instances*

.. code-block:: javascript

   "opReadConcernCounters" : {
      "available" : NumberLong(<num>),
      "linearizable" : NumberLong(<num>),
      "local" : NumberLong(<num>),
      "majority" : NumberLong(<num>),
      "snapshot" : NumberLong(<num>),
      "none" :  NumberLong(<num>)
   }

.. serverstatus:: opReadConcernCounters

   *Removed in version 5.0*. Replaced by
   :serverstatus:`readConcernCounters`.

   A document that reports on the :ref:`read concern level
   <read-concern-levels>` specified by query operations to the
   :binary:`~bin.mongod` instance since it last started.

   .. list-table::
      :header-rows: 1
      :widths: 20 80

      * - Specified ``w``
        - Description

      * - ``"available"``

        - Number of query operations that specified read concern level
          :readconcern:`"available"`.

      * - ``"linearizable"``

        - Number of query operations that specified read concern level
          :readconcern:`"linearizable"`.

      * - ``"local"``

        - Number of query operations that specified read
          concern level :readconcern:`"local"`.

      * - ``"majority"``

        - Number of query operations that specified read
          concern level :readconcern:`"majority"`.

      * - ``"snapshot"``

        - Number of query operations that specified read
          concern level :readconcern:`"snapshot"`.

      * - ``"none"``

        - Number of query operations that did not specify a read
          concern level and instead used the default :ref:`read concern level
          <read-concern-levels>`.

   The sum of the :serverstatus:`opReadConcernCounters` equals
   :serverstatus:`opcounters.query`.

.. _server-status-opWriteConcernCounters:

opWriteConcernCounters
~~~~~~~~~~~~~~~~~~~~~~~

.. versionadded:: 4.0.6

*Only for mongod instances*

.. code-block:: javascript

   "opWriteConcernCounters" : {
      "insert" : {
         "wmajority" : NumberLong(<num>),
         "wnum" : {
            "<num>" :  NumberLong(<num>),
            ...
         },
         "wtag" : {
            "<tag1>" :  NumberLong(<num>),
            ...
         },
         "none" : NumberLong(<num>)
      },
      "update" : {
         "wmajority" : NumberLong(<num>),
         "wnum" : {
            "<num>" :  NumberLong(<num>),
         },
         "wtag" : {
            "<tag1>" :  NumberLong(<num>),
            ...
         },
         "none" : NumberLong(<num>)
      },
      "delete" : {
         "wmajority" :  NumberLong(<num>)
         "wnum" : {
            "<num>" :  NumberLong(<num>),
            ...
         },
         "wtag" : {
            "<tag1>" :  NumberLong(<num>),
            ...
         },
         "none" : NumberLong(<num>)
      }
   }

.. serverstatus:: opWriteConcernCounters

   A document that reports on the :doc:`write concerns
   </reference/write-concern>` specified by write operations to the
   :binary:`~bin.mongod` instance since it last started.

   More specifically, the :serverstatus:`opWriteConcernCounters`
   reports on the :ref:`w: \<value\> <wc-w>` specified by the write
   operations. The journal flag option (``j``) and the timeout option
   (``wtimeout``) of the write concerns does not affect the count. The
   count is incremented even if the operation times out.

   .. note::

      .. include:: /includes/extracts/serverStatus-opWriteConcernCounters.rst

.. serverstatus:: opWriteConcernCounters.insert

   .. versionadded:: 4.0.6

   A document that reports on the :ref:`w: \<value\> <wc-w>` specified
   by insert operations to the :binary:`~bin.mongod` instance since it
   last started:

   .. note::

      .. include:: /includes/extracts/serverStatus-opWriteConcernCounters.rst

   .. code-block:: javascript

      "insert" : {
         "wmajority" : NumberLong(<num>),
         "wnum" : {
            "<num>" :  NumberLong(<num>),
            ...
         },
         "wtag" : {
            "<tag1>" :  NumberLong(<num>),
            ...
         },
         "none" : NumberLong(<num>)
      },

   .. list-table::
      :header-rows: 1
      :widths: 20 80

      * - Specified ``w``
        - Description

      * - ``"wmajority"``

        - Number of insert operations that specified
          :writeconcern:`w: "majority" <"majority">`.

      * - ``"wnum"``

        - Number of insert operations that specified
          :writeconcern:`w: \<num\> <\<number\>>`. The counts are
          grouped by the specific``<num>``.

      * - ``"wtag"``

        - Number of insert operations that specified
          :writeconcern:`w: \<tag\> <\<custom write concern name\>>`.
          The counts are grouped by the specific ``<tag>``.

      * - ``"none"``

        - Number of insert operations that did not specify ``w`` value.
          These operations use the default ``w`` value of ``1``.

   The sum of the :serverstatus:`opWriteConcernCounters.insert` equals
   :serverstatus:`opcounters.insert`.

.. serverstatus:: opWriteConcernCounters.update

   .. versionadded:: 4.0.6

   A document that reports on the :ref:`w: \<value\> <wc-w>` specified
   by update operations to the :binary:`~bin.mongod` instance since it
   last started:

   .. note::

      .. include:: /includes/extracts/serverStatus-opWriteConcernCounters.rst

   .. code-block:: javascript

      "update" : {
         "wmajority" : NumberLong(<num>),
         "wnum" : {
            "<num>" :  NumberLong(<num>),
            ...
         },
         "wtag" : {
            "<tag1>" :  NumberLong(<num>),
            ...
         },
         "none" : NumberLong(<num>)
      },

   .. list-table::
      :header-rows: 1
      :widths: 20 80

      * - Specified ``w``
        - Description

      * - ``"wmajority"``

        - Number of update operations that specified
          :writeconcern:`w: "majority" <"majority">`.

      * - ``"wnum"``

        - Number of update operations that specified
          :writeconcern:`w: \<num\> <\<number\>>`. The counts are
          grouped by the specific ``<num>``.

      * - ``"wtag"``

        - Number of update operations that specified
          :writeconcern:`w: \<tag\> <\<custom write concern name\>>`.
          The counts are grouped by the specific ``<tag>``.

      * - ``"none"``

        - Number of update operations that did not specify ``w`` value.
          These operations use the default ``w`` value of ``1``.

   The sum of the :serverstatus:`opWriteConcernCounters.update` equals
   :serverstatus:`opcounters.update`.

.. serverstatus:: opWriteConcernCounters.delete

   .. versionadded:: 4.0.6

   A document that reports on the :ref:`w: \<value\> <wc-w>` specified
   by delete operations to the :binary:`~bin.mongod` instance since it
   last started:

   .. note::

      .. include:: /includes/extracts/serverStatus-opWriteConcernCounters.rst

   .. code-block:: javascript

      "delete" : {
         "wmajority" :  NumberLong(<num>),
         "wnum" : {
            "<num>" :  NumberLong(<num>),
            ...
         },
         "wtag" : {
            "<tag1>" :  NumberLong(<num>),
            ...
         },
         "none" : NumberLong(<num>)
      }

   .. list-table::
      :header-rows: 1
      :widths: 20 80

      * - Specified ``w``
        - Description

      * - ``"wmajority"``

        - Number of delete operations that specified
          :writeconcern:`w: "majority" <"majority">`.

      * - ``"wnum"``

        - Number of delete operations that specified
          :writeconcern:`w: \<num\> <\<number\>>`. The counts are
          grouped by the specific ``<num>``.

      * - ``"wtag"``

        - Number of delete operations that specified
          :writeconcern:`w: \<tag\> <\<custom write concern name\>>`.
          The counts are grouped by the specific ``<tag>``.

      * - ``"none"``

        - Number of delete operations that did not specify ``w`` value.
          These operations use the default ``w`` value of ``1``.

   The sum of the :serverstatus:`opWriteConcernCounters.delete` equals
   :serverstatus:`opcounters.delete`.

.. _server-status-opcounters:

opcounters
~~~~~~~~~~

.. include:: /includes/extracts/4.2-changes-opcounters-type.rst

.. code-block:: javascript

   "opcounters" : {
      "insert" : NumberLong(<num>),  // Starting in MongoDB 4.2, type is NumberLong
      "query" : NumberLong(<num>),   // Starting in MongoDB 4.2, type is NumberLong
      "update" : NumberLong(<num>),  // Starting in MongoDB 4.2, type is NumberLong
      "delete" : NumberLong(<num>),  // Starting in MongoDB 4.2, type is NumberLong
      "getmore" : NumberLong(<num>), // Starting in MongoDB 4.2, type is NumberLong
      "command" : NumberLong(<num>), // Starting in MongoDB 4.2, type is NumberLong
   },

.. serverstatus:: opcounters

   A document that reports on database operations by type since the
   :binary:`~bin.mongod` instance last started.

   These numbers will grow over time until next restart. Analyze these
   values over time to track database utilization.

   .. note::

      The data in :serverstatus:`opcounters` treats operations
      that affect multiple documents, such as bulk insert or
      multi-update operations, as a single operation. See
      :serverstatus:`metrics.document` for more granular
      document-level operation tracking.

      Additionally, these values reflect received operations, and
      increment even when operations are not successful.

.. serverstatus:: opcounters.insert

   The total number of insert operations received since the
   :binary:`~bin.mongod` instance last started.

   .. include:: /includes/extracts/4.2-changes-opcounters-type.rst

.. serverstatus:: opcounters.query

   The total number of queries received since the :binary:`~bin.mongod`
   instance last started.

   .. include:: /includes/extracts/4.2-changes-opcounters-type.rst

.. serverstatus:: opcounters.update

   The total number of update operations received since the
   :binary:`~bin.mongod` instance last started.

   .. include:: /includes/extracts/4.2-changes-opcounters-type.rst

.. serverstatus:: opcounters.delete

   The total number of delete operations since the :binary:`~bin.mongod`
   instance last started.

   .. include:: /includes/extracts/4.2-changes-opcounters-type.rst

.. serverstatus:: opcounters.getmore

   The total number of :dbcommand:`getMore` operations since the
   :binary:`~bin.mongod` instance last started. This counter can be high
   even if the query count is low. Secondary nodes send
   :dbcommand:`getMore` operations as part of the replication process.

   .. include:: /includes/extracts/4.2-changes-opcounters-type.rst

.. serverstatus:: opcounters.command

   The total number of commands issued to the database since the
   :binary:`~bin.mongod` instance last started.

   :serverstatus:`opcounters.command` counts all :doc:`commands
   </reference/command>` **except** the write commands:
   :dbcommand:`insert`, :dbcommand:`update`, and :dbcommand:`delete`.

   .. include:: /includes/extracts/4.2-changes-opcounters-type.rst

.. _server-status-opcountersrepl:
.. _server-status-opcounters-repl:

opcountersRepl
~~~~~~~~~~~~~~

.. include:: /includes/extracts/4.2-changes-opcountersRepl-type.rst

.. code-block:: javascript

   "opcountersRepl" : {
      "insert" : NumberLong(<num>),  // Starting in MongoDB 4.2, type is NumberLong
      "query" : NumberLong(<num>),   // Starting in MongoDB 4.2, type is NumberLong
      "update" : NumberLong(<num>),  // Starting in MongoDB 4.2, type is NumberLong
      "delete" : NumberLong(<num>),  // Starting in MongoDB 4.2, type is NumberLong
      "getmore" : NumberLong(<num>), // Starting in MongoDB 4.2, type is NumberLong
      "command" : NumberLong(<num>), // Starting in MongoDB 4.2, type is NumberLong
   },

.. serverstatus:: opcountersRepl

   A document that reports on database replication operations by type
   since the :binary:`~bin.mongod` instance last started.

   These values only appear when the current host is a member of a
   replica set.

   These values will differ from the :serverstatus:`opcounters` values
   because of how MongoDB serializes operations during replication.
   See :doc:`/replication` for more information on replication.

   These numbers will grow over time in response to database use until
   next restart. Analyze these values over time to track database
   utilization.

   .. include:: /includes/extracts/4.2-changes-opcountersRepl-type.rst

.. serverstatus:: opcountersRepl.insert

   The total number of replicated insert operations since the
   :binary:`~bin.mongod` instance last started.

   .. include:: /includes/extracts/4.2-changes-opcountersRepl-type.rst

.. serverstatus:: opcountersRepl.query

   The total number of replicated queries since the :binary:`~bin.mongod`
   instance last started.

   .. include:: /includes/extracts/4.2-changes-opcountersRepl-type.rst

.. serverstatus:: opcountersRepl.update

   The total number of replicated update operations since the
   :binary:`~bin.mongod` instance last started.

   .. include:: /includes/extracts/4.2-changes-opcountersRepl-type.rst

.. serverstatus:: opcountersRepl.delete

   The total number of replicated delete operations since the
   :binary:`~bin.mongod` instance last started.

   .. include:: /includes/extracts/4.2-changes-opcountersRepl-type.rst

.. serverstatus:: opcountersRepl.getmore

   The total number of :dbcommand:`getMore` operations since the
   :binary:`~bin.mongod` instance last started. This counter can be high
   even if the query count is low. Secondary nodes send
   :dbcommand:`getMore` operations as part of the replication process.

   .. include:: /includes/extracts/4.2-changes-opcountersRepl-type.rst

.. serverstatus:: opcountersRepl.command

   The total number of replicated commands issued to the database since
   the :binary:`~bin.mongod` instance last started.

   .. include:: /includes/extracts/4.2-changes-opcountersRepl-type.rst

readConcernCounters
~~~~~~~~~~~~~~~~~~~

.. versionadded:: 5.0

.. code-block:: javascript

   "readConcernCounters" : {
      "nonTransactionOps" : {
         "none" : NumberLong(<num>),
         "local" : NumberLong(<num>),
         "available" : NumberLong(<num>),
         "majority" : NumberLong(<num>),
         "snapshot" : {
            "withClusterTime" : NumberLong(<num>),
            "withoutClusterTime" : NumberLong(<num>)
         },
         "linearizable" : NumberLong(<num>)
      },
      "transactionOps" : {
         "none" : NumberLong(<num>),
         "local" : NumberLong(<num>),
         "majority" : NumberLong(<num>),
         "snapshot" : {
            "withClusterTime" : NumberLong(<num>),
            "withoutClusterTime" : NumberLong(<num>)
         }
      }
   },

.. serverstatus:: readConcernCounters

   A document that reports on the :ref:`read concern level
   <read-concern-levels>` specified by query operations. This document
   contains the :serverstatus:`readConcernCounters.nonTransactionOps`
   and :serverstatus:`readConcernCounters.transactionOps` documents.

.. serverstatus:: readConcernCounters.nonTransactionOps

   A document that reports on the :ref:`read concern level
   <read-concern-levels>` specified by non-transaction query operations
   performed after the database server last started.

.. serverstatus:: readConcernCounters.nonTransactionOps.none

   Number of non-transaction query operations that did not specify a
   read concern level and instead used the default :ref:`read concern
   level <read-concern-levels>`.

.. serverstatus:: readConcernCounters.nonTransactionOps.local

   Number of non-transaction query operations that specified the
   :readconcern:`"local"` read concern level.

.. serverstatus:: readConcernCounters.nonTransactionOps.available

   Number of non-transaction query operations that specified the
   :readconcern:`"available"` read concern level.

.. serverstatus:: readConcernCounters.nonTransactionOps.majority

   Number of non-transaction query operations that specified the
   :readconcern:`"majority"` read concern level.

.. serverstatus:: readConcernCounters.nonTransactionOps.snapshot

   Document containing non-transaction query operations that specified
   the :readconcern:`"snapshot"` read concern level.

.. serverstatus:: readConcernCounters.nonTransactionOps.snapshot.withClusterTime

   Number of non-transaction query operations that specified the
   :readconcern:`"snapshot"` read concern level and the cluster time,
   which specified a point in time.

.. serverstatus:: readConcernCounters.nonTransactionOps.snapshot.withoutClusterTime

   Number of non-transaction query operations that specified the
   :readconcern:`"snapshot"` read concern level without the cluster
   time, which means a point in time was omitted and the server will
   read the most recently committed snapshot available to the node.

.. serverstatus:: readConcernCounters.nonTransactionOps.linearizable

   Number of non-transaction query operations that specified the
   :readconcern:`"linearizable"` read concern level.

.. serverstatus:: readConcernCounters.transactionOps

   A document that reports on the :ref:`read concern level
   <read-concern-levels>` specified by transaction query operations
   performed after the database server last started.

.. serverstatus:: readConcernCounters.transactionOps.none

   Number of transaction query operations that did not specify a
   read concern level and instead used the default :ref:`read concern
   level <read-concern-levels>`.

.. serverstatus:: readConcernCounters.transactionOps.local

   Number of transaction query operations that specified the
   :readconcern:`"local"` read concern level.

.. serverstatus:: readConcernCounters.transactionOps.available

   Number of transaction query operations that specified the
   :readconcern:`"available"` read concern level.

.. serverstatus:: readConcernCounters.transactionOps.majority

   Number of transaction query operations that specified the
   :readconcern:`"majority"` read concern level.

.. serverstatus:: readConcernCounters.transactionOps.snapshot

   Document containing transaction query operations that specified the
   :readconcern:`"snapshot"` read concern level.

.. serverstatus:: readConcernCounters.transactionOps.snapshot.withClusterTime

   Number of transaction query operations that specified the
   :readconcern:`"snapshot"` read concern level and the cluster time,
   which specified a point in time.

.. serverstatus:: readConcernCounters.transactionOps.snapshot.withoutClusterTime

   Number of transaction query operations that specified the
   :readconcern:`"snapshot"` read concern level without the cluster
   time, which means a point in time was omitted and the server will
   read the most recently committed snapshot available to the node.

.. _server-status-oplogTruncation:

oplogTruncation
~~~~~~~~~~~~~~~

.. code-block:: javascript

   "oplogTruncation" : {
      "totalTimeProcessingMicros" : NumberLong(<num>),
      "processingMethod" : <string>,
      "oplogMinRetentionHours" : <double>
      "totalTimeTruncatingMicros" : NumberLong(<num>),
      "truncateCount" : NumberLong(<num>)
   },

.. serverstatus:: oplogTruncation

   A document that reports on :doc:`oplog </core/replica-set-oplog>`
   truncations.

   The field only appears when the current instance is a member of a
   replica set and uses either the :doc:`/core/wiredtiger` or
   :doc:`/core/inmemory`.

   .. versionchanged:: 4.4

       Also available in :doc:`/core/inmemory`.

   .. versionadded:: 4.2.1

      Available in the :doc:`/core/wiredtiger`.

.. serverstatus:: oplogTruncation.totalTimeProcessingMicros

   The total time taken, in microseconds, to scan or sample the oplog
   to determine the oplog truncation points.

   :serverstatus:`~oplogTruncation.totalTimeProcessingMicros` is only
   meaningful if the :binary:`~bin.mongod` instance started on existing
   data files (i.e. not meaningful for :doc:`/core/inmemory`).

   See :serverstatus:`oplogTruncation.processingMethod`

   .. versionchanged:: 4.4

       Also available in :doc:`/core/inmemory`.

   .. versionadded:: 4.2.1

      Available in the :doc:`/core/wiredtiger`.

.. serverstatus:: oplogTruncation.processingMethod

   The method used at start up to determine the oplog truncation points.
   The value can be either ``"sampling"`` or ``"scanning"``.

   :serverstatus:`~oplogTruncation.processingMethod` is only meaningful
   if the :binary:`~bin.mongod` instance started on existing data files
   (i.e. not meaningful for :doc:`/core/inmemory`).

   .. versionchanged:: 4.4

       Also available in :doc:`/core/inmemory`.

   .. versionadded:: 4.2.1

      Available in the :doc:`/core/wiredtiger`.

.. serverstatus:: oplogTruncation.minRetentionHours

   .. versionadded:: 4.4

      The minimum retention period for the oplog in hours. If the oplog
      has exceeded the oplog size, the :binary:`~bin.mongod` only
      truncates oplog entries older than the configured retention
      value.

   Only visible if the :binary:`~bin.mongod` is a member of a replica
   set *and*:

   - The :binary:`~bin.mongod` was started with the
     :option:`--oplogMinRetentionHours
     <mongod --oplogMinRetentionHours>` command line option *or* the 
     :setting:`storage.oplogMinRetentionHours` configuration file 
     option,

     *or*

   - The minimum retention period was configured after startup using
     :dbcommand:`replSetResizeOplog`.

.. serverstatus:: oplogTruncation.totalTimeTruncatingMicros

   The cumulative time spent, in microseconds, performing oplog truncations.

   .. versionchanged:: 4.4

       Also available in :doc:`/core/inmemory`.

   .. versionadded:: 4.2.1

      Available in the :doc:`/core/wiredtiger`.

.. serverstatus:: oplogTruncation.truncateCount


   The cumulative number of oplog truncations.

   .. versionchanged:: 4.4

       Also available in :doc:`/core/inmemory`.

   .. versionadded:: 4.2.1

      Available in the :doc:`/core/wiredtiger`.

.. _server-status-repl:

repl
~~~~

.. code-block:: javascript

   "repl" : {
      "hosts" : [
            <string>,
            <string>,
            <string>
      ],
      "setName" : <string>,
      "setVersion" : <num>,
      "isWritablePrimary" : <boolean>,
      "secondary" : <boolean>,
      "primary" : <hostname>,
      "me" : <hostname>,
      "electionId" : ObjectId(""),
      "primaryOnlyServices": {
         "ReshardingRecipientService": { "state": <string>, "numInstances": <num> },
         "RenameCollectionParticipantService": { "state": <string>, "numInstances": <num> },
         "ShardingDDLCoordinator": { "state": <string>, "numInstances": <num> },
         "ReshardingDonorService": { "state": <string>, "numInstances": <num> }
      },
      "rbid" : <num>,
      "replicationProgress" : [
            {
               "rid" : <ObjectId>,
               "optime" : { ts: <timestamp>, term: <num> },
               "host" : <hostname>,
               "memberId" : <num>
            },
           ...
      ]
   }

.. serverstatus:: repl

   A document that reports on the replica set configuration.
   :serverstatus:`repl` only appear when the current host is a replica
   set. See :doc:`/replication` for more information on replication.

.. serverstatus:: repl.hosts

   An array of the current replica set members' hostname and port
   information (``"host:port"``).

.. serverstatus:: repl.setName

   A string with the name of the current replica set. This value
   reflects the :option:`--replSet <mongod --replSet>` command line
   argument, or :setting:`~replication.replSetName` value in the
   configuration file.

.. serverstatus:: repl.isWritablePrimary

   A boolean that indicates whether the current node is the
   :term:`primary` of the replica set.

.. serverstatus:: repl.secondary

   A boolean that indicates whether the current node is a
   :term:`secondary` member of the replica set.

.. serverstatus:: repl.primary

   The hostname and port information (``"host:port"``) of the current
   :term:`primary` member of the replica set.

.. serverstatus:: repl.me

    The hostname and port information (``"host:port"``) for the current
    member of the replica set.

.. serverstatus:: repl.primaryOnlyServices

   Document that contains the number and status of 
   instances of each primary service active on the server. Primary 
   services can only start when a server is primary but can continue running to 
   completion after the server changes state.
   
   .. versionadded:: 5.0

.. serverstatus:: repl.primaryOnlyServices.ReshardingRecipientService

   Document that contains the state and number of instances of the
   ``ReshardingRecipientService``.

   Recipients are the shards,that would own the chunks after as a 
   result of the resharding operation, according to the new 
   :manual:`shard key</core/sharding-shard-key/>` and 
   :manual:`zones</core/zone-sharding/>`.

   The resharding coordinator instructs each donor and recipient shard 
   primary, to rename the temporary sharded collection.
   The temporary collection becomes the new resharded collection.

   .. versionadded:: 5.0

.. serverstatus:: repl.primaryOnlyServices.RenameCollectionParticipantService

   Document that contains the state and number of instances of the
   ``RenameCollectionParticipantService``.

   The ``RenameCollectionParticipantService`` ensures that, after a shard 
   receives a 
   :manual:`renameCollection</reference/method/db.collection.renameCollection/>`
   request, the shard is able to resume the local rename in case of 
   system failure.

   .. versionadded:: 5.0

.. serverstatus:: repl.primaryOnlyServices.ShardingDDLCoordinator

   Document that contains the state and number of instances of the
   ``ShardingDDLCoordinator``.

   The ``ShardingDDLCoordinator`` service manages DDL operations for 
   :manual:`primary</core/replica-set-members/#std-label-replica-set-primary-member>`
   databases such as:
   :manual:`create database</core/databases-and-collections/#create-a-database>`,
   :manual:`drop database</reference/method/db.dropDatabase/>`,
   :manual:`renameCollection</reference/method/db.collection.renameCollection>`. 
   
   The ``ShardingDDLCoordinator`` ensures that one DDL operation for
   each database can happen at any one specific point in time within a 
   sharded cluster. 

   .. versionadded:: 5.0

.. serverstatus:: repl.primaryOnlyServices.ReshardingDonorService

   Document that contains the state and number of instances of the
   ``ReshardingDonorService``.

   Donors are the shards that own chunks of the sharded collection
   before the rename operation completes.

   The resharding coordinator instructs each donor and recipient shard 
   primary, to rename the temporary sharded collection.
   The temporary collection becomes the new resharded collection.

   .. versionadded:: 5.0

.. serverstatus:: repl.rbid

   :term:`Rollback <rollback>` identifier. Used to determine if a rollback has
   happened for this :binary:`~bin.mongod` instance.

.. serverstatus:: repl.replicationProgress

   An array with one document for each member of the replica set that
   reports replication process to this member. Typically this is the
   primary, or secondaries if using chained replication.

   To include this output, you must pass the ``repl`` option to the
   :dbcommand:`serverStatus`, as in the following:

   .. code-block:: javascript

      db.serverStatus({ "repl": 1 })
      db.runCommand({ "serverStatus": 1, "repl": 1 })

   The content of the :serverstatus:`repl.replicationProgress` section
   depends on the source of each member's replication. This section
   supports internal operation and is for internal and diagnostic use only.

.. serverstatus:: repl.replicationProgress[n].rid

   An ObjectId used as an ID for the members of the replica
   set. For internal use only.

.. serverstatus:: repl.replicationProgress[n].optime

   Information regarding the last operation from the :term:`oplog` that
   the member applied, as reported from this member.

.. serverstatus:: repl.replicationProgress[n].host

   The name of the host in ``[hostname]:[port]`` format for the member
   of the replica set.

.. serverstatus:: repl.replicationProgress[n].memberID

   The integer identifier for this member of the replica set.

.. _server-status-security:

security
~~~~~~~~

.. code-block:: javascript

   "security" : {
      "authentication" : {
         "saslSupportedMechsReceived" : <num>,
         "mechanisms" : {
            "MONGODB-X509" : {
               "speculativeAuthenticate" : {
                  "received" : NumberLong(<num>),
                  "successful" : NumberLong(<num>)
               },
               "authenticate" : {
                  "received" : NumberLong(<num>),
                  "successful" : NumberLong(<num>)
               }
            },
            "SCRAM-SHA-1" : {
               "speculativeAuthenticate" : {
                  "received" : NumberLong(<num>),
                  "successful" : NumberLong(<num>)
               },
               "authenticate" : {
                  "received" : NumberLong(<num>),
                  "successful" : NumberLong(<num>)
               }
            },
            "SCRAM-SHA-256" : {
               "speculativeAuthenticate" : {
                  "received" : NumberLong(<num>),
                  "successful" : NumberLong(<num>)
               },
               "authenticate" : {
                  "received" : NumberLong(<num>),
                  "successful" : NumberLong(<num>)
               }
             }
          }
        },
        "SSLServerSubjectName": <string>,
        "SSLServerHasCertificateAuthority": <boolean>,
        "SSLServerCertificateExpirationDate": <date>
   },

.. serverstatus:: security

   A document that reports on:

   - The number of times a given authentication mechanism has been used
     to authenticate against the :binary:`~bin.mongod` or
     :binary:`~bin.mongos` instance. (New in MongoDB 4.4)

   - The :binary:`~bin.mongod`/:binary:`~bin.mongos` instance's TLS/SSL
     certificate. (Only appears for :binary:`~bin.mongod` or
     :binary:`~bin.mongos` instance with support for TLS)

   .. serverstatus:: security.authentication.saslSupportedMechsReceived

      .. versionadded:: 5.0

      The number of times a :dbcommand:`hello` request includes a valid
      :data:`hello.saslSupportedMechs` field.

   .. serverstatus:: security.authentication.mechanisms

      A document that reports on the number of times a given
      authentication mechanism has been used to authenticate against the
      :binary:`~bin.mongod` or :binary:`~bin.mongos` instance. The
      values in the document distinguish standard authentication and
      speculative authentication. [#speculative-auth]_

      .. versionadded:: 4.4

      .. note::

         The fields in the ``mechanisms`` document depend on the
         configuration of the :parameter:`authenticationMechanisms`
         parameter. The ``mechanisms`` document includes a field for
         each authentication mechanism supported by your
         :binary:`~bin.mongod` or :binary:`~bin.mongos` instance.

         The following example shows the shape of the ``mechanisms``
         document for a deployment that only supports :doc:`x.509
         </core/security-x.509/>` authentication.

   .. serverstatus:: security.authentication.mechanisms.MONGODB-X509

      A document that reports on the number of times
      :doc:`x.509 </core/security-x.509/>` has been used to
      authenticate against the
      :binary:`~bin.mongod` or :binary:`~bin.mongos` instance.

      Includes total number of ``x.509`` authentication attempts and the
      subset of those attempts which were speculative.
      [#speculative-auth]_

      .. versionadded:: 4.4

   .. serverstatus:: security.authentication.mechanisms.MONGODB-X509.speculativeAuthenticate.received

      Number of speculative authentication attempts received using
      :doc:`x.509 </core/security-x.509/>`. Includes both successful and
      failed speculative authentication attempts. [#speculative-auth]_

      .. versionadded:: 4.4

   .. serverstatus:: security.authentication.mechanisms.MONGODB-X509.speculativeAuthenticate.successful

      Number of successful speculative authentication attempts received
      using :doc:`x.509 </core/security-x.509/>`. [#speculative-auth]_

      .. versionadded:: 4.4

   .. serverstatus:: security.authentication.mechanisms.MONGODB-X509.authenticate.received

      Number of successful and failed authentication attempts
      received using :doc:`x.509 </core/security-x.509/>`. This value
      includes speculative authentication attempts received using x.509.

      .. versionadded:: 4.4

   .. serverstatus:: security.authentication.mechanisms.MONGODB-X509.authenticate.successful

      Number of successful authentication attempts received using
      :doc:`x.509 </core/security-x.509/>`. This value includes
      successful speculative authentication attempts which used x.509.

      .. versionadded:: 4.4

   .. [#speculative-auth]

      Speculative authentication minimizes the number of network round
      trips during the authentication process to optimize performance.

   .. serverstatus:: security.SSLServerSubjectName

      The subject name associated with the
      :binary:`~bin.mongod`/:binary:`~bin.mongos` instance's TLS/SSL
      certificate.

   .. serverstatus:: security.SSLServerHasCertificateAuthority

      A boolean that is:

      - ``true`` when the :binary:`~bin.mongod`/:binary:`~bin.mongos`
        instance's TLS/SSL certificate is associated with a certificate
        authority.

      - ``false`` when the TLS/SSL certificate is self-signed.

   .. serverstatus:: security.SSLServerCertificateExpirationDate

      The expiration date and time of the
      :binary:`~bin.mongod`/:binary:`~bin.mongos` instance's TLS/SSL
      certificate.

.. _server-status-sharding:

sharding
~~~~~~~~

.. versionadded:: 3.2

   When run on :binary:`~bin.mongos`, the command returns sharding
   information.

.. versionchanged:: 3.6

   Starting in MongoDB 3.6, shard members return sharding information.

.. code-block:: javascript

   {
      "configsvrConnectionString" : "csRS/cfg1.example.net:27019,cfg2.example.net:27019,cfg2.example.net:27019",
      "lastSeenConfigServerOpTime" : {
         "ts" : <timestamp>,
         "t" : NumberLong(<num>)
      },
      "maxChunkSizeInBytes" : NumberLong(<num>)
   }

.. serverstatus:: sharding

   A document with data regarding the sharded cluster. The
   :serverstatus:`~sharding.lastSeenConfigServerOpTime` is present only
   for a :binary:`~bin.mongos` or a shard member, not for a config
   server.

.. serverstatus:: sharding.configsvrConnectionString

   The connection string for the config servers.

.. serverstatus:: sharding.lastSeenConfigServerOpTime

   The latest optime of the CSRS primary that the :program:`mongos` or
   the shard member has seen. The optime document includes:

   .. include:: /includes/fact-optime.rst

   The :serverstatus:`~sharding.lastSeenConfigServerOpTime` is present
   only if the sharded cluster uses CSRS.

.. serverstatus:: sharding.maxChunkSizeInBytes

   .. versionadded:: 3.6

   The maximum :ref:`size limit <sharding-chunk-size>` for a chunk. If
   the chunk size has been updated recently on the config server, the
   :serverstatus:`~sharding.maxChunkSizeInBytes` may not reflect the
   most recent value.

.. _server-status-sharding-statistics:

shardingStatistics
~~~~~~~~~~~~~~~~~~

.. versionadded:: 4.0

.. tabs::

   tabs:

      - id: shard
        name: Shard
        content: |

         When run on a member of a shard:

         .. code-block:: javascript

            "shardingStatistics" : {
               "countStaleConfigErrors" : NumberLong(<num>),
               "countDonorMoveChunkStarted" : NumberLong(<num>),
               "totalDonorChunkCloneTimeMillis" : NumberLong(<num>),
               "totalCriticalSectionCommitTimeMillis" : NumberLong(<num>),
               "totalCriticalSectionTimeMillis" : NumberLong(<num>),
               "countDocsClonedOnRecipient" : NumberLong(<num>),
               "countDocsClonedOnDonor" : NumberLong(<num>),
               "countRecipientMoveChunkStarted" : NumberLong(<num>),
               "countDocsDeletedOnDonor" : NumberLong(<num>),
               "countDonorMoveChunkLockTimeout" : NumberLong(<num>),
               "unfinishedMigrationFromPreviousPrimary" : NumberLong(<num>),
               "catalogCache" : {
                  "numDatabaseEntries" : NumberLong(<num>),
                  "numCollectionEntries" : NumberLong(<num>),
                  "countStaleConfigErrors" : NumberLong(<num>),
                  "totalRefreshWaitTimeMicros" : NumberLong(<num>),
                  "numActiveIncrementalRefreshes" : NumberLong(<num>),
                  "countIncrementalRefreshesStarted" : NumberLong(<num>),
                  "numActiveFullRefreshes" : NumberLong(<num>),
                  "countFullRefreshesStarted" : NumberLong(<num>),
                  "countFailedRefreshes" : NumberLong(<num>)
               },
               "rangeDeleterTasks" : <num>,
               "resharding" : {
                  "countReshardingOperations" : NumberLong(<num>),
                  "countReshardingSuccessful" : NumberLong(<num>),
                  "countReshardingFailures" : NumberLong(<num>),
                  "countReshardingCanceled" : NumberLong(<num>),
                  "totalOperationTimeElapsedMillis" : NumberLong(<num>),
                  "remainingOperationTimeEstimatedMillis" : NumberLong(<num>),
                  "approxDocumentsToCopy" : NumberLong(<num>),
                  "documentsCopied" : NumberLong(<num>),
                  "approxBytesToCopy" : NumberLong(<num>),
                  "bytesCopied" : NumberLong(<num>),
                  "totalCopyTimeElapsedMillis" : NumberLong(<num>),
                  "oplogEntriesFetched" : NumberLong(<num>),
                  "oplogEntriesApplied" : NumberLong(<num>),
                  "totalApplyTimeElapsedMillis" : NumberLong(<num>),
                  "countWritesDuringCriticalSection" : NumberLong(<num>),
                  "totalCriticalSectionTimeElapsedMillis" : NumberLong(<num>),
                  "donorState" : <num>,
                  "recipientState" : <num>,
                  "coordinatorState" : <num>,
                  "opStatus" : <num>
               }
            },

      - id: mongos
        name: mongos
        content: |

         When run on a :binary:`~bin.mongos`:

         .. code-block:: javascript

            "shardingStatistics" : {
               "numHostsTargeted": {
                  "find" : {
                     "allShards": NumberLong(<num>),
                     "manyShards": NumberLong(<num>),
                     "oneShard": NumberLong(<num>),
                     "unsharded": NumberLong(<num>) 
                           },
                  "insert": { 
                     "allShards": NumberLong(<num>),
                     "manyShards": NumberLong(<num>),
                     "oneShard": NumberLong(<num>),
                     "unsharded": NumberLong(<num>) 
                           },
                  "update": { 
                     "allShards": NumberLong(<num>),
                     "manyShards": NumberLong(<num>),
                     "oneShard": NumberLong(<num>),
                     "unsharded": NumberLong(<num>) 
                           },
                  "delete": { 
                     "allShards": NumberLong(<num>),
                     "manyShards": NumberLong(<num>),
                     "oneShard": NumberLong(<num>),
                     "unsharded": NumberLong(<num>) 
                           },
                  "aggregate": { 
                     "allShards": NumberLong(<num>),
                     "manyShards": NumberLong(<num>),
                     "oneShard": NumberLong(<num>),
                     "unsharded": NumberLong(<num>) 
                           }
                  }
               },
               "catalogCache" : {
                  "numDatabaseEntries" : NumberLong(<num>),
                  "numCollectionEntries" : NumberLong(<num>),
                  "countStaleConfigErrors" : NumberLong(<num>),
                  "totalRefreshWaitTimeMicros" : NumberLong(<num>),
                  "numActiveIncrementalRefreshes" : NumberLong(<num>),
                  "countIncrementalRefreshesStarted" : NumberLong(<num>),
                  "numActiveFullRefreshes" : NumberLong(<num>),
                  "countFullRefreshesStarted" : NumberLong(<num>),
                  "countFailedRefreshes" : NumberLong(<num>),
                  "operationsBlockedByRefresh" : {
                    "countAllOperations" : NumberLong(<num>),
                    "countInserts" : NumberLong(<num>),
                    "countQueries" : NumberLong(<num>),
                    "countUpdates" : NumberLong(<num>),
                    "countDeletes" : NumberLong(<num>),
                    "countCommands" : NumberLong(<num>)
                  }
               }
            },

.. serverstatus:: shardingStatistics

   A document which contains metrics on metadata refresh on sharded
   clusters.

.. serverstatus:: shardingStatistics.countStaleConfigErrors

   The total number of times that threads hit stale config exception.
   Since a stale config exception triggers a refresh of the metadata,
   this number is roughly proportional to the number of metadata
   refreshes.

   *Only present when run on a shard.*

.. serverstatus:: shardingStatistics.countDonorMoveChunkStarted

   The total number of times that the :dbcommand:`moveChunk` command
   has started on the shard, of which this node is a member, as part of
   a :ref:`chunk migration process <chunk-migration-procedure>`. This
   increasing number does not consider whether the chunk migrations
   succeed or not.

   *Only present when run on a shard.*

.. serverstatus:: shardingStatistics.totalDonorChunkCloneTimeMillis

   The cumulative time, in milliseconds, taken by the :ref:`clone phase
   of the chunk migrations <chunk-migration-procedure>` from this
   shard, of which this node is a member. Specifically, for each
   migration from this shard, the tracked time starts with the
   :dbcommand:`moveChunk` command and ends before the destination shard
   enters a catch-up phase to apply changes that occurred during the
   :ref:`chunk migrations <chunk-migration-procedure>`.

   *Only present when run on a shard.*

.. serverstatus:: shardingStatistics.totalCriticalSectionCommitTimeMillis

   The cumulative time, in milliseconds, taken by the :ref:`update
   metadata phase of the chunk migrations <chunk-migration-procedure>`
   from this shard, of which this node is a member. During the update
   metadata phase, all operations on the collection are blocked.

   *Only present when run on a shard.*

.. serverstatus:: shardingStatistics.totalCriticalSectionTimeMillis

   The cumulative time, in milliseconds, taken by the :ref:`catch-up
   phase and the update metadata phase of the chunk migrations
   <chunk-migration-procedure>` from this shard, of which this node is
   a member.

   To calculate the duration of the catch-up phase, subtract
   :serverstatus:`~shardingStatistics.totalCriticalSectionCommitTimeMillis` from
   :serverstatus:`~shardingStatistics.totalCriticalSectionTimeMillis`:

   .. code-block:: none

      totalCriticalSectionTimeMillis - totalCriticalSectionCommitTimeMillis

   *Only present when run on a shard.*

.. serverstatus:: shardingStatistics.countDocsClonedOnRecipient

   Cumulative, always-increasing count of documents that have been
   cloned on this member where it acted as the primary of the recipient
   shard.

   *Only present when run on a shard.*

   .. versionadded:: 4.2

.. serverstatus:: shardingStatistics.countDocsClonedOnDonor

   Cumulative, always-increasing count of documents that haves been
   cloned on this member where it acted as the primary of the donor
   shard.

   *Only present when run on a shard.*

   .. versionadded:: 4.2

.. serverstatus:: shardingStatistics.countRecipientMoveChunkStarted

   Cumulative, always-increasing count of chunks this member, acting as
   the primary of the recipient shard, has started to receive (whether
   the move has succeeded or not).

   *Only present when run on a shard.*

   .. versionadded:: 4.2

.. serverstatus:: shardingStatistics.countDocsDeletedOnDonor

   Cumulative, always-increasing count of documents that have been
   deleted on this member during chunk migration where the member acted
   as the primary of the donor shard.

   *Only present when run on a shard.*

   .. versionadded:: 4.2

.. serverstatus:: shardingStatistics.countDonorMoveChunkLockTimeout

   Cumulative, always-increasing count of chunk migrations that were
   aborted due to lock acquisition timeouts, where the member acted as
   the primary of the donor shard.

   *Only present when run on a shard.*

   .. versionadded:: 4.2

.. serverstatus:: shardingStatistics.unfinishedMigrationFromPreviousPrimary

   The number of unfinished migrations left by the previous
   primary after an election. This value is only updated after
   the newly-elected :binary:`~bin.mongod` completes the transition to
   primary.

   *Only present when run on a shard.*

   .. versionadded:: 4.4

.. serverstatus:: shardingStatistics.catalogCache

   A document with statistics about the cluster's routing information cache.

.. serverstatus:: shardingStatistics.catalogCache.numDatabaseEntries

   The total number of database entries that are currently in the
   catalog cache.

.. serverstatus:: shardingStatistics.catalogCache.numCollectionEntries

   The total number of collection entries (across all databases) that
   are currently in the catalog cache.

.. serverstatus:: shardingStatistics.catalogCache.countStaleConfigErrors

   The total number of times that threads hit stale config exception. A
   stale config exception triggers a refresh of the metadata.

.. serverstatus:: shardingStatistics.catalogCache.totalRefreshWaitTimeMicros

   The cumulative time, in microseconds, that threads had to wait for a
   refresh of the metadata.

.. serverstatus:: shardingStatistics.catalogCache.numActiveIncrementalRefreshes

   The number of incremental catalog cache refreshes that are currently
   waiting to complete.

.. serverstatus:: shardingStatistics.countIncrementalRefreshesStarted

   The cumulative number of incremental refreshes that have started.

.. serverstatus:: shardingStatistics.catalogCache.numActiveFullRefreshes

   The number of full catalog cache refreshes that are currently
   waiting to complete.

.. serverstatus:: shardingStatistics.catalogCache.countFullRefreshesStarted

   The cumulative number of full refreshes that have started.

.. serverstatus:: shardingStatistics.catalogCache.countFailedRefreshes

   The cumulative number of full or incremental refreshes that have failed.

.. serverstatus:: shardingStatistics.rangeDeleterTasks

   The current total of the queued chunk range deletion tasks that are
   ready to run or are running as part of the :ref:`chunk migration
   process <chunk-migration-procedure>`.

   Inspect the documents in the :data:`config.rangeDeletions` collection
   for information about the chunk ranges pending deletion from a shard
   after a chunk migration.

   *Only present when run on a shard member.*

   .. versionadded:: 4.4

.. serverstatus:: shardingStatistics.catalogCache.operationsBlockedByRefresh

   A document with statistics about operations blocked by catalog
   cache refresh activity on a :binary:`~bin.mongos`.

   Only present when run on a :binary:`~bin.mongos`.

   .. versionadded:: 4.2.7

.. serverstatus:: shardingStatistics.catalogCache.operationsBlockedByRefresh.countAllOperations

   The cumulative number of all operations ran on a
   :binary:`~bin.mongos` that were blocked at any point in their
   lifetime by a refresh of the catalog cache. This counter is the
   aggregate sum of all other ``operationsBlockedByRefresh`` metrics
   tracked below.

   Only present when run on a :binary:`~bin.mongos`.

   .. versionadded:: 4.2.7

.. serverstatus:: shardingStatistics.catalogCache.operationsBlockedByRefresh.countInserts

   The cumulative number of insert operations ran on a
   :binary:`~bin.mongos` that were blocked at any point in their
   lifetime by a refresh of the catalog cache.

   Only present when run on a :binary:`~bin.mongos`.

   .. versionadded:: 4.2.7

.. serverstatus:: shardingStatistics.catalogCache.operationsBlockedByRefresh.countQueries

   The cumulative number of query operations ran on a
   :binary:`~bin.mongos` that were blocked at any point in their
   lifetime by a refresh of the catalog cache.

   Only present when run on a :binary:`~bin.mongos`.

   .. versionadded:: 4.2.7

.. serverstatus:: shardingStatistics.catalogCache.operationsBlockedByRefresh.countUpdates

   The cumulative number of update operations ran on a
   :binary:`~bin.mongos` that were blocked at any point in their
   lifetime by a refresh of the catalog cache.

   Only present when run on a :binary:`~bin.mongos`.

   .. versionadded:: 4.2.7

.. serverstatus:: shardingStatistics.catalogCache.operationsBlockedByRefresh.countDeletes

   The cumulative number of delete operations ran on a
   :binary:`~bin.mongos` that were blocked at any point in their
   lifetime by a refresh of the catalog cache.

   Only present when run on a :binary:`~bin.mongos`.

   .. versionadded:: 4.2.7

.. serverstatus:: shardingStatistics.catalogCache.operationsBlockedByRefresh.countCommands

   The cumulative number of command operations ran on a
   :binary:`~bin.mongos` that were blocked at any point in their
   lifetime by a refresh of the catalog cache.

   Only present when run on a :binary:`~bin.mongos`.

   .. versionadded:: 4.2.7

.. serverstatus:: shardingStatistics.resharding

   A document with statistics about :ref:`resharding operations
   <sharding-resharding>`.

   Each shard returns its own resharding operation statistics. If a
   shard is not involved in a resharding operation, then that shard will
   not contain statistics about the resharding operation.

   *Only present when run on a shard or config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.countReshardingOperations

   The sum of
   :serverstatus:`~shardingStatistics.resharding.countReshardingSuccessful`,
   :serverstatus:`~shardingStatistics.resharding.countReshardingFailures`,
   and
   :serverstatus:`~shardingStatistics.resharding.countReshardingCanceled`.
   The sum is further incremented by ``1`` if a :ref:`resharding
   operation <sharding-resharding>` has started but has not yet
   completed. Sum is set to 0 when :binary:`~bin.mongod` is started or
   restarted.

   *Only present when run on a shard or config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.countReshardingSuccessful

   Number of successful :ref:`resharding operations
   <sharding-resharding>`. Number is set to 0 when :binary:`~bin.mongod`
   is started or restarted.

   *Only present when run on a shard or config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.countReshardingFailures

   Number of failed :ref:`resharding operations <sharding-resharding>`.
   Number is set to 0 when :binary:`~bin.mongod` is started or
   restarted.

   *Only present when run on a shard or config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.countReshardingCanceled

   Number of canceled :ref:`resharding operations
   <sharding-resharding>`. Number is set to 0 when :binary:`~bin.mongod`
   is started or restarted.

   *Only present when run on a shard or config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.totalOperationTimeElapsedMillis

   Total elapsed time, in milliseconds, for the current :ref:`resharding
   operation <sharding-resharding>`. Time is set to 0 when a new
   resharding operation starts.

   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.remainingOperationTimeEstimatedMillis

   Estimated remaining time, in milliseconds, for the current resharding
   operation. Time is set to 0 when a new :ref:`resharding operation
   <sharding-resharding>` starts.

   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.approxDocumentsToCopy

   Approximate number of documents to copy from donor shards to
   recipient shards for the current :ref:`resharding operation
   <sharding-resharding>`. Number is an estimate that is set when the
   resharding operation starts and the number is not updated as the
   operation progresses. Number is set to 0 when a new resharding
   operation starts.

   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.documentsCopied

   Number of documents copied from donor shards to recipient shards for
   the current :ref:`resharding operation <sharding-resharding>`. Number
   is set to 0 when a new resharding operation starts.

   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.approxBytesToCopy

   Approximate number of bytes to copy from donor shards to recipient
   shards for the current :ref:`resharding operation
   <sharding-resharding>`. Number is an estimate that is set when the
   resharding operation starts and the number is not updated as the
   operation progresses. Number is set to 0 when a new resharding
   operation starts.

   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.bytesCopied

   Number of bytes copied from donor shards to recipient shards for the
   current :ref:`resharding operation <sharding-resharding>`. Number is
   set to 0 when a new resharding operation starts.

   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.totalCopyTimeElapsedMillis

   Total elapsed time, in milliseconds, for ongoing data copy tasks from
   donor shards to recipient shards for the current :ref:`resharding
   operation <sharding-resharding>`. Time is set to 0 when a new
   resharding operation starts.

   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.oplogEntriesFetched

   Number of entries fetched from the :term:`oplog` for the current
   :ref:`resharding operation <sharding-resharding>`. Number is set to 0
   when a new resharding operation starts.

   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

.. serverstatus:: shardingStatistics.resharding.oplogEntriesApplied

   Number of entries applied to the :term:`oplog` for the current
   :ref:`resharding operation <sharding-resharding>`. Number is set to 0
   when a new resharding operation starts.

   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.totalApplyTimeElapsedMillis

   Total elapsed time, in milliseconds, for the apply step of the
   current :ref:`resharding operation <sharding-resharding>`. In the
   apply step, recipient shards modify their data based on new incoming
   writes from donor shards. Time is set to 0 when a new resharding
   operation starts.

   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.countWritesDuringCriticalSection

   Number of writes perfomed in the critical section for the current
   :ref:`resharding operation <sharding-resharding>`. The critical
   section prevents new incoming writes to the collection currently
   being resharded. Number is set to 0 when a new resharding operation
   starts.

   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.totalCriticalSectionTimeElapsedMillis

   Total elapsed time, in milliseconds, for the critical section of the
   current :ref:`resharding operation <sharding-resharding>`. The
   critical section prevents new incoming writes to the collection
   currently being resharded. Time is set to 0 when a new resharding
   operation starts.

   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.donorState

   State of the donor shard for the current :ref:`resharding operation
   <sharding-resharding>`. Number is set to 0 when a new
   resharding operation starts.

   .. list-table::
      :header-rows: 1
      :widths: 15 20 40

      * - Number Returned
        - Meaning
        - Description

      * - 0
        - ``unused``
        - The shard is not a donor in the current resharding operation.

      * - 1
        - ``preparing-to-donate``
        - The donor shard is preparing to donate data to the recipient
          shards.

      * - 2
        - ``donating-initial-data``
        - The donor shard is donating data to the recipient shards.

      * - 3
        - ``donating-oplog-entries``
        - The donor shard is donating :term:`oplog` entries to the
          recipient shards.

      * - 4
        - ``preparing-to-block-writes``
        - The donor shard is about to prevent new incoming write
          operations to the collection that is being resharded.

      * - 5
        - ``error``
        - An error occurred during the resharding operation.

      * - 6
        - ``blocking-writes``
        - The donor shard is preventing new incoming write operations
          and the donor shard has notified all recipient shards that new
          incoming writes are prevented.

      * - 7
        - ``done``
        - The donor shard has dropped the old sharded collection and the
          resharding operation is complete.

   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.recipientState

   State of the recipient shard for the current :ref:`resharding
   operation <sharding-resharding>`. Number is set to 0 when a new
   resharding operation starts.

   .. list-table::
      :header-rows: 1
      :widths: 15 20 40

      * - Number Returned
        - Meaning
        - Description

      * - 0
        - ``unused``
        - Shard is not a recipient in the current resharding operation.

      * - 1
        - ``awaiting-fetch-timestamp``
        - The recipient shard is waiting for the donor shards to be
          prepared to donate their data

      * - 2
        - ``creating-collection``
        - The recipient shard is creating the new sharded collection.

      * - 3
        - ``cloning``
        - The recipient shard is receiving data from the donor shards.

      * - 4
        - ``applying``
        - The recipient shard is applying :term:`oplog` entries to
          modify its copy of the data based on the new incoming writes
          from donor shards.

      * - 5
        - ``error``
        - An error occurred during the resharding operation.

      * - 6
        - ``strict-consistency``
        - The recipient shard has all data changes stored in a temporary
          collection.

      * - 7
        - ``done``
        - The resharding operation is complete.


   *Only present when run on a shard or config server. Returns 0 on a
   config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.numHostsTargeted

   Indicates the number of shards targeted for ``CRUD`` operations and 
   aggregation commands. When a ``CRUD`` operation or aggregation
   command is run, the following metrics will be incremented.

   .. include:: /includes/fact-server-status-num-hosts-targeted.rst

   .. note:: 

      Running the :dbcommand:`serverStatus` command on :binary:`mongos` 
      will provide insight into the CRUD and aggregation operations that
      run on a sharded cluster.

      Multi-shard operations can either be 
      :ref:`scatter-gather<sharding-query-patterns>`
      or shard specific. Multi-shard scatter-gather operations can
      :ref:`consume more resources<sharding-troubleshooting-scatter-gather>`.
      By using the 
      :serverstatus:`shardingStatistics.numHostsTargeted`
      metrics you can tune the aggregation queries that run on a 
      sharded cluster.

.. serverstatus:: shardingStatistics.resharding.coordinatorState

   State of the resharding coordinator for the current :ref:`resharding
   operation <sharding-resharding>`. The resharding coordinator is a
   thread that runs on the :doc:`config server
   </core/sharded-cluster-config-servers>` primary. Number is set to 0
   when a new resharding operation starts.

   .. list-table::
      :header-rows: 1
      :widths: 15 20 40

      * - Number Returned
        - Meaning
        - Description

      * - 0
        - ``unused``
        - The shard is not the coordinator in the current resharding
          operation.

      * - 1
        - ``initializing``
        - The resharding coordinator has inserted the coordinator
          document into ``config.reshardingOperations`` and has added
          the ``reshardingFields`` to the ``config.collections`` entry
          for the original collection.

      * - 2
        - ``preparing-to-donate``
        - The resharding coordinator

          - has created a ``config.collections`` entry for the temporary
            resharding collection.
          - has inserted entries into ``config.chunks`` for ranges based
            on the new shard key.
          - has inserted entries into ``config.tags`` for any zones
            associated with the new shard key.

          The coordinator informs participant shards to begin the
          resharding operation. The coordinator then waits until all
          donor shards have picked a ``minFetchTimestamp`` and are ready
          to donate.

      * - 3
        - ``cloning``
        - The resharding coordinator informs donor shards to donate data
          to recipient shards. The coordinator waits for all recipients
          to finish cloning the data from the donor.

      * - 4
        - ``applying``
        - The resharding coordinator informs recipient shards to modify
          their copies of data based on new incoming writes from donor
          shards. The coordinator waits for all recipients to finish
          applying :term:`oplog` entries.

      * - 5
        - ``blocking-writes``
        - The resharding coordinator informs donor shards to prevent new
          incoming write operations to the collection being resharded.
          The coordinator then waits for all recipients to have all data
          changes.

      * - 6
        - ``aborting``
        - An unrecoverable error occurred during the resharding
          operation or the :dbcommand:`abortReshardCollection` command
          (or the :method:`sh.abortReshardCollection()` method) was run.

      * - 6
        - ``committing``
        - The resharding coordinator removes the ``config.collections``
          entry for the temporary resharding collection. The coordinator
          then adds the ``recipientFields`` to the source collection's
          entry.

   *Only present when run on a shard or config server.*

   .. versionadded:: 5.0

.. serverstatus:: shardingStatistics.resharding.opStatus

   Status for the current :ref:`resharding operation
   <sharding-resharding>`.

   .. list-table::
      :header-rows: 1
      :widths: 10 40

      * - Number Returned
        - Description

      * - -1
        - Resharding operation not in progress.

      * - 0
        - Resharding operation succeeded.

      * - 1
        - Resharding operation failed.

      * - 2
        - Resharding operation canceled.

   *Only present when run on a shard or config server.*

   .. versionadded:: 5.0

.. _server-status-sharded-index-consistency:

shardedIndexConsistency
~~~~~~~~~~~~~~~~~~~~~~~

.. code-block:: javascript

   "shardedIndexConsistency" : {
      "numShardedCollectionsWithInconsistentIndexes" : NumberLong(<num>)
   },

.. serverstatus:: shardedIndexConsistency

   *Available only on config server instances.*

   A document that returns results of index consistency checks for
   sharded collections.

   The returned metrics are meaningful only when run on the primary of
   the :doc:`config server replica set
   </core/sharded-cluster-config-servers>` for a version 4.4+ (and
   4.2.6+) sharded cluster.

   .. seealso::

      - :parameter:`enableShardedIndexConsistencyCheck` parameter
      - :parameter:`shardedIndexConsistencyCheckIntervalMS` parameter

   *New in version 4.4. (and 4.2.6)*

.. serverstatus:: shardedIndexConsistency.numShardedCollectionsWithInconsistentIndexes

   *Available only on config server instances.*

   Number of sharded collections whose indexes are inconsistent across
   the shards. A sharded collection has an inconsistent index if the
   collection does not have the exact same indexes (including the index
   options) on each shard that contains chunks for the collection.

   To investigate if a sharded collection has inconsistent indexes, see
   :ref:`manage-indexes-find-inconsistent-indexes`.

   The returned metrics are meaningful only when run on the primary of
   the :doc:`config server replica set
   </core/sharded-cluster-config-servers>` for a version 4.4+ (and
   4.2.6+) sharded cluster.

   .. seealso::

      - :parameter:`enableShardedIndexConsistencyCheck` parameter
      - :parameter:`shardedIndexConsistencyCheckIntervalMS` parameter

   *New in version 4.4. (and 4.2.6)*

.. _server-status-storage-engine:

storageEngine
~~~~~~~~~~~~~

.. code-block:: javascript

   "storageEngine" : {
      "name" : <string>,
      "supportsCommittedReads" : <boolean>,
      "persistent" : <boolean>
   },

.. serverstatus:: storageEngine

   A document with data about the current storage engine.

.. serverstatus:: storageEngine.name

   The name of the current storage engine.

.. serverstatus:: storageEngine.supportsCommittedReads

   .. versionadded:: 3.2

   A boolean that indicates whether the storage engine supports
   :readconcern:`"majority"` :doc:`read concern
   </reference/read-concern>`.

.. serverstatus:: storageEngine.persistent

   .. versionadded:: 3.2.6

   A boolean that indicates whether the :doc:`storage engine
   </core/storage-engines>` does or does not persist data to disk.

.. _server-status-transactions:

transactions
~~~~~~~~~~~~

.. tabs::

   tabs:

      - id: mongod
        name: mongod
        content: |

           .. versionadded:: 3.6.3

           .. code-block:: javascript

              "transactions" : {
                 "retriedCommandsCount" : NumberLong(<num>),
                 "retriedStatementsCount" : NumberLong(<num>),
                 "transactionsCollectionWriteCount" : NumberLong(<num>),
                 "currentActive" : NumberLong(<num>),
                 "currentInactive" : NumberLong(<num>),
                 "currentOpen" : NumberLong(<num>),
                 "totalAborted" : NumberLong(<num>),
                 "totalCommitted" : NumberLong(<num>),
                 "totalStarted" : NumberLong(<num>),
                 "totalPrepared" : NumberLong(<num>),
                 "totalPreparedThenCommitted" : NumberLong(<num>),
                 "totalPreparedThenAborted" :  NumberLong(<num>),
                 "currentPrepared" :  NumberLong(<num>),
                 "lastCommittedTransaction" : <document> // Starting in 4.2.2 (and 4.0.9)
              },

      - id: mongos
        name: mongos
        content: |

           .. versionadded:: 4.2

           .. code-block:: javascript

              "transactions" : {
                 "currentOpen" : NumberLong(<num>),     // Starting in 4.2.1
                 "currentActive" : NumberLong(<num>),   // Starting in 4.2.1
                 "currentInactive" : NumberLong(<num>), // Starting in 4.2.1
                 "totalStarted" : NumberLong(<num>),
                 "totalCommitted" : NumberLong(<num>),
                 "totalAborted" : NumberLong(<num>),
                 "abortCause" : {
                    <String1> : NumberLong(<num>),
                    <String2>" : NumberLong(<num>),
                    ...
                 },
                 "totalContactedParticipants" : NumberLong(<num>),
                 "totalParticipantsAtCommit" : NumberLong(<num>),
                 "totalRequestsTargeted" : NumberLong(<num>),
                 "commitTypes" : {
                    "noShards" : {
                       "initiated" : NumberLong(<num>),
                       "successful" : NumberLong(<num>),
                       "successfulDurationMicros" : NumberLong(<num>)
                    },
                    "singleShard" : {
                       "initiated" : NumberLong(<num>),
                       "successful" : NumberLong(<num>),
                       "successfulDurationMicros" : NumberLong(<num>)
                    },
                    "singleWriteShard" : {
                       "initiated" : NumberLong(<num>),
                       "successful" : NumberLong(<num>),
                       "successfulDurationMicros" : NumberLong(<num>)
                    },
                    "readOnly" : {
                       "initiated" : NumberLong(<num>),
                       "successful" : NumberLong(<num>),
                       "successfulDurationMicros" : NumberLong(<num>)
                    },
                    "twoPhaseCommit" : {
                       "initiated" : NumberLong(<num>),
                       "successful" : NumberLong(<num>),
                       "successfulDurationMicros" : NumberLong(<num>)
                    },
                    "recoverWithToken" : {
                       "initiated" : NumberLong(<num>),
                       "successful" : NumberLong(<num>),
                       "successfulDurationMicros" : NumberLong(<num>)
                    }
                 }
              },

.. serverstatus:: transactions

   *Available on mongod in 3.6.3+ and on mongos in 4.2+.*

   When run on a :binary:`~bin.mongod`, a document with data about the
   :doc:`retryable writes </core/retryable-writes>` and
   :doc:`transactions </core/transactions>`.

   When run on a :binary:`~bin.mongos`, a document with data about the
   :doc:`transactions </core/transactions>` run on the instance.

.. serverstatus:: transactions.retriedCommandsCount

   |mongod-only|

   The total number of retry attempts that have been received after the
   corresponding retryable write command has already been committed.
   That is, a retryable write is attempted even though the write has
   previously succeeded and has an associated record for the
   transaction and session in the :data:`config.transactions`
   collection, such as when the initial write response to the client is
   lost.

   .. note::

      MongoDB does not re-execute the committed writes.

   The total is across all sessions.

   The total does not include any retryable writes that may happen
   internally as part of a chunk migration.

   .. versionadded:: 3.6.3

.. serverstatus:: transactions.retriedStatementsCount

   |mongod-only|

   The total number of write statements associated with the retried
   commands in :serverstatus:`transactions.retriedCommandsCount`.

   .. note::

      MongoDB does not re-execute the committed writes.

   The total does not include any retryable writes that may happen
   internally as part of a chunk migration.

   .. versionadded:: 3.6.3

.. serverstatus:: transactions.transactionsCollectionWriteCount

   |mongod-only|

   The total number of writes to the :data:`config.transactions`
   collection, triggered when a new retryable write statement is
   committed.

   For update and delete commands, since only single document
   operations are retryable, there is one write per statement.

   For insert operations, there is one write per batch of documents
   inserted, except when a failure leads to each document being
   inserted separately.

   The total includes writes to a server's :data:`config.transactions`
   collection that occur as part of a migration.

   .. versionadded:: 3.6.3

.. serverstatus:: transactions.currentActive

   *Available on mongod in 4.0.2+ and mongos in 4.2.1+*

   The total number of open transactions currently executing a command.

.. serverstatus:: transactions.currentInactive

   *Available on mongod in 4.0.2+ and mongos in 4.2.1+*

   The total number of open transactions that are not currently
   executing a command.

.. serverstatus:: transactions.currentOpen

   *Available on mongod in 4.0.2+ and mongos in 4.2.1+*

   The total number of open transactions. A transaction is opened when
   the first command is run as a part of that transaction, and stays
   open until the transaction either commits or aborts.

.. serverstatus:: transactions.totalAborted

   *Available on mongod in 4.0.2+ and mongos in 4.2+.*

   For the :binary:`~bin.mongod`, the total number of transactions
   aborted on this instance since its last startup.

   For the :binary:`~bin.mongos`, the total number of transactions
   aborted through this instance since its last startup.

.. serverstatus:: transactions.totalCommitted

   *Available on mongod in 4.0.2+ and mongos in 4.2+.*

   For the :binary:`~bin.mongod`, the total number of transactions
   committed on the instance since its last startup.

   For the :binary:`~bin.mongos`,the total number of transactions
   committed through this instance since its last startup.

.. serverstatus:: transactions.totalStarted

   *Available on mongod in 4.0.2+ and mongos in 4.2+.*

   For the :binary:`~bin.mongod`, the total number of transactions
   started on this instance since its last startup.

   For the :binary:`~bin.mongos`, the total number of transactions
   started on this instance since its last startup.

.. serverstatus:: transactions.abortCause

   |mongos-only|

   Breakdown of the :serverstatus:`transactions.totalAborted` by cause.
   If a client issues an explicit ``abortTransaction``, the cause is
   listed as ``abort``.

   For example:

   .. code-block:: javascript

      "totalAborted" : NumberLong(5),
      "abortCause" : {
         "abort" : NumberLong(1),
         "DuplicateKey" : NumberLong(1),
         "StaleConfig" : NumberLong(3),
         "SnapshotTooOld" : NumberLong(1)
      },

   .. versionadded:: 4.2

.. serverstatus:: transactions.totalContactedParticipants

   |mongos-only|

   The total number of shards contacted for all transactions started
   through this :binary:`~bin.mongos` since its last startup.

   The number of shards contacted during the transaction processes can
   include those shards that may not be included as part of the commit.

   .. versionadded:: 4.2

.. serverstatus:: transactions.totalParticipantsAtCommit

   |mongos-only|

   Total number of shards involved in the commit for all transactions
   started through this :binary:`~bin.mongos` since its last startup.

   .. versionadded:: 4.2

.. serverstatus:: transactions.totalRequestsTargeted

   |mongos-only|

   Total number of network requests targeted by the
   :binary:`~bin.mongos` as part of its transactions.

   .. versionadded:: 4.2

.. serverstatus:: transactions.commitTypes

   |mongos-only|

   Breakdown of the commits by types. For example:

   .. code-block:: javascript
      :copyable: false

      "noShards" : {
         "initiated" : NumberLong(0),
         "successful" : NumberLong(0),
         "successfulDurationMicros" : NumberLong(0)
      },
      "singleShard" : {
         "initiated" : NumberLong(5),
         "successful" : NumberLong(5),
         "successfulDurationMicros" : NumberLong(203118)
      },
      "singleWriteShard" : {
         "initiated" : NumberLong(0),
         "successful" : NumberLong(0),
         "successfulDurationMicros" : NumberLong(0)
      },
      "readOnly" : {
         "initiated" : NumberLong(0),
         "successful" : NumberLong(0),
         "successfulDurationMicros" : NumberLong(0)
      },
      "twoPhaseCommit" : {
         "initiated" : NumberLong(1),
         "successful" : NumberLong(1),
         "successfulDurationMicros" : NumberLong(179616)
      },
      "recoverWithToken" : {
         "initiated" : NumberLong(0),
         "successful" : NumberLong(0),
         "successfulDurationMicros" : NumberLong(0)
      }

   The types of commit are:

   .. list-table::
      :header-rows: 1
      :widths: 20 80

      * - Type
        - Description

      * - ``noShards``

        - Commits of transactions that did not contact any shards.

      * - ``singleShard``

        - Commits of transactions that affected a single shard.

      * - ``singleWriteShard``

        - Commits of transactions that contacted multiple shards but
          whose write operations only affected a single shard.

      * - ``readOnly``

        - Commits of transactions that only involved read operations.

      * - ``twoPhaseCommit``

        - Commits of transactions that included writes to multiple
          shards

      * - ``recoverWithToken``

        - Commits that recovered the outcome of transactions from
          another instance or after this instance was restarted.

   For each commit type, the command returns the following metrics:

   .. list-table::
      :header-rows: 1
      :widths: 20 80

      * - Metrics
        - Description

      * - ``initiated``

        - Total number of times that commits of this type were
          initiated.

      * - ``successful``

        - Total number of times that commits of this type succeeded.

      * - ``successfulDurationMicros``

        - Total time, in microseconds, taken by successful commits of
          this type.

   .. versionadded:: 4.2

.. serverstatus:: transactions.totalPrepared

   |mongod-only|

   The total number of transactions in prepared state on this server
   since the :binary:`mongod <bin.mongod>` process's last startup.

   .. versionadded:: 4.2

.. serverstatus:: transactions.totalPreparedThenCommitted

   |mongod-only|

   The total number of transactions that were prepared and committed on
   this server since the :binary:`mongod <bin.mongod>` process's last
   startup.

   .. versionadded:: 4.2

.. serverstatus:: transactions.totalPreparedThenAborted

   |mongod-only|

   The total number of transactions that were prepared and aborted on
   this server since the :binary:`mongod <bin.mongod>` process's last
   startup.

   .. versionadded:: 4.2

.. serverstatus:: transactions.currentPrepared

   |mongod-only|

   The current number of transactions in prepared state on this server.

   .. versionadded:: 4.2

.. serverstatus:: transactions.lastCommittedTransaction

   |mongod-only|

   The details of the last transaction committed when the
   :binary:`mongod <bin.mongod>` is primary.

   When returned from a secondary,
   :serverstatus:`~transactions.lastCommittedTransaction` returns the
   details of the last transaction committed when that secondary was a
   primary.

   .. code-block:: javascript
      :copyable: false

      "lastCommittedTransaction" : {
         "operationCount" : NumberLong(1),
         "oplogOperationBytes" : NumberLong(211),
         "writeConcern" : {
            "w" : "majority",
            "wtimeout" : 0
         }
      }

   .. list-table::
      :header-rows: 1
      :widths: 20 80

      * - Metrics
        - Description

      * - ``operationCount``
        - The number of write operations in the transaction.

      * - ``oplogOperationBytes``

        - The size of the corresponding oplog entry or entries for
          the transaction. [#oplog-change]_

      * - ``writeConcern``
        - The write concern used for the transaction.

   .. versionadded:: 4.2.2 (*Also available in 4.0.9*)

.. [#oplog-change]

   Starting in version 4.2, MongoDB creates as many oplog entries as
   necessary to encapsulate all write operations in a transaction
   whereas in version 4.0, the write operations in a transaction must
   fit within a single oplog entry. See :ref:`txn-oplog-size-limit` for
   details.


transportSecurity
~~~~~~~~~~~~~~~~~

.. versionadded:: 4.0.2 (*Also available in 3.6.7+ and 3.4.17+*)

.. code-block:: javascript

   "transportSecurity" : {
      "1.0" : NumberLong(<num>),
      "1.1" : NumberLong(<num>),
      "1.2" : NumberLong(<num>),
      "1.3" : NumberLong(<num>),
      "unknown" : NumberLong(<num>)
   },

.. serverstatus:: transportSecurity.<version>

   .. versionadded:: 4.0.2 (*Also available in 3.6.7+ and 3.4.17+*)

   The cumulative number of TLS <version> connections that have been
   made to this :binary:`~bin.mongod` or :binary:`~bin.mongos`
   instance. The value is reset upon restart.


.. _server-status-wiredTiger:

wiredTiger
~~~~~~~~~~

``wiredTiger`` information only appears if using the :doc:`WiredTiger
</core/wiredtiger>` storage engine. Some of the statistics roll up for the server.

.. code-block:: javascript

   {
      "uri" : "statistics:",
      "async" : {
         "current work queue length" : <num>,
         "maximum work queue length" : <num>,
         "number of allocation state races" : <num>,
         "number of flush calls" : <num>,
         "number of operation slots viewed for allocation" : <num>,
         "number of times operation allocation failed" : <num>,
         "number of times worker found no work" : <num>,
         "total allocations" : <num>,
         "total compact calls" : <num>,
         "total insert calls" : <num>,
         "total remove calls" : <num>,
         "total search calls" : <num>,
         "total update calls" : <num>
      },
      "block-manager" : {
         "blocks pre-loaded" : <num>,
         "blocks read" : <num>,
         "blocks written" : <num>,
         "bytes read" : <num>,
         "bytes written" : <num>,
         "bytes written for checkpoint" : <num>,
         "mapped blocks read" : <num>,
         "mapped bytes read" : <num>
      },
      "cache" : {
         "application threads page read from disk to cache count" : <num>,
         "application threads page read from disk to cache time (usecs)" : <num>,
         "application threads page write from cache to disk count" : <num>,
         "application threads page write from cache to disk time (usecs)" : <num>,
         "bytes belonging to page images in the cache" : <num>,
         "bytes belonging to the cache overflow table in the cache" : <num>,
         "bytes currently in the cache" : <num>,
         "bytes dirty in the cache cumulative" : <num>,
         "bytes not belonging to page images in the cache" : <num>,
         "bytes read into cache" : <num>,
         "bytes written from cache" : <num>,
         "cache overflow cursor application thread wait time (usecs)" : <num>,
         "cache overflow cursor internal thread wait time (usecs)" : <num>,
         "cache overflow score" : <num>,
         "cache overflow table entries" : <num>,
         "cache overflow table insert calls" : <num>,
         "cache overflow table max on-disk size" : <num>,
         "cache overflow table on-disk size" : <num>,
         "cache overflow table remove calls" : <num>,
         "checkpoint blocked page eviction" : <num>,
         "eviction calls to get a page" : <num>,
         "eviction calls to get a page found queue empty" : <num>,
         "eviction calls to get a page found queue empty after locking" : <num>,
         "eviction currently operating in aggressive mode" : <num>,
         "eviction empty score" : <num>,
         "eviction passes of a file" : <num>,
         "eviction server candidate queue empty when topping up" : <num>,
         "eviction server candidate queue not empty when topping up" : <num>,
         "eviction server evicting pages" : <num>,
         "eviction server slept, because we did not make progress with eviction" : <num>,
         "eviction server unable to reach eviction goal" : <num>,
         "eviction server waiting for a leaf page" : <num>,
         "eviction server waiting for an internal page sleep (usec)" : <num>,
         "eviction server waiting for an internal page yields" : <num>,
         "eviction state" : <num>,
         "eviction walk target pages histogram - 0-9" : <num>,
         "eviction walk target pages histogram - 10-31" : <num>,
         "eviction walk target pages histogram - 128 and higher" : <num>,
         "eviction walk target pages histogram - 32-63" : <num>,
         "eviction walk target pages histogram - 64-128" : <num>,
         "eviction walks abandoned" : <num>,
         "eviction walks gave up because they restarted their walk twice" : <num>,
         "eviction walks gave up because they saw too many pages and found no candidates" : <num>,
         "eviction walks gave up because they saw too many pages and found too few candidates" : <num>,
         "eviction walks reached end of tree" : <num>,
         "eviction walks started from root of tree" : <num>,
         "eviction walks started from saved location in tree" : <num>,
         "eviction worker thread active" : <num>,
         "eviction worker thread created" : <num>,
         "eviction worker thread evicting pages" : <num>,
         "eviction worker thread removed" : <num>,
         "eviction worker thread stable number" : <num>,
         "files with active eviction walks" : <num>,
         "files with new eviction walks started" : <num>,
         "force re-tuning of eviction workers once in a while" : <num>,
         "forced eviction - pages evicted that were clean count" : <num>,
         "forced eviction - pages evicted that were clean time (usecs)" : <num>,
         "forced eviction - pages evicted that were dirty count" : <num>,
         "forced eviction - pages evicted that were dirty time (usecs)" : <num>,
         "forced eviction - pages selected because of too many deleted items count" : <num>,
         "forced eviction - pages selected count" : <num>,
         "forced eviction - pages selected unable to be evicted count" : <num>,
         "forced eviction - pages selected unable to be evicted time" : <num>,
         "hazard pointer blocked page eviction" : <num>,
         "hazard pointer check calls" : <num>,
         "hazard pointer check entries walked" : <num>,
         "hazard pointer maximum array length" : <num>,
         "in-memory page passed criteria to be split" : <num>,
         "in-memory page splits" : <num>,
         "internal pages evicted" : <num>,
         "internal pages split during eviction" : <num>,
         "leaf pages split during eviction" : <num>,
         "maximum bytes configured" : <num>,
         "maximum page size at eviction" : <num>,
         "modified pages evicted" : <num>,
         "modified pages evicted by application threads" : <num>,
         "operations timed out waiting for space in cache" : <num>,
         "overflow pages read into cache" : <num>,
         "page split during eviction deepened the tree" : <num>,
         "page written requiring cache overflow records" : <num>,
         "pages currently held in the cache" : <num>,
         "pages evicted by application threads" : <num>,
         "pages queued for eviction" : <num>,
         "pages queued for eviction post lru sorting" : <num>,
         "pages queued for urgent eviction" : <num>,
         "pages queued for urgent eviction during walk" : <num>,
         "pages read into cache" : <num>,
         "pages read into cache after truncate" : <num>,
         "pages read into cache after truncate in prepare state" : <num>,
         "pages read into cache requiring cache overflow entries" : <num>,
         "pages read into cache requiring cache overflow for checkpoint" : <num>,
         "pages read into cache skipping older cache overflow entries" : <num>,
         "pages read into cache with skipped cache overflow entries needed later" : <num>,
         "pages read into cache with skipped cache overflow entries needed later by checkpoint" : <num>,
         "pages requested from the cache" : <num>,
         "pages seen by eviction walk" : <num>,
         "pages selected for eviction unable to be evicted" : <num>,
         "pages walked for eviction" : <num>,
         "pages written from cache" : <num>,
         "pages written requiring in-memory restoration" : <num>,
         "percentage overhead" : <num>,
         "tracked bytes belonging to internal pages in the cache" : <num>,
         "tracked bytes belonging to leaf pages in the cache" : <num>,
         "tracked dirty bytes in the cache" : <num>,
         "tracked dirty pages in the cache" : <num>,
         "unmodified pages evicted" : <num>
      },
      "capacity" : {
         "background fsync file handles considered" : <num>,
         "background fsync file handles synced" : <num>,
         "background fsync time (msecs)" : <num>,
         "bytes read" : <num>,
         "bytes written for checkpoint" : <num>,
         "bytes written for eviction" : <num>,
         "bytes written for log" : <num>,
         "bytes written total" : <num>,
         "threshold to call fsync" : <num>,
         "time waiting due to total capacity (usecs)" : <num>,
         "time waiting during checkpoint (usecs)" : <num>,
         "time waiting during eviction (usecs)" : <num>,
         "time waiting during logging (usecs)" : <num>,
         "time waiting during read (usecs)" : <num>
      },
      "connection" : {
         "auto adjusting condition resets" : <num>,
         "auto adjusting condition wait calls" : <num>,
         "detected system time went backwards" : <num>,
         "files currently open" : <num>,
         "memory allocations" : <num>,
         "memory frees" : <num>,
         "memory re-allocations" : <num>,
         "pthread mutex condition wait calls" : <num>,
         "pthread mutex shared lock read-lock calls" : <num>,
         "pthread mutex shared lock write-lock calls" : <num>,
         "total fsync I/Os" : <num>,
         "total read I/Os" : <num>,
         "total write I/Os" : <num>
      },
      "cursor" : {
         "cached cursor count" : <num>,
         "cursor bulk loaded cursor insert calls" : <num>,
         "cursor close calls that result in cache" : <num>,
         "cursor create calls" : <num>,
         "cursor insert calls" : <num>,
         "cursor insert key and value bytes" : <num>,
         "cursor modify calls" : <num>,
         "cursor modify key and value bytes affected" : <num>,
         "cursor modify value bytes modified" : <num>,
         "cursor next calls" : <num>,
         "cursor operation restarted" : <num>,
         "cursor prev calls" : <num>,
         "cursor remove calls" : <num>,
         "cursor remove key bytes removed" : <num>,
         "cursor reserve calls" : <num>,
         "cursor reset calls" : <num>,
         "cursor search calls" : <num>,
         "cursor search near calls" : <num>,
         "cursor sweep buckets" : <num>,
         "cursor sweep cursors closed" : <num>,
         "cursor sweep cursors examined" : <num>,
         "cursor sweeps" : <num>,
         "cursor truncate calls" : <num>,
         "cursor update calls" : <num>,
         "cursor update key and value bytes" : <num>,
         "cursor update value size change" : <num>,
         "cursors reused from cache" : <num>,
         "open cursor count" : <num>
      },
      "data-handle" : {
         "connection data handle size" : <num>,
         "connection data handles currently active" : <num>,
         "connection sweep candidate became referenced" : <num>,
         "connection sweep dhandles closed" : <num>,
         "connection sweep dhandles removed from hash list" : <num>,
         "connection sweep time-of-death sets" : <num>,
         "connection sweeps" : <num>,
         "session dhandles swept" : <num>,
         "session sweep attempts" : <num>
      },
      "lock" : {
         "checkpoint lock acquisitions" : <num>,
         "checkpoint lock application thread wait time (usecs)" : <num>,
         "checkpoint lock internal thread wait time (usecs)" : <num>,
         "dhandle lock application thread time waiting (usecs)" : <num>,
         "dhandle lock internal thread time waiting (usecs)" : <num>,
         "dhandle read lock acquisitions" : <num>,
         "dhandle write lock acquisitions" : <num>,
         "durable timestamp queue lock application thread time waiting (usecs)" : <num>,
         "durable timestamp queue lock internal thread time waiting (usecs)" : <num>,
         "durable timestamp queue read lock acquisitions" : <num>,
         "durable timestamp queue write lock acquisitions" : <num>,
         "metadata lock acquisitions" : <num>,
         "metadata lock application thread wait time (usecs)" : <num>,
         "metadata lock internal thread wait time (usecs)" : <num>,
         "read timestamp queue lock application thread time waiting (usecs)" : <num>,
         "read timestamp queue lock internal thread time waiting (usecs)" : <num>,
         "read timestamp queue read lock acquisitions" : <num>,
         "read timestamp queue write lock acquisitions" : <num>,
         "schema lock acquisitions" : <num>,
         "schema lock application thread wait time (usecs)" : <num>,
         "schema lock internal thread wait time (usecs)" : <num>,
         "table lock application thread time waiting for the table lock (usecs)" : <num>,
         "table lock internal thread time waiting for the table lock (usecs)" : <num>,
         "table read lock acquisitions" : <num>,
         "table write lock acquisitions" : <num>,
         "txn global lock application thread time waiting (usecs)" : <num>,
         "txn global lock internal thread time waiting (usecs)" : <num>,
         "txn global read lock acquisitions" : <num>,
         "txn global write lock acquisitions" : <num>
      },
      "log" : {
         "busy returns attempting to switch slots" : <num>,
         "force archive time sleeping (usecs)" : <num>,
         "log bytes of payload data" : <num>,
         "log bytes written" : <num>,
         "log files manually zero-filled" : <num>,
         "log flush operations" : <num>,
         "log force write operations" : <num>,
         "log force write operations skipped" : <num>,
         "log records compressed" : <num>,
         "log records not compressed" : <num>,
         "log records too small to compress" : <num>,
         "log release advances write LSN" : <num>,
         "log scan operations" : <num>,
         "log scan records requiring two reads" : <num>,
         "log server thread advances write LSN" : <num>,
         "log server thread write LSN walk skipped" : <num>,
         "log sync operations" : <num>,
         "log sync time duration (usecs)" : <num>,
         "log sync_dir operations" : <num>,
         "log sync_dir time duration (usecs)" : <num>,
         "log write operations" : <num>,
         "logging bytes consolidated" : <num>,
         "maximum log file size" : <num>,
         "number of pre-allocated log files to create" : <num>,
         "pre-allocated log files not ready and missed" : <num>,
         "pre-allocated log files prepared" : <num>,
         "pre-allocated log files used" : <num>,
         "records processed by log scan" : <num>,
         "slot close lost race" : <num>,
         "slot close unbuffered waits" : <num>,
         "slot closures" : <num>,
         "slot join atomic update races" : <num>,
         "slot join calls atomic updates raced" : <num>,
         "slot join calls did not yield" : <num>,
         "slot join calls found active slot closed" : <num>,
         "slot join calls slept" : <num>,
         "slot join calls yielded" : <num>,
         "slot join found active slot closed" : <num>,
         "slot joins yield time (usecs)" : <num>,
         "slot transitions unable to find free slot" : <num>,
         "slot unbuffered writes" : <num>,
         "total in-memory size of compressed records" : <num>,
         "total log buffer size" : <num>,
         "total size of compressed records" : <num>,
         "written slots coalesced" : <num>,
         "yields waiting for previous log file close" : <num>
      },
      "perf" : {
         "file system read latency histogram (bucket 1) - 10-49ms" : <num>,
         "file system read latency histogram (bucket 2) - 50-99ms" : <num>,
         "file system read latency histogram (bucket 3) - 100-249ms" : <num>,
         "file system read latency histogram (bucket 4) - 250-499ms" : <num>,
         "file system read latency histogram (bucket 5) - 500-999ms" : <num>,
         "file system read latency histogram (bucket 6) - 1000ms+" : <num>,
         "file system write latency histogram (bucket 1) - 10-49ms" : <num>,
         "file system write latency histogram (bucket 2) - 50-99ms" : <num>,
         "file system write latency histogram (bucket 3) - 100-249ms" : <num>,
         "file system write latency histogram (bucket 4) - 250-499ms" : <num>,
         "file system write latency histogram (bucket 5) - 500-999ms" : <num>,
         "file system write latency histogram (bucket 6) - 1000ms+" : <num>,
         "operation read latency histogram (bucket 1) - 100-249us" : <num>,
         "operation read latency histogram (bucket 2) - 250-499us" : <num>,
         "operation read latency histogram (bucket 3) - 500-999us" : <num>,
         "operation read latency histogram (bucket 4) - 1000-9999us" : <num>,
         "operation read latency histogram (bucket 5) - 10000us+" : <num>,
         "operation write latency histogram (bucket 1) - 100-249us" : <num>,
         "operation write latency histogram (bucket 2) - 250-499us" : <num>,
         "operation write latency histogram (bucket 3) - 500-999us" : <num>,
         "operation write latency histogram (bucket 4) - 1000-9999us" : <num>,
         "operation write latency histogram (bucket 5) - 10000us+" : <num>
      },
      "reconciliation" : {
         "fast-path pages deleted" : <num>,
         "page reconciliation calls" : <num>,
         "page reconciliation calls for eviction" : <num>,
         "pages deleted" : <num>,
         "split bytes currently awaiting free" : <num>,
         "split objects currently awaiting free" : <num>
      },
      "session" : {
         "open session count" : <num>,
         "session query timestamp calls" : <num>,
         "table alter failed calls" : <num>,
         "table alter successful calls" : <num>,
         "table alter unchanged and skipped" : <num>,
         "table compact failed calls" : <num>,
         "table compact successful calls" : <num>,
         "table create failed calls" : <num>,
         "table create successful calls" : <num>,
         "table drop failed calls" : <num>,
         "table drop successful calls" : <num>,
         "table import failed calls" : <num>,
         "table import successful calls" : <num>,
         "table rebalance failed calls" : <num>,
         "table rebalance successful calls" : <num>,
         "table rename failed calls" : <num>,
         "table rename successful calls" : <num>,
         "table salvage failed calls" : <num>,
         "table salvage successful calls" : <num>,
         "table truncate failed calls" : <num>,
         "table truncate successful calls" : <num>,
         "table verify failed calls" : <num>,
         "table verify successful calls" : <num>
      },
      "thread-state" : {
         "active filesystem fsync calls" : <num>,
         "active filesystem read calls" : <num>,
         "active filesystem write calls" : <num>
      },
      "thread-yield" : {
         "application thread time evicting (usecs)" : <num>,
         "application thread time waiting for cache (usecs)" : <num>,
         "connection close blocked waiting for transaction state stabilization" : <num>,
         "connection close yielded for lsm manager shutdown" : <num>,
         "data handle lock yielded" : <num>,
         "get reference for page index and slot time sleeping (usecs)" : <num>,
         "log server sync yielded for log write" : <num>,
         "page access yielded due to prepare state change" : <num>,
         "page acquire busy blocked" : <num>,
         "page acquire eviction blocked" : <num>,
         "page acquire locked blocked" : <num>,
         "page acquire read blocked" : <num>,
         "page acquire time sleeping (usecs)" : <num>,
         "page delete rollback time sleeping for state change (usecs)" : <num>,
         "page reconciliation yielded due to child modification" : <num>
      },
      "transaction" : {
         "Number of prepared updates" : <num>,
         "Number of prepared updates added to cache overflow" : <num>,
         "Number of prepared updates resolved" : <num>,
         "durable timestamp queue entries walked" : <num>,
         "durable timestamp queue insert to empty" : <num>,
         "durable timestamp queue inserts to head" : <num>,
         "durable timestamp queue inserts total" : <num>,
         "durable timestamp queue length" : <num>,
         "number of named snapshots created" : <num>,
         "number of named snapshots dropped" : <num>,
         "prepared transactions" : <num>,
         "prepared transactions committed" : <num>,
         "prepared transactions currently active" : <num>,
         "prepared transactions rolled back" : <num>,
         "query timestamp calls" : <num>,
         "read timestamp queue entries walked" : <num>,
         "read timestamp queue insert to empty" : <num>,
         "read timestamp queue inserts to head" : <num>,
         "read timestamp queue inserts total" : <num>,
         "read timestamp queue length" : <num>,
         "rollback to stable calls" : <num>,
         "rollback to stable updates aborted" : <num>,
         "rollback to stable updates removed from cache overflow" : <num>,
         "set timestamp calls" : <num>,
         "set timestamp durable calls" : <num>,
         "set timestamp durable updates" : <num>,
         "set timestamp oldest calls" : <num>,
         "set timestamp oldest updates" : <num>,
         "set timestamp stable calls" : <num>,
         "set timestamp stable updates" : <num>,
         "transaction begins" : <num>,
         "transaction checkpoint currently running" : <num>,
         "transaction checkpoint generation" : <num>,
         "transaction checkpoint max time (msecs)" : <num>,
         "transaction checkpoint min time (msecs)" : <num>,
         "transaction checkpoint most recent time (msecs)" : <num>,
         "transaction checkpoint scrub dirty target" : <num>,
         "transaction checkpoint scrub time (msecs)" : <num>,
         "transaction checkpoint total time (msecs)" : <num>,
         "transaction checkpoints" : <num>,
         "transaction checkpoints skipped because database was clean" : <num>,
         "transaction failures due to cache overflow" : <num>,
         "transaction fsync calls for checkpoint after allocating the transaction ID" : <num>,
         "transaction fsync duration for checkpoint after allocating the transaction ID (usecs)" : <num>,
         "transaction range of IDs currently pinned" : <num>,
         "transaction range of IDs currently pinned by a checkpoint" : <num>,
         "transaction range of IDs currently pinned by named snapshots" : <num>,
         "transaction range of timestamps currently pinned" : <num>,
         "transaction range of timestamps pinned by a checkpoint" : <num>,
         "transaction range of timestamps pinned by the oldest active read timestamp" : <num>,
         "transaction range of timestamps pinned by the oldest timestamp" : <num>,
         "transaction read timestamp of the oldest active reader" : <num>,
         "transaction sync calls" : <num>,
         "transactions committed" : <num>,
         "transactions rolled back" : <num>,
         "update conflicts" : <num>
      },
      "concurrentTransactions" : {
         "write" : {
            "out" : <num>,
            "available" : <num>,
            "totalTickets" : <num>
         },
         "read" : {
            "out" : <num>,
            "available" : <num>,
            "totalTickets" : <num>
         }
      },
      "snapshot-window-settings" : {
         "total number of SnapshotTooOld errors" : <num>,
         "max target available snapshots window size in seconds" : <num>,
         "target available snapshots window size in seconds" : <num>,
         "current available snapshots window size in seconds" : <num>,
         "latest majority snapshot timestamp available" : <string>,
         "oldest majority snapshot timestamp available" : <string>
      }
   }

.. note::

   The following is not an exhaustive list.

.. serverstatus:: wiredTiger.uri

   A string. For internal use by MongoDB.

.. serverstatus:: wiredTiger.async

   A document that returns statistics related to the asynchronous
   operations API. This is unused by MongoDB.

.. serverstatus:: wiredTiger.block-manager

   A document that returns statistics on the block manager operations.

.. serverstatus:: wiredTiger.cache

   A document that returns statistics on the cache and page evictions
   from the cache.

   The following describes some of the key
   :serverstatus:`wiredTiger.cache` statistics:

   .. serverstatus:: wiredTiger.cache.maximum bytes configured

      Maximum cache size.

   .. serverstatus:: wiredTiger.cache.bytes currently in the cache

      Size in byte of the data currently in cache. This value should
      not be greater than the ``maximum bytes configured`` value.

   .. serverstatus:: wiredTiger.cache.unmodified pages evicted

      Main statistics for page eviction.

   .. serverstatus:: wiredTiger.cache.tracked dirty bytes in the cache

      Size in bytes of the dirty data in the cache. This value should
      be less than the ``bytes currently in the cache`` value.

   .. serverstatus:: wiredTiger.cache.pages read into cache

      Number of pages read into the cache.
      :serverstatus:`wiredTiger.cache.pages read into cache` with
      the :serverstatus:`wiredTiger.cache.pages written from
      cache` can provide an overview of the I/O activity.

   .. serverstatus:: wiredTiger.cache.pages written from cache

      Number of pages written from the cache.
      :serverstatus:`wiredTiger.cache.pages written from cache`
      with the :serverstatus:`wiredTiger.cache.pages read into
      cache` can provide an overview of the I/O activity.

   .. include:: /includes/extracts/wt-cache-setting.rst

.. serverstatus:: wiredTiger.connection

   A document that returns statistics related to WiredTiger connections.

.. serverstatus:: wiredTiger.cursor

   A document that returns statistics on WiredTiger cursor.

.. serverstatus:: wiredTiger.data-handle

   A document that returns statistics on the data handles and sweeps.

.. serverstatus:: wiredTiger.log

   A document that returns statistics on WiredTiger's write ahead log
   (i.e. the journal).

   .. seealso::

      :ref:`journaling-wiredTiger`

.. serverstatus:: wiredTiger.reconciliation

   A document that returns statistics on the reconciliation process.

.. serverstatus:: wiredTiger.session

   A document that returns the open cursor count and open session count
   for the session.

.. serverstatus:: wiredTiger.thread-yield

   A document that returns statistics on yields during page
   acquisitions.

.. serverstatus:: wiredTiger.transaction

   A document that returns statistics on transaction checkpoints and
   operations.

   .. serverstatus:: wiredTiger.transaction.transaction checkpoint most recent time (msecs)

      Amount of time, in milliseconds, to create the most recent
      checkpoint. An increase in this value under stead write load may
      indicate saturation on the I/O subsystem.

.. serverstatus:: wiredTiger.concurrentTransactions

   A document that returns information on the number of concurrent of
   read and write transactions allowed into the WiredTiger storage
   engine. These settings are MongoDB-specific.

   To change the settings for concurrent
   reads and write transactions, see
   :parameter:`wiredTigerConcurrentReadTransactions` and
   :parameter:`wiredTigerConcurrentWriteTransactions`.

.. _server-status-writebacksqueued:
.. _server-status-write-backs-queued:

writeBacksQueued
~~~~~~~~~~~~~~~~

.. code-block:: javascript

   "writeBacksQueued" : <boolean>,

.. serverstatus:: writeBacksQueued

   A boolean that indicates whether there are operations from a
   :binary:`~bin.mongos` instance queued for retrying. Typically, this
   value is false.  See also :term:`writeBacks`.

.. _memory-status:
.. _server-status-memory:

mem
~~~

.. code-block:: javascript

   "mem" : {
      "bits" : <int>,
      "resident" : <int>,
      "virtual" : <int>,
      "supported" : <boolean>,
      "mapped" : <int>,
      "mappedWithJournal" : <int>
   },


.. serverstatus:: mem

   A document that reports on the system architecture of the
   :binary:`~bin.mongod` and current memory use.

.. serverstatus:: mem.bits

   A number, either ``64`` or ``32``, that indicates whether the
   MongoDB instance is compiled for 64-bit or 32-bit architecture.

.. serverstatus:: mem.resident

   The value of :serverstatus:`mem.resident` is roughly equivalent to
   the amount of RAM, in mebibyte (MiB), currently used by the database
   process. During normal use, this value tends to grow. In dedicated
   database servers, this number tends to approach the total amount of
   system memory.

.. serverstatus:: mem.virtual

   :serverstatus:`mem.virtual` displays the quantity, in mebibyte
   (MiB), of virtual memory used by the :binary:`~bin.mongod` process.

.. serverstatus:: mem.supported

   A boolean that indicates whether the underlying system supports
   extended memory information. If this value is false and the system
   does not support extended memory information, then other
   :serverstatus:`mem` values may not be accessible to the database
   server.


.. serverstatus:: mem.note

   The field :serverstatus:`mem.note` appears if
   :serverstatus:`mem.supported` is false.

   The :serverstatus:`mem.note` field contains the text: ``"not all mem
   info support on this platform"``.

.. _server-status-metrics:

metrics
~~~~~~~

.. code-block:: javascript

   "metrics" : {
      "aggStageCounters" : {
            "<aggregation stage>" : NumberLong(<num>)
      },
      "commands": {
            "<command>": {
               "failed": NumberLong(<num>),
               "total": NumberLong(<num>)
            }
      },
      "cursor" : {
            "moreThanOneBatch" : NumberLong(<num>),
            "timedOut" : NumberLong(<num>),
            "totalOpened" : NumberLong(<num>),
            "lifespan" : {
               "greaterThanOrEqual10Minutes" : NumberLong(<num>),
               "lessThan10Minutes" : NumberLong(<num>),
               "lessThan15Seconds" : NumberLong(<num>),
               "lessThan1Minute" : NumberLong(<num>),
               "lessThan1Second" : NumberLong(<num>),
               "lessThan30Seconds" : NumberLong(<num>),
               "lessThan5Seconds" : NumberLong(<num>)
            },
            "open" : {
               "noTimeout" : NumberLong(<num>),
               "pinned" : NumberLong(<num>),
               "multiTarget" : NumberLong(<num>),
               "singleTarget" : NumberLong(<num>),
               "total" : NumberLong(<num>)
            }
      },
      "document" : {
            "deleted" : NumberLong(<num>),
            "inserted" : NumberLong(<num>),
            "returned" : NumberLong(<num>),
            "updated" : NumberLong(<num>)
      },
      "dotsAndDollarsFields" : {
            "inserts" : Long("0"),
            "updates" : Long("0")
      },
      "getLastError" : {
            "wtime" : {
               "num" : <num>,
               "totalMillis" : <num>
            },
            "wtimeouts" : NumberLong(<num>),
            "default" : {
                "unsatisfiable" : NumberLong(<num>),
                "wtimeouts" : NumberLong(<num>)
            }
      },
      "mongos" : {
         "cursor" : {
            "moreThanOneBatch" : NumberLong(<num>),
            "totalOpened" : NumberLong(<num>)
         }
      },
      "operation" : {
            "scanAndOrder" : NumberLong(<num>),
            "writeConflicts" : NumberLong(<num>)
      },
      "operatorCounters" : {
            "expressions" : {
               "<command>" : Long("0")
            }
      },
      "queryExecutor": {
            "scanned" : NumberLong(<num>),
            "scannedObjects" : NumberLong(<num>),
            "collectionScans" : {
                "nonTailable" : NumbeLong(<num>),
                "total" : NumberLong(<num>)
            }
      },
      "record" : {
            "moves" : NumberLong(<num>)
      },
      "repl" : {
         "executor" : {
            "pool" : {
               "inProgressCount" : <num>
            },
            "queues" : {
               "networkInProgress" : <num>,
               "sleepers" : <num>
            },
            "unsignaledEvents" : <num>,
            "shuttingDown" : <boolean>,
            "networkInterface" : <string>
         },
         "apply" : {
            "attemptsToBecomeSecondary" : NumberLong(<num>),
            "batches" : {
               "num" : <num>,
               "totalMillis" : <num>
            },
            "ops" : NumberLong(<num>)
         },
         "buffer" : {
            "count" : NumberLong(<num>),
            "maxSizeBytes" : NumberLong(<num>),
            "sizeBytes" : NumberLong(<num>)
         },
         "initialSync" : {
            "completed" : NumberLong(<num>),
            "failedAttempts" : NumberLong(<num>),
            "failures" : NumberLong(<num>)
         },
         "network" : {
            "bytes" : NumberLong(<num>),
            "getmores" : {
               "num" : <num>,
               "totalMillis" : <num>
            },
            "notPrimaryLegacyUnacknowledgedWrites" : NumberLong(<num>),
            "notPrimaryUnacknowledgedWrites" : NumberLong(<num>),
            "oplogGetMoresProcessed" : {
               "num" : <num>,
               "totalMillis" : <num>
            },
            "ops" : NumberLong(<num>),
            "readersCreated" : NumberLong(<num>),
            "replSetUpdatePosition" : {
                "num" : NumberLong(<num>)
            }
         },
         "reconfig" : {
            "numAutoReconfigsForRemovalOfNewlyAddedFields" :
               NumberLong(<num>)
         },
         "stepDown" : {
            "userOperationsKilled" : NumberLong(<num>),
            "userOperationsRunning" : NumberLong(<num>)
         },
         "syncSource" : {
            "numSelections" : NumberLong(<num>),
            "numTimesChoseSame" : NumberLong(<num>),
            "numTimesChoseDifferent" : NumberLong(<num>),
            "numTimesCouldNotFind" : NumberLong(<num>)
         }
      },
      "storage" : {
            "freelist" : {
               "search" : {
                  "bucketExhausted" : <num>,
                  "requests" : <num>,
                  "scanned" : <num>
               }
            }
      },
      "ttl" : {
            "deletedDocuments" : NumberLong(<num>),
            "passes" : NumberLong(<num>)
      }
   },

.. serverstatus:: metrics

   A document that returns various statistics that reflect the current
   use and state of a running :binary:`~bin.mongod` instance.

.. serverstatus:: metrics.aggStageCounters

   A document that reports on the use of
   :doc:`aggregation pipeline stages
   </reference/operator/aggregation-pipeline/>`. The fields
   in :serverstatus:`metrics.aggStageCounters` are the names of
   aggregation pipeline stages. For each pipeline stage,
   :dbcommand:`serverStatus` reports the number of times that stage
   has been executed.

   *New in version 4.4 (4.2.6 and 4.0.19).* 

.. serverstatus:: metrics.operatorCounters

   A document with a number that indicates how often
   :ref:`aggregation-expression-operators` ran. For some operators, the
   number reported is a multiple of the times the operator actually
   ran.

   To get metrics for a specific operator, such as the greater-than
   operator (:expression:`$gt`), append the operator to the command:

   .. code-block:: javascript

      db.runCommand( { serverStatus: 1 } ).metrics.operatorCounters.expressions.$gt

   .. versionadded:: 5.0

.. serverstatus:: metrics.commands

   A document that reports on the use of database commands. The fields
   in :serverstatus:`metrics.commands` are the names of :doc:`database
   commands </reference/command>`. For each command, the
   :dbcommand:`serverStatus` reports the total number of executions and
   the number of failed executions.

   Starting in MongoDB 4.0.13 and 4.2.1,
   :serverstatus:`metrics.commands` include
   ``replSetStepDownWithForce`` (i.e. the :dbcommand:`replSetStepDown`
   command with ``force: true``) as well as the overall
   ``replSetStepDown``. In earlier versions, the command
   reported only overall ``replSetStepDown`` metrics.

.. serverstatus:: metrics.commands.<command>.failed

   The number of times ``<command>`` failed on this
   :binary:`~bin.mongod`.

.. serverstatus:: metrics.commands.<command>.total

   The number of times ``<command>`` executed on this
   :binary:`~bin.mongod`.

.. serverstatus:: metrics.commands.update.pipeline

   The number of times an
   :ref:`aggregation pipeline <aggregation-pipeline-operator-reference>`
   was used to update documents on this :binary:`~bin.mongod`. Subtract
   this value from the total number of updates to get the number of
   updates made with :ref:`document <update-operators-top-level>`
   syntax.

   The ``pipeline`` counter is only available for ``update`` and
   ``findAndModify`` operations.

.. serverstatus:: metrics.commands.findAndModify.pipeline

   The number of times :method:`~db.collection.findAndModify()` was
   used in an
   :ref:`aggregation pipeline <aggregation-pipeline-operator-reference>`
   to update documents on this :binary:`~bin.mongod`.

   The ``pipeline`` counter is only available for ``update`` and
   ``findAndModify`` operations.

.. serverstatus:: metrics.commands.update.arrayFilters

   The number of times an :ref:`arrayFilter <findAndModify-arrayFilters>`
   was used to update documents on this :binary:`~bin.mongod`.

   The ``arrayFilters`` counter is only available for ``update`` and
   ``findAndModify`` operations.

.. serverstatus:: metrics.commands.findAndModify.arrayFilters

   The number of times an :ref:`arrayFilter <findAndModify-arrayFilters>`
   was used with :method:`~db.collection.findAndModify()` to update
   documents on this :binary:`~bin.mongod`.

   The ``arrayFilters`` counter is only available for ``update`` and
   ``findAndModify`` operations.

.. serverstatus:: metrics.document

   A document that reflects document access and modification patterns.
   Compare these values to the data in the :serverstatus:`opcounters`
   document, which track total number of operations.

.. serverstatus:: metrics.document.deleted

   The total number of documents deleted.

.. serverstatus:: metrics.document.inserted

   The total number of documents inserted.

.. serverstatus:: metrics.document.returned

   The total number of documents returned by queries.

.. serverstatus:: metrics.document.updated

   The total number of documents updated.

.. serverstatus:: metrics.dotsAndDollarsFields

   A document with a number that indicates how often
   :ref:`insert <write-op-insert>` or :ref:`update <write-op-update>`
   operations ran using a dollar (``$``) prefixed name. The value does
   not report the exact number of operations.  

   When an :term:`upsert` operation creates a new document, it is
   considered to be an ``insert`` rather than an ``update``.

   .. versionadded:: 5.0

.. serverstatus:: metrics.executor

   A document that reports on various statistics for the replication
   executor.

.. serverstatus:: metrics.getLastError

   A document that reports on :dbcommand:`getLastError` use.

.. serverstatus:: metrics.getLastError.wtime

   A document that reports :dbcommand:`getLastError` operation counts
   with a ``w`` argument greater than ``1``.

.. serverstatus:: metrics.getLastError.wtime.num

   The total number of :dbcommand:`getLastError` operations with a
   specified write concern (i.e. ``w``) that wait for one or more
   members of a replica set to acknowledge the write operation (i.e. a
   ``w`` value greater than ``1``.)

.. serverstatus:: metrics.getLastError.wtime.totalMillis

   The total amount of time in milliseconds that the :binary:`~bin.mongod`
   has spent performing :dbcommand:`getLastError` operations with write
   concern (i.e. ``w``) that wait for one or more members of a replica
   set to acknowledge the write operation (i.e. a ``w`` value greater
   than ``1``.)

.. serverstatus:: metrics.getLastError.wtimeouts

   The number of times that :term:`write concern` operations have timed
   out as a result of the ``wtimeout`` threshold to
   :dbcommand:`getLastError`. This number increments for both default
   and non-default write concern specifications.

.. serverstatus:: metrics.getLastError.default

   A document that reports on the use of :dbcommand:`getLastError`
   specific to operations where a default write concern was used
   (meaning, a non-``clientSupplied`` write concern). The possible
   origins of a default write concern are:

   - ``implicitDefault``
   - ``customDefault``
   - ``getLastErrorDefaults``

   Refer to the following table for information on
   each possible write concern origin, or ``provenance``:

   .. include:: /includes/fact-wc-provenance-table.rst

.. serverstatus:: metrics.getLastError.default.unsatisfiable

   Number of times that a non-``clientSupplied`` write concern
   returned the ``UnsatisfiableWriteConcern`` error code.

.. serverstatus:: metrics.getLastError.default.wtimeouts

   Number of times a non-``clientSupplied`` write concern timed out.

.. _server-status-metrics-mongos:

.. serverstatus:: metrics.mongos

   A document that contains metrics about :binary:`~bin.mongos`.

.. serverstatus:: metrics.mongos.cursor

   A document that contains metrics for cursors used by
   :binary:`~bin.mongos`.

.. serverstatus:: metrics.mongos.cursor.moreThanOneBatch

   The total number of cursors that have returned more than one batch
   since :binary:`~bin.mongos` started. Additional batches are retrieved
   using the :dbcommand:`getMore` command.

   .. versionadded:: 5.0

.. serverstatus:: metrics.mongos.cursor.totalOpened

   The total number of cursors that have been opened since
   :binary:`~bin.mongos` started, including cursors currently open.
   Differs from :serverstatus:`metrics.cursor.open.total`, which is the
   number of currently open cursors only.

   .. versionadded:: 5.0

.. serverstatus:: metrics.operation

   A document that holds counters for several types of update and query
   operations that MongoDB handles using special operation types.

.. serverstatus:: metrics.operation.scanAndOrder

   The total number of queries that return sorted numbers that cannot
   perform the sort operation using an index.

.. serverstatus:: metrics.operation.writeConflicts

   The total number of queries that encountered write conflicts.

.. serverstatus:: metrics.queryExecutor

   A document that reports data from the query execution system.

.. serverstatus:: metrics.queryExecutor.scanned

   The total number of index items scanned during queries and
   query-plan evaluation. This counter is the same as
   :data:`~explain.executionStats.totalKeysExamined` in the output of
   :method:`~cursor.explain()`.

.. serverstatus:: metrics.queryExecutor.scannedObjects

   The total number of documents scanned during queries and query-plan
   evaluation. This counter is the same as
   :data:`~explain.executionStats.totalDocsExamined` in the output of
   :method:`~cursor.explain()`.

.. serverstatus:: metrics.queryExecutor.collectionScans

   A document that reports on the number of queries that performed a
   collection scan.

   .. versionadded:: 4.4

.. serverstatus:: metrics.queryExecutor.collectionScans.nonTailable

   The number of queries that performed a collection scan that did not
   use a :doc:`tailable cursor </core/tailable-cursors>`.

   .. versionadded:: 4.4

.. serverstatus:: metrics.queryExecutor.collectionScans.total

   The total number queries that performed a collection scan. The total
   consists of queries that did and did not use a :doc:`tailable cursor
   </core/tailable-cursors>`.

   .. versionadded:: 4.4

.. serverstatus:: metrics.record

   A document that reports on data related to record allocation in the
   on-disk memory files.

.. _server-status-replnetworkqueue:
.. _server-status-repl-network-queue:

.. serverstatus:: metrics.repl

   A document that reports metrics related to the replication process.
   :serverstatus:`metrics.repl` document appears on all
   :binary:`~bin.mongod` instances, even those that aren't members of
   :term:`replica sets <replica set>`.

.. serverstatus:: metrics.repl.apply

   A document that reports on the application of operations from the
   replication :term:`oplog`.

.. serverstatus:: metrics.repl.apply.batchSize

   .. versionadded:: 4.0.6 (Also available in 3.6.11+)

   The total number of oplog operations applied. The
   :serverstatus:`metrics.repl.apply.batchSize` is incremented with the
   number of operations in a batch at the batch boundaries instead of
   being incremented by one after each operation.

   For finer granularity, see :serverstatus:`metrics.repl.apply.ops`.

.. serverstatus:: metrics.repl.apply.batches

   :serverstatus:`metrics.repl.apply.batches` reports on the
   oplog application process on :term:`secondaries <secondary>`
   members of replica sets. See
   :ref:`replica-set-internals-multi-threaded-replication` for more
   information on the oplog application processes.

.. serverstatus:: metrics.repl.apply.batches.num

   The total number of batches applied across all databases.

.. serverstatus:: metrics.repl.apply.batches.totalMillis

   The total amount of time in milliseconds the :binary:`~bin.mongod` has
   spent applying operations from the oplog.

.. serverstatus:: metrics.repl.apply.ops

   The total number of :term:`oplog` operations applied.
   :serverstatus:`metrics.repl.apply.ops` is incremented after each
   operation.

   .. seealso::

      :serverstatus:`metrics.repl.apply.batchSize`

.. serverstatus:: metrics.repl.buffer

   MongoDB buffers oplog operations from the replication sync source
   buffer before applying oplog entries in a
   batch. :serverstatus:`metrics.repl.buffer` provides a way to
   track the oplog buffer. See
   :ref:`replica-set-internals-multi-threaded-replication` for more
   information on the oplog application process.

.. serverstatus:: metrics.repl.buffer.count

   The current number of operations in the oplog buffer.

.. serverstatus:: metrics.repl.buffer.maxSizeBytes

   The maximum size of the buffer. This value is a constant setting in
   the :binary:`~bin.mongod`, and is not configurable.

.. serverstatus:: metrics.repl.buffer.sizeBytes

   The current size of the contents of the oplog buffer.

.. serverstatus:: metrics.repl.network

   :serverstatus:`metrics.repl.network` reports network use by
   the replication process.

.. serverstatus:: metrics.repl.network.bytes

   :serverstatus:`metrics.repl.network.bytes` reports the total
   amount of data read from the replication sync source.

.. serverstatus:: metrics.repl.network.getmores

   :serverstatus:`metrics.repl.network.getmores` reports on the
   ``getmore`` operations, which are requests for additional results
   from the oplog :term:`cursor` as part of the oplog replication
   process.

   .. TODO move the documentation of getmore into some central place

.. serverstatus:: metrics.repl.network.getmores.num

   :serverstatus:`metrics.repl.network.getmores.num` reports the
   total number of ``getmore`` operations, which are operations that
   request an additional set of operations from the replication sync
   source.

.. serverstatus:: metrics.repl.network.getmores.totalMillis

   :serverstatus:`metrics.repl.network.getmores.totalMillis`
   reports the total amount of time required to collect data from
   ``getmore`` operations.

   .. note::

      This number can be quite large, as MongoDB will wait for more
      data even if the ``getmore`` operation does not initial return
      data.

.. serverstatus:: metrics.repl.network.getmores.numEmptyBatches

   The number of empty ``oplog`` batches a secondary receives from its
   sync source. A secondary receives an empty batch if it is fully
   synced with its source and either:

   - The ``getmore`` times out waiting for more data, or

   - The sync source's majority commit point has advanced since the
     last batch sent to this secondary.

   For a primary, if the instance was previously a secondary, the
   number reports on the empty batches received when it was a
   secondary. Otherwise, for a primary, this number is ``0``.

   .. versionadded:: 4.4

.. serverstatus:: metrics.repl.network.notPrimaryLegacyUnacknowledgedWrites

   The number of unacknowledged (``w: 0``) legacy write operations (see
   :ref:`wp-request-opcodes`) that failed because the current
   :binary:`~bin.mongod` is not in :replstate:`PRIMARY` state.

   .. versionadded:: 4.2

.. serverstatus:: metrics.repl.network.notPrimaryUnacknowledgedWrites

   The number of unacknowledged (``w: 0``) write operations that failed
   because the current :binary:`~bin.mongod` is not in
   :replstate:`PRIMARY` state.

   .. versionadded:: 4.2

.. serverstatus:: metrics.repl.network.oplogGetMoresProcessed

   A document that reports the number of :dbcommand:`getMore`
   commands to fetch the :term:`oplog` that a node processed as a sync
   source.

   .. versionadded:: 4.4

.. serverstatus:: metrics.repl.network.oplogGetMoresProcessed.num

   The number of :dbcommand:`getMore` commands to fetch the
   :term:`oplog` that a node processed as a sync source.

   .. versionadded:: 4.4

.. serverstatus:: metrics.repl.network.oplogGetMoresProcessed.totalMillis

   The time, in milliseconds, that a node spent processing the
   :dbcommand:`getMore` commands counted in
   :serverstatus:`metrics.repl.network.oplogGetMoresProcessed.num`. 

   .. versionadded:: 4.4

.. serverstatus:: metrics.repl.network.ops

   The total
   number of operations read from the replication source.

.. serverstatus:: metrics.repl.network.readersCreated

   The total number of oplog query processes created. MongoDB will
   create a new oplog query any time an error occurs in the
   connection, including a timeout, or a network
   operation. Furthermore,
   :serverstatus:`metrics.repl.network.readersCreated` will
   increment every time MongoDB selects a new source for replication.

.. serverstatus:: metrics.repl.network.replSetUpdatePosition

   A document that reports the number of ``replSetUpdatePosition``
   commands a node sent to its sync source.

   .. versionadded:: 4.4

.. serverstatus:: metrics.repl.network.replSetUpdatePosition.num

   The number of ``replSetUpdatePosition`` commands a node sent
   to its sync source. ``replSetUpdatePosition`` commands are internal
   replication commands that communicate replication progress from
   nodes to their sync sources.

   .. versionadded:: 4.4

   .. note::

      Replica set members in the :replstate:`STARTUP2` state do not send
      the ``replSetUpdatePosition`` command to their sync source.

.. serverstatus:: metrics.repl.reconfig

   A document containing the number of times that member ``newlyAdded``
   fields were automatically removed by the primary. When a member is
   first added to the replica set, the member's ``newlyAdded`` field is
   set to ``true``.

   .. versionadded:: 5.0

.. serverstatus:: metrics.repl.reconfig.numAutoReconfigsForRemovalOfNewlyAddedFields

   The number of times that ``newlyAdded`` member fields were
   automatically removed by the primary. When a member is first added to
   the replica set, the member's ``newlyAdded`` field is set to
   ``true``. After the primary receives the member's heartbeat response
   indicating the member state is :replstate:`SECONDARY`,
   :replstate:`RECOVERING`, or :replstate:`ROLLBACK`, the primary
   automatically removes the member's ``newlyAdded`` field. The
   ``newlyAdded`` fields are stored in the :data:`local.system.replset`
   collection.

   .. versionadded:: 5.0

.. serverstatus:: metrics.repl.stepDown

   Information on user operations that were running when the
   :binary:`~bin.mongod` stepped down.

   .. versionadded:: 4.2

.. serverstatus:: metrics.repl.stepDown.userOperationsKilled

   The number of user operations killed when the :binary:`~bin.mongod`
   stepped down.

   .. versionadded:: 4.2

.. serverstatus:: metrics.repl.stepDown.userOperationsRunning

   The number of user operations that remained running when the
   :binary:`~bin.mongod` stepped down.

   .. versionadded:: 4.2

.. serverstatus:: metrics.repl.syncSource

   Information on a replica set node's
   :doc:`sync source selection </core/replica-set-sync/>` process.

   .. versionadded:: 4.4

.. serverstatus:: metrics.repl.syncSource.numSelections

   Number of times a node attempted to choose a node to sync from among
   the available sync source options. A node attempts to choose a node
   to sync from if, for example, the sync source is re-evaluated or the
   node receives an error from its current sync source.

   .. versionadded:: 4.4

.. serverstatus:: metrics.repl.syncSource.numTimesChoseSame

   Number of times a node kept its original sync source after
   re-evaluating if its current sync source was optimal.

   .. versionadded:: 4.4

.. serverstatus:: metrics.repl.syncSource.numTimesChoseDifferent

   Number of times a node chose a new sync source after re-evaluating if
   its current sync source was optimal.

   .. versionadded:: 4.4

.. serverstatus:: metrics.repl.syncSource.numTimesCouldNotFind

   Number of times a node could not find an available sync source when
   attempting to choose a node to sync from.

   .. versionadded:: 4.4

.. serverstatus:: metrics.storage.freelist.search.bucketExhausted

   The number of times that :binary:`~bin.mongod` has examined the free
   list without finding a large record allocation.

.. serverstatus:: metrics.storage.freelist.search.requests

   The number of times :binary:`~bin.mongod` has searched for available
   record allocations.

.. serverstatus:: metrics.storage.freelist.search.scanned

   The number of available record allocations :binary:`~bin.mongod` has
   searched.

.. serverstatus:: metrics.ttl

   A document that reports on the operation of the resource use of the
   :doc:`ttl index </tutorial/expire-data/>` process.

.. serverstatus:: metrics.ttl.deletedDocuments

   The total number of documents deleted from collections with a
   :doc:`ttl index </tutorial/expire-data/>`.

.. serverstatus:: metrics.ttl.passes

   The number of times the background process removes documents from
   collections with a :doc:`ttl index </tutorial/expire-data/>`.

.. _server-status-metrics-cursor:

.. serverstatus:: metrics.cursor

   A document that contains data regarding cursor state and use.

.. serverstatus:: metrics.cursor.moreThanOneBatch

   The total number of cursors that have returned more than one batch
   since the server process started. Additional batches are retrieved
   using the :dbcommand:`getMore` command.

   .. versionadded:: 5.0

.. serverstatus:: metrics.cursor.timedOut

   The total number of cursors that have timed out since the server
   process started. If this number is large or growing at a regular
   rate, this may indicate an application error.

.. serverstatus:: metrics.cursor.totalOpened

   The total number of cursors that have been opened since the server
   process started, including cursors currently open. Differs from
   :serverstatus:`metrics.cursor.open.total`, which is the number of
   currently open cursors only.

   .. versionadded:: 5.0

.. _server-status-metrics-cursor-lifespan:

.. serverstatus:: metrics.cursor.lifespan

   A document that reports the number of cursors that have lifespans
   within specified time periods. The cursor lifespan is the time period
   from when the cursor is created to when the cursor is killed using
   the :dbcommand:`killCursors` command or the cursor has no remaining
   objects in the :ref:`batch <cursor-batches>`.

   The lifespan time periods are:

   - < 1 second

   - >= 1 second to < 5 seconds

   - >= 5 seconds to < 15 seconds

   - >= 15 seconds to < 30 seconds

   - >= 30 seconds to < 1 minute

   - >= 1 minute to < 10 minutes

   - >= 10 minutes

   .. versionadded:: 5.0

.. serverstatus:: metrics.cursor.lifespan.greaterThanOrEqual10Minutes

   The number of cursors with a lifespan >= 10 minutes.

   .. versionadded:: 5.0

.. serverstatus:: metrics.cursor.lifespan.lessThan10Minutes

   The number of cursors with a lifespan >= 1 minute to < 10 minutes.

   .. versionadded:: 5.0

.. serverstatus:: metrics.cursor.lifespan.lessThan15Seconds

   The number of cursors with a lifespan >= 5 seconds to < 15 seconds.

   .. versionadded:: 5.0

.. serverstatus:: metrics.cursor.lifespan.lessThan1Minute

   The number of cursors with a lifespan >= 30 seconds to < 1 minute.

   .. versionadded:: 5.0

.. serverstatus:: metrics.cursor.lifespan.lessThan1Second

   The number of cursors with a lifespan < 1 second.

   .. versionadded:: 5.0

.. serverstatus:: metrics.cursor.lifespan.lessThan30Seconds

   The number of cursors with a lifespan >= 15 seconds to < 30 seconds.

   .. versionadded:: 5.0

.. serverstatus:: metrics.cursor.lifespan.lessThan5Seconds

   The number of cursors with a lifespan >= 1 second to < 5 seconds.

   .. versionadded:: 5.0

.. serverstatus:: metrics.cursor.open

   A document that contains data regarding open cursors.

.. serverstatus:: metrics.cursor.open.noTimeout

   The number of open cursors with the option
   :data:`DBQuery.Option.noTimeout` set to prevent timeout after a
   period of inactivity.

.. serverstatus:: metrics.cursor.open.pinned

   The number of "pinned" open cursors.

.. serverstatus:: metrics.cursor.open.total

   The number of cursors that MongoDB is maintaining for clients.
   Because MongoDB exhausts unused cursors, typically this value small
   or zero. However, if there is a queue, or stale tailable cursors, or
   a large number of operations this value may increase.

.. serverstatus:: metrics.cursor.open.singleTarget

   The total number of cursors that only target a *single* shard. Only
   :binary:`~bin.mongos` instances report
   :serverstatus:`metrics.cursor.open.singleTarget` values.

.. serverstatus:: metrics.cursor.open.multiTarget

   The total number of cursors that only target *more than one* shard.
   Only :binary:`~bin.mongos` instances report
   :serverstatus:`metrics.cursor.open.multiTarget` values.

watchdog
~~~~~~~~

.. versionadded:: 3.6

.. code-block:: javascript

   "watchdog" : {
      "checkGeneration" : NumberLong(<num>),
      "monitorGeneration" : NumberLong(<num>),
      "monitorPeriod" : <num>
   }

.. note::

   The ``watchdog`` section is only present if the :ref:`Storage Node Watchdog
   <storage-node-watchdog>` is enabled.

.. serverstatus:: watchdog

   A document reporting the status of the
   :ref:`Storage Node Watchdog <storage-node-watchdog>`.

.. serverstatus:: watchdog.checkGeneration

   The number of times the directories have been checked since startup.
   Directories are checked multiple times every ``monitoringPeriod``.

.. serverstatus:: watchdog.monitorGeneration

   The number of times the status of all filesystems used by
   :binary:`~bin.mongod` has been examined. This is incremented once
   every ``monitoringPeriod``.

.. serverstatus:: watchdog.monitorPeriod

   The value set by :parameter:`watchdogPeriodSeconds`. This is the
   period between status checks.