serverStatus (database command数据库命令)

Initialization初始化

The statistics reported by serverStatus are reset when the mongod server is restarted.当mongod服务器重新启动时，serverStatus报告的统计信息将被重置。

This command will always return a value, even on a fresh database. The related command db.serverStatus() does not always return a value unless a counter has started to increment for a particular metric.即使在新数据库上，此命令也将始终返回一个值。相关的命令db.serverStatus()并不总是返回值，除非计数器已经开始为特定指标递增。

After you run an update query, db.serverStatus() and db.runCommand({ serverStatus: 1}) both return the same values.运行更新查询后，db.serverStatus()和db.runCommand({ serverStatus: 1})都返回相同的值。

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

Include 包含mirroredReads

By default, the mirroredReads information is not included in the output. To return mirroredReads information, you must explicitly specify the inclusion:默认情况下，输出中不包括mirroredReads信息。要返回mirroredReads信息，您必须明确指定包含：

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

asserts

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

asserts

A document that reports on the number of assertions raised since the MongoDB process started. Assertions are internal checks for errors that occur while the database is operating and can help diagnose issues with the MongoDB server. Non-zero asserts values indicate assertion errors, which are uncommon and not an immediate cause for concern. Errors that generate asserts can be recorded in the log file or returned directly to a client application for more information.一份报告自MongoDB进程启动以来提出的断言数量的文档。断言是对数据库运行时发生的错误的内部检查，可以帮助诊断MongoDB服务器的问题。非零断言值表示断言错误，这种错误并不常见，也不是立即引起关注的原因。生成断言的错误可以记录在日志文件中，也可以直接返回给客户端应用程序以获取更多信息。

asserts.regular

The number of regular assertions raised since the MongoDB process started. Examine the MongoDB log for more information.自MongoDB进程启动以来提出的常规断言数量。检查MongoDB日志以获取更多信息。

asserts.warning

This field always returns zero 0.此字段始终返回0。

asserts.msg

The number of message assertions raised since the MongoDB process started. Examine the log file for more information about these messages.自MongoDB进程启动以来引发的消息断言数。有关这些消息的详细信息，请检查日志文件。

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. 自上次启动MongoDB进程以来发生的“用户断言”数量。这些是用户可能产生的错误，例如磁盘空间不足或键重复。您可以通过修复应用程序或部署的问题来防止这些断言。Server logs may have limited information about "user asserts." To learn more information about the source of "user asserts," check the application logs for application errors.服务器日志中有关“用户断言”的信息可能有限。要了解有关“用户声明”来源的更多信息，请检查应用程序日志中的应用程序错误。

asserts.rollovers

The number of times that the assert counters have rolled over since the last time the MongoDB process started. The counters will roll over to zero after 2 ³⁰ assertions. 自上次启动MongoDB进程以来，断言计数器翻转的次数。在2³⁰次断言后，计数器将翻转为零。Use this value to provide context to the other values in the asserts data structure.使用此值为asserts数据结构中的其他值提供上下文。

bucketCatalog

bucketCatalog: {
    numBuckets: <num>,
    numOpenBuckets: <num>,
    numIdleBuckets: <num>,
    memoryUsage: <num>,
    numBucketInserts: <num>,
    numBucketUpdates: <num>,
    numBucketsOpenedDueToMetadata: <num>,
    numBucketsClosedDueToCount: <num>,
    numBucketsClosedDueToSchemaChange: <num>,
    numBucketsClosedDueToSize: <num>,
    numBucketsClosedDueToTimeForward: <num>,
    numBucketsClosedDueToTimeBackward: <num>,
    numBucketsClosedDueToMemoryThreshold: <num>,
    numCommits: <num>,
    numMeasurementsGroupCommitted: <num>,
    numWaits: <num>,
    numMeasurementsCommitted: <num>,
    avgNumMeasurementsPerCommit: <num>,
    numBucketsClosedDueToReopening: <num>,
    numBucketsArchivedDueToMemoryThreshold: <num>,
    numBucketsArchivedDueToTimeBackward: <num>,
    numBucketsReopened: <num>,
    numBucketsKeptOpenDueToLargeMeasurements: <num>,
    numBucketsClosedDueToCachePressure: <num>,
    numBucketsFrozen: <num>,
    numCompressedBucketsConvertedToUnsorted: <num>,
    numBucketsFetched: <num>,
    numBucketsQueried: <num>,
    numBucketFetchesFailed: <num>,
    numBucketQueriesFailed: <num>,
    numBucketReopeningsFailed: <num>,
    numDuplicateBucketsReopened: <num>,
    stateManagement: {
       bucketsManaged: <num>,
       currentEra: <num>,
       erasWithRemainingBuckets: <num>,
       trackedClearOperations: <num>
    }
 }

A document that reports metrics related to the internal storage of time series collections.报告与时间序列集合的内部存储相关的指标的文档。

The bucketCatalog returns the following metrics:bucketCatalog返回以下指标：

You can also use the $collStats aggregation pipeline stage to find time series metrics. 您还可以使用$collStats聚合管道阶段来查找时间序列指标。To learn more, see storageStats Output on Time Series Collections.要了解更多信息，请参阅时间序列集合上的storageStats输出。

catalogStats

catalogStats: {
   collections: <num>,
   capped: <num>,
   views: <num>,
   timeseries: <num>,
   internalCollections: <num>,
   internalViews: <num>,
   systemProfile: <num>
}

catalogStats

A document that reports statistics on collection usage via collection counts.通过集合计数报告集合使用统计数据的文档。

catalogStats.collections

The total number of user collections (not including system collections).用户集合的总数（不包括系统集合）。

catalogStats.capped

The total number of capped user collections.上限用户集合的总数。

catalogStats.views

The total number of user views.用户视图的总数。

catalogStats.timeseries

The total number of time series collections.时间序列集合的总数。

catalogStats.internalCollections

The total number of system collections (collections on the config, admin, or local databases).系统集合的总数（config、admin或local数据库上的集合）。

catalogStats.internalViews

The total number of views of system collections (collections on the config, admin, or local databases).系统集合（config、admin或local数据库上的集合）的视图总数。

catalogStats.systemProfile

The total number of profile collections on all databases.所有数据库上的profile集合总数。

changeStreamPreImages

changeStreamPreImages : {
   purgingJob : {
      totalPass : <num>,
      docsDeleted : <num>,
      bytesDeleted : <num>,
      scannedCollections : <num>,
      scannedInternalCollections : <num>,
      maxTimestampEligibleForTruncate : <timestamp>,
      maxStartWallTimeMillis : <num>,
      timeElapsedMillis : <num>,
   },
   expireAfterSeconds : <num>
}

A document that reports metrics related to change stream pre-images.报告与更改流前映像相关的指标的文档。

changeStreamPreImages.purgingJob

New in version 7.1.在版本7.1中新增。

A document that reports metrics related to the purging jobs for change stream pre-images. Purging jobs are background processes that the system uses to remove pre-images asynchronously.报告与更改流预映像的清除作业相关的指标的文档。清除作业是系统用于异步删除预映像的后台进程。

The changeStreamPreImages.purgingJob field returns the following metrics:changeStreamPreImagespurgeingJob字段返回以下指标：

Metric指标	Description描述
totalPass	Total number of deletion passes completed by the purging job.清除作业完成的删除过程总数。
docsDeleted	Cumulative number of pre-image documents deleted by the purging job.清除作业删除的预映像文档的累积数量。
bytesDeleted	Cumulative size in bytes of all deleted documents from all pre-image collections by the purging job.清除作业从所有预映像集合中删除的所有文档的累积大小（以字节为单位）。
scannedCollections	Cumulative number of pre-image collections scanned by the purging job.清除作业扫描的预图像集合的累积数量。 In single-tenant environments, this number is the same as totalPass since each tenant has one pre-image collection.
scannedInternalCollections	Cumulative number of internal pre-image collections scanned by the purging job. Internal collections are the collections within the pre-image collections stored in config.system.preimages.
maxTimestampEligibleForTruncate	Most recent timestamp up to which old pre-images can be truncated to reduce storage space. Pre-images older than maxTimestampEligibleForTruncate can be truncated. New in version 8.1.在版本8.1中新增。
maxStartWallTimeMillis	Maximum wall time in milliseconds from the first document of each pre-image collection.从每个预图像集合的第一个文档开始的最长墙时间（毫秒）。
timeElapsedMillis	Cumulative time in milliseconds of all deletion passes by the purging job.清除作业经过的所有删除的累积时间（毫秒）。

changeStreamPreImages.expireAfterSeconds

New in version 7.1.在版本7.1中新增。

Amount of time in seconds that MongoDB retains pre-images. MongoDB保留预映像的时间量（秒）。If expireAfterSeconds is not defined, this metric does not appear in the serverStatus output.如果未定义expireAfterSeconds，则此指标不会出现在serverStatus输出中。

connections

connections : {
   current : <num>,
   available : <num>,
   totalCreated : <num>,
   rejected : <num>,  // Added in MongoDB 6.3
   active : <num>,
   threaded : <num>,
   exhaustIsMaster : <num>,
   exhaustHello : <num>,
   awaitingTopologyChanges : <num>,
   loadBalanced : <num>,
   queuedForEstablishment : <num>, // Added in MongoDB 8.2 *(also available in 8.1.1, 8.0.12, and 7.0.23)*
   establishmentRateLimit : { // Added in MongoDB 8.2 *(also available in 8.1.1, 8.0.12, and 7.0.23)*
      rejected: <num>,
      exempted: <num>,
      interruptedDueToClientDisconnect: <num>
   }
}

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.报告连接状态的文档。使用这些值来评估服务器的当前负载和容量要求。

connections.current

The number of incoming connections from clients to the database server. This number includes the current shell session. Consider the value of connections.available to add more context to this datum.从客户端到数据库服务器的传入连接数。此数字包括当前shell会话。考虑connections.available的值，为该数据添加更多上下文。

The value will include all incoming connections including any shell connections or connections from other servers, such as replica set members or mongos instances.该值将包括所有传入连接，包括任何shell连接或来自其他服务器的连接，如副本集成员或mongos实例。

connections.available

The number of unused incoming connections available. Consider this value in combination with the value of connections.current to understand the connection load on the database, and the UNIX ulimit Settings for Self-Managed Deployments document for more information about system thresholds on available connections.可用的未使用的传入连接数。将此值与connections.current的值结合考虑，以了解数据库上的连接负载，有关可用连接的系统阈值的更多信息，请参阅自我管理的部署的UNIX ulimit设置文档。

connections.totalCreated

Count of all incoming connections created to the server. This number includes connections that have since closed.创建到服务器的所有传入连接的计数。此数字包括此后关闭的连接。

connections.rejected

New in version 6.3.在版本6.3中新增。

The number of incoming connections the server rejected because the server doesn't have the capacity to accept additional connections or the net.maxIncomingConnections setting is reached.

connections.queuedForEstablishment

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

The number of incoming connections currently queued and waiting for establishment. This metric is relevant when connection establishment rate limiting is enabled using the ingressConnectionEstablishmentRateLimiterEnabled parameter.

connections.establishmentRateLimit

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

A document that contains metrics related to the ingress connection establishment rate limiter. These metrics provide insights into how the rate limiter handles connection requests when ingressConnectionEstablishmentRateLimiterEnabled is set to true. For more information on rate limiting, see Configure the Ingress Connection Establishment Rate Limiter.

connections.establishmentRateLimit.rejected

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

The number of incoming connections the server rejects due to connection establishment rate limiting. This metric shows how many connection attempts the server rejected rejected because they exceeded the rate limits set by the ingress connection establishment rate limiter parameters.

connections.establishmentRateLimit.exempted

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

The number of incoming connections that bypassed the rate limiter because they originated from IP addresses or CIDR ranges specified in the ingressConnectionEstablishmentRateLimiterBypass parameter. The server does note rate limit these connections and establishes them immediately, regardless of current queue size or rate limits.

connections.establishmentRateLimit.interruptedDueToClientDisconnect

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

The number of incoming connections that were interrupted while waiting in the establishment queue because the client disconnected before establishment could complete. 在建立队列中等待时因客户端在建立完成之前断开连接而中断的传入连接数。A high value for this metric sometimes indicates that the client's connectTimeoutMS setting is too short relative to the queue wait time, which is affected by ingressConnectionEstablishmentMaxQueueDepth and ingressConnectionEstablishmentRatePerSec. If this value is high, consider adjusting these parameters using the following formula: maxQueueDepth < (establishmentRatePerSec / 1000) * (connectTimeoutMs - avgEstablishmentTimeMs).

connections.active

The number of active client connections to the server. Active client connections refers to client connections that currently have operations in progress.与服务器的活动客户端连接数。活动客户端连接是指当前正在进行操作的客户端连接。

connections.threaded

The number of incoming connections from clients that are assigned to threads that service client requests.分配给为客户端请求提供服务的线程的来自客户端的传入连接数。

New in version 5.0.在版本5.0中新增。

connections.exhaustIsMaster

The number of connections whose last request was an isMaster request with exhaustAllowed.

Note

If you are running MongoDB 5.0 or later, do not use the isMaster command. Instead, use hello.如果您运行的是MongoDB 5.0或更高版本，请不要使用isMaster命令。相反，使用hello。

connections.exhaustHello

The number of connections whose last request was a hello request with exhaustAllowed.最后一个请求是带有exhaustAllowed的hello请求的连接数。

New in version 5.0.在版本5.0中新增。

connections.awaitingTopologyChanges

The number of clients currently waiting in a hello or isMaster request for a topology change.当前在hello或isMaster请求中等待拓扑更改的客户端数量。

Note

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

connections.loadBalanced

New in version 5.3.在版本5.3中新增。

The current number of incoming connections received through the load balancer.通过负载平衡器接收到的当前传入连接数。

defaultRWConcern

The defaultRWConcern section provides information on the local copy of the global default read or write concern settings. defaultRWConcern部分提供有关全局默认读或写入关注设置的本地副本的信息。The data may be stale or out of date. See getDefaultRWConcern for more information.数据可能已经过时。有关更多信息，请参阅getDefaultRWConcern。

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

defaultRWConcern

The last known global default read or write concern settings.最后一个已知的全局默认读或写入关注设置。

defaultRWConcern.defaultReadConcern

The last known global default read concern setting.

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

defaultRWConcern.defaultReadConcern.level

The last known global default read concern level setting.

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

defaultRWConcern.defaultWriteConcern

The last known global default write concern setting.最后一个已知的全局默认写入关注设置。

If serverStatus does not return this field, the global default write concern has either not been set or has not yet propagated to the instance.如果serverStatus未返回此字段，则表示全局默认写入关注尚未设置或尚未传播到实例。

defaultRWConcern.defaultWriteConcern.w

The last known global default w setting.最后一个已知的全局默认w设置。

If 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.如果serverStatus未返回此字段，则表示此设置的全局默认值尚未设置或尚未传播到实例。

defaultRWConcern.defaultWriteConcern.wtimeout

The last known global default wtimeout setting.最后一个已知的全局默认wtimeout设置。

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

defaultRWConcern.defaultWriteConcernSource

The source of the default write concern. By default, the value is "implicit". Once you set the default write concern with setDefaultRWConcern, the value becomes "global".

New in version 5.0.在版本5.0中新增。

defaultRWConcern.defaultReadConcernSource

The source of the default read concern. By default, the value is "implicit". Once you set the default read concern with setDefaultRWConcern, the value becomes "global".

New in version 5.0.在版本5.0中新增。

defaultRWConcern.updateOpTime

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

defaultRWConcern.updateWallClockTime

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

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 defaultRWConcern, the instance has never had knowledge of a global default read or write concern setting.

electionMetrics

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

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

electionMetrics.stepUpCmd

Metrics on elections that were called by the mongod instance as part of an election handoff when the primary stepped down.

The stepUpCmd includes both the number of elections called and the number of elections that succeeded.

electionMetrics.priorityTakeover

Metrics on elections that were called by the mongod instance because its priority is higher than the primary's.

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

electionMetrics.catchUpTakeover

Metrics on elections called by the mongod instance because it is more current than the primary.

The catchUpTakeover includes both the number of elections called and the number of elections that succeeded.

Tip

settings.catchUpTakeoverDelayMillis

electionMetrics.electionTimeout

Metrics on elections called by the mongod instance because it has not been able to reach the primary within settings.electionTimeoutMillis.

The electionTimeout includes both the number of elections called and the number of elections that succeeded.

Tip

settings.electionTimeoutMillis

electionMetrics.freezeTimeout

Metrics on elections called by the mongod instance after its freeze period (during which the member cannot seek an election) has expired.

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

electionMetrics.numStepDownsCausedByHigherTerm

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

electionMetrics.numCatchUps

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

electionMetrics.numCatchUpsSucceeded

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

electionMetrics.numCatchUpsAlreadyCaughtUp

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

electionMetrics.numCatchUpsSkipped

Number of times the mongod instance as the newly-elected primary skipped the catchup process.

electionMetrics.numCatchUpsTimedOut

Number of times the mongod instance as the newly-elected primary concluded its catchup process because of the settings.catchUpTimeoutMillis limit.

electionMetrics.numCatchUpsFailedWithError

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

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

electionMetrics.numCatchUpsFailedWithReplSetAbortPrimaryCatchUpCmd

Number of times the newly-elected primary's catchup process concluded because the mongod received the replSetAbortPrimaryCatchUp command.

electionMetrics.averageCatchUpOps

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

extra_info

extra_info : {
   note : 'fields vary by platform',
   page_faults : <num>
},

extra_info

A document that provides additional information about the underlying system.

extra_info.note

A string with the text 'fields vary by platform'

extra_info.page_faults

The total number of page faults. The 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.

flowControl

flowControl : {
   enabled : <boolean>,
   targetRateLimit : <int>,
   timeAcquiringMicros : Long("<num>"),
   locksPerKiloOp : <double>,
   sustainerRate : <int>,
   isLagged : <boolean>,
   isLaggedCount : <int>,
   isLaggedTimeMicros : Long("<num>")
},

flowControl

A document that returns statistics on the Flow Control. With flow control enabled, as the majority commit point lag grows close to the flowControlTargetLagSeconds, writes on the primary must obtain tickets before taking locks. As such, the metrics returned are meaningful when run on the primary.

flowControl.enabled

A boolean that indicates whether Flow Control is enabled (true) or disabled (false).

See also enableFlowControl.

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.

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.

flowControl.locksPerKiloOp

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.

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.

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

Replication lag can occur without engaging flow control. An unresponsive secondary might lag without the replica set receiving sufficient load to engage flow control, leaving the flowControl.isLagged value at false.

For additional information, see Flow Control.

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

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

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

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

globalLock

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

globalLock

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

Generally, the locks document provides more detailed data on lock uses.

globalLock.totalTime

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

globalLock.currentQueue

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

globalLock.currentQueue.total

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

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

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.

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.

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 globalLock.currentQueue data.

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.

globalLock.activeClients.readers

The number of the active client connections performing read operations.

globalLock.activeClients.writers

The number of active client connections performing write operations.

indexBuilds

indexBuilds : {
   total : <num>,
   killedDueToInsufficientDiskSpace : <num>,
   failedDueToDataCorruption : <num>
},

indexBuilds

Provides metrics on index builds after the server last started.

indexBuilds.total

Total number of index builds.

indexBuilds.killedDueToInsufficientDiskSpace

Total number of index builds that were ended because of insufficient disk space. Starting in MongoDB 7.1, you can set the minimum amount of disk space required for building indexes using the indexBuildMinAvailableDiskSpaceMB parameter.

New in version 7.1.在版本7.1中新增。

indexBuilds.failedDueToDataCorruption

Total number of index builds that failed because of data corruption.

New in version 7.1.在版本7.1中新增。

indexBulkBuilder

indexBulkBuilder: {
   count: <long>,
   resumed: <long>,
   filesOpenedForExternalSort: <long>,
   filesClosedForExternalSort: <long>,
   spilledRanges: <long>,
   bytesSpilledUncompressed: <long>,
   bytesSpilled: <long>,
   numSorted: <long>,
   bytesSorted: <long>,
   memUsage: <long>
}

indexBulkBuilder

Provides metrics for index bulk builder operations. Use these metrics to diagnose index build issues with createIndexes, collection cloning during initial sync, index builds that resume after startup, and statistics on disk usage by the external sorter.

indexBuildBuilder.bytesSpilled

New in version 6.0.4.在版本6.0.4中新增。

The number of bytes written to disk by the external sorter.

indexBuilder.bytesSpilledUncompressed

New in version 6.0.4.在版本6.0.4中新增。

The number of bytes to be written to disk by the external sorter before compression.

indexBulkBuilder.count

The number of instances of the bulk builder created.

indexBulkBuilder.filesClosedForExternalSort

The number of times the external sorter closed a file handle to spill data to disk. Combine this value with filesOpenedForExternalSort to determine the number of open file handles in use by the external sorter.

indexBulkBuilder.filesOpenedForExternalSort

The number of times the external sorter opened a file handle to spill data to disk. Combine this value with filesClosedForExternalSort to determine the number of open file handles in use by the external sorter.

indexBulkBuilder.resumed

The number of times the bulk builder was created for a resumable index build.

indexBulkBuilder.spilledRanges

New in version 6.0.4.在版本6.0.4中新增。

The number of times the external sorter spilled to disk.

indexBulkBuilder.numSorted

New in version 6.3.在版本6.3中新增。

The total number of sorted documents.

indexBulkBuilder.bytesSorted

New in version 6.3.在版本6.3中新增。

The total number of bytes for sorted documents. For example, if a total of 10 documents were sorted and each document is 20 bytes, the total number of bytes sorted is 200.

indexBulkBuilder.memUsage

New in version 6.3.在版本6.3中新增。

The current bytes of memory allocated for building indexes.

indexStats

indexStats: {
   count: Long("<num>"),
   features: {
      '2d': { count: Long("<num>"), accesses: Long("<num>") },
      '2dsphere': { count: Long("<num>"), accesses: Long("<num>") },
      '2dsphere_bucket': { count: Long("<num>"), accesses: Long("<num>") },
      collation: { count: Long("<num>"), accesses: Long("<num>") },
      compound: { count: Long("<num>"), accesses: Long("<num>") },
      hashed: { count: Long("<num>"), accesses: Long("<num>") },
      id: { count: Long("<num>"), accesses: Long("<num>") },
      normal: { count: Long("<num>"), accesses: Long("<num>") },
      partial: { count: Long("<num>"), accesses: Long("<num>") },
      prepareUnique: { count: Long("<num>"), accesses: Long("<num>") }, // Added in 8.1 (and 8.0.4 and 7.0.14)
      single: { count: Long("<num>"), accesses: Long("<num>") },
      sparse: { count: Long("<num>"), accesses: Long("<num>") },
      text: { count: Long("<num>"), accesses: Long("<num>") },
      ttl: { count: Long("<num>"), accesses: Long("<num>") },
      unique: { count: Long("<num>"), accesses: Long("<num>") },
      wildcard: { count: Long("<num>"), accesses: Long("<num>") }
   }
}

indexStats

A document that reports statistics on all indexes on databases and collections in non-system namespaces only. indexStats does not report statistics on indexes in the admin, local, and config databases.

New in version 6.0.在版本6.0中新增。

indexStats.count

The total number of indexes.

New in version 6.0.在版本6.0中新增。

indexStats.features

A document that provides counters for each index type and the number of accesses on each index. Each index type under indexStats.features has a count field that counts the total number of indexes for that type, and an accesses field that counts the number of accesses on that index.

New in version 6.0.在版本6.0中新增。

Instance Information

host : <string>,
advisoryHostFQDNs : <array>,
version : <string>,
process : <'mongod'|'mongos'>,
service : <'router'|'shard'>,
pid : Long("<num>"),
uptime : <num>,
uptimeMillis : Long("<num>"),
uptimeEstimate : Long("<num>"),
localTime : ISODate("<Date>"),

host

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

advisoryHostFQDNs

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

version

The MongoDB version of the current MongoDB process.

process

The current MongoDB process. Possible values are: mongos or mongod.

service

The role of the current MongoDB process. Possible values are router or shard.

New in version 8.0.在版本8.0中新增。

pid

The process ID number.

uptime

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

uptimeMillis

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

uptimeEstimate

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

localTime

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

locks

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

locks

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

The possible lock <types> are:

Lock Type	Description描述
ParallelBatchWriterMode	Represents a lock for parallel batch writer mode. In earlier versions, PBWM information was reported as part of the Global lock information.
ReplicationStateTransition	Represents lock taken for replica set member state transitions.
Global	Represents global lock.
Database	Represents database lock.
Collection	Represents collection lock.
Mutex	Represents mutex.
Metadata	Represents metadata lock.
DDLDatabase	Represents a DDL database lock. New in version 7.1.在版本7.1中新增。
DDLCollection	Represents a DDL collection lock. New in version 7.1.在版本7.1中新增。
oplog	Represents lock on the oplog.

The possible <modes> are:

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

All values are of the Long() type.

locks.<type>.acquireCount

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

locks.<type>.acquireWaitCount

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

locks.<type>.timeAcquiringMicros

Cumulative wait time in microseconds for the lock acquisitions.

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

locks.<type>.deadlockCount

Number of times the lock acquisitions encountered deadlocks.

logicalSessionRecordCache

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>
},

logicalSessionRecordCache

Provides metrics around the caching of server sessions.

logicalSessionRecordCache.activeSessionsCount

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

Tip

• $listLocalSessions
• logicalSessionRefreshMillis

logicalSessionRecordCache.sessionsCollectionJobCount

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

Tip

logicalSessionRefreshMillis

logicalSessionRecordCache.lastSessionsCollectionJobDurationMillis

The length in milliseconds of the last refresh.

logicalSessionRecordCache.lastSessionsCollectionJobTimestamp

The time at which the last refresh occurred.

logicalSessionRecordCache.lastSessionsCollectionJobEntriesRefreshed

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

logicalSessionRecordCache.lastSessionsCollectionJobEntriesEnded

The number of sessions that ended during the last refresh.

logicalSessionRecordCache.lastSessionsCollectionJobCursorsClosed

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

logicalSessionRecordCache.transactionReaperJobCount

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

logicalSessionRecordCache.lastTransactionReaperJobDurationMillis

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

logicalSessionRecordCache.lastTransactionReaperJobTimestamp

The time of the last transaction record cleanup.

logicalSessionRecordCache.lastTransactionReaperJobEntriesCleanedUp

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

logicalSessionRecordCache.sessionCatalogSize

• For a 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 localLogicalSessionTimeoutMinutes.

• For a mongos instance,

  The number of the in-memory cache of its sessions that have had transactions within the most recent localLogicalSessionTimeoutMinutes interval.

mem

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

mem

A document that reports on the system architecture of the mongod and current memory use.

mem.bits

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

mem.resident

The value of 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.

mem.virtual

mem.virtual displays the quantity, in mebibyte (MiB), of virtual memory used by the mongod process.

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 mem values may not be accessible to the database server.

mem.note

The field mem.note appears if mem.supported is false.

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

metrics

metrics : {
   abortExpiredTransactions: {
      passes: <integer>,
      successfulKills: <integer>,
      timedOutKills: <integer>
   },
   apiVersions: {
      <appName1>: <string>,
      <appName2>: <string>,
      <appName3>: <string>
   },
   aggStageCounters : {
      <aggregation stage> : Long("<num>")
   },
   changeStreams: {
      largeEventsFailed: Long("<num>"),
      largeEventsSplit: Long("<num>"),
      showExpandedEvents: Long("<num>")
   },
   commands: {
      <command>: {
         failed: Long("<num>"),
         validator: {
           total: Long("<num>"),
           failed: Long("<num>"),
           jsonSchema: Long("<num>")
         },
         total: Long("<num>"),
         rejected: Long("<num>")
      }
   },
   cursor : {
      moreThanOneBatch : Long("<num>"),
      timedOut : Long("<num>"),
      totalOpened : Long("<num>"),
      lifespan : {
         greaterThanOrEqual10Minutes : Long("<num>"),
         lessThan10Minutes : Long("<num>"),
         lessThan15Seconds : Long("<num>"),
         lessThan1Minute : Long("<num>"),
         lessThan1Second : Long("<num>"),
         lessThan30Seconds : Long("<num>"),
         lessThan5Seconds : Long("<num>")
      },
      open : {
         noTimeout : Long("<num>"),
         pinned : Long("<num>"),
         multiTarget : Long("<num>"),
         singleTarget : Long("<num>"),
         total : Long("<num>")
      }
   },
   document : {
      deleted : Long("<num>"),
      inserted : Long("<num>"),
      returned : Long("<num>"),
      updated : Long("<num>")
   },
   dotsAndDollarsFields : {
         inserts : Long("<num>"),
         updates : Long("<num>")
   },
   getLastError : {
      wtime : {
         num : <num>,
         totalMillis : <num>
      },
      wtimeouts : Long("<num>"),
      default : {
         unsatisfiable : Long("<num>"),
         wtimeouts : Long("<num>")
      }
   },
   mongos : {
      cursor : {
         moreThanOneBatch : Long("<num>"),
         totalOpened : Long("<num>")
      }
   },
   network : {  // Added in MongoDB 6.3
      totalEgressConnectionEstablishmentTimeMillis : Long("<num>"),
      totalIngressTLSConnections : Long("<num>"),
      totalIngressTLSHandshakeTimeMillis : Long("<num>"),
      totalTimeForEgressConnectionAcquiredToWireMicros : Long("<num>"),
      totalTimeToFirstNonAuthCommandMillis : Long("<num>")
      "averageTimeToCompletedTLSHandshakeMicros": Long("<num>"), // Added in MongoDB 8.2
      "averageTimeToCompletedHelloMicros": Long("<num>"), // Added in MongoDB 8.2
      "averageTimeToCompletedAuthMicros": Long("<num>") // Added in MongoDB 8.2
   },
   operation : {
      killedDueToClientDisconnect : Long("<num>"),  // Added in MongoDB 7.1
      killedDueToDefaultMaxTimeMSExpired : Long("<num>"),
      killedDueToMaxTimeMSExpired : Long("<num>"),  // Added in MongoDB 7.2
      killedDueToRangeDeletion: Long("<num>"), // Added in MongoDB 8.2
      numConnectionNetworkTimeouts : Long("<num>"),  // Added in MongoDB 6.3
      scanAndOrder : Long("<num>"),
      totalTimeWaitingBeforeConnectionTimeoutMillis : Long("<num>"),  // Added in MongoDB 6.3
      unsendableCompletedResponses : Long("<num>"),  // Added in MongoDB 7.1
      writeConflicts : Long("<num>")
   },
   operatorCounters : {
      expressions : {
         <command> : Long("<num>")
      },
      match : {
         <command> : Long("<num>")
      }
   },
   query: {
      allowDiskUseFalse: Long("<num>"),
      updateOneOpStyleBroadcastWithExactIDCount: Long("<num>"),
      bucketAuto: {
         spilledBytes: Long("<num>"),
         spilledDataStorageSize: Long("<num>"),
         spilledRecords: Long("<num>"),
         spills: Long("<num>")
      },
      lookup: {
         hashLookup: Long("<num>"),
         hashLookupSpillToDisk: Long("<num>"),
         indexedLoopJoin: Long("<num>"),
         nestedLoopJoin: Long("<num>")
      },
      multiPlanner: {
         classicCount: Long("<num>"),
         classicMicros: Long("<num>"),
         classicWorks: Long("<num>"),
         sbeCount: Long("<num>"),
         sbeMicros: Long("<num>"),
         sbeNumReads: Long("<num>"),
         histograms: {
            classicMicros: [
               { lowerBound: Long("0"), count: Long("<num>") },
               { < Additional histogram groups not shown. > },
               { lowerBound: Long("1073741824"), count: Long("<num>")> }>
            ],
            classicNumPlans: [
               { lowerBound: Long("0"), count: Long("<num>") },
               { < Additional histogram groups not shown. > },
               { lowerBound: Long("32"), count: Long("<num>") }
            ],
            classicWorks: [
               { lowerBound: Long("0"), count: Long("<num>") },
               { < Additional histogram groups not shown. > },
               { lowerBound: Long("32768"), count: Long("<num>") }
            ],
            sbeMicros: [
               { lowerBound: Long("0"), count: Long("<num>") },
               { < Additional histogram groups not shown. > },
               { lowerBound: Long("1073741824"), count: Long("<num>") }
            ],
            sbeNumPlans: [
               { lowerBound: Long("0"), count: Long("<num>") },
               { < Additional histogram groups not shown. > },
               { lowerBound: Long("32"), count: Long("<num>") }
            ],
            sbeNumReads: [
               { lowerBound: Long("0"), count: Long("<num>") },
               { < Additional histogram groups not shown. > },
               { lowerBound: Long("32768"), count: Long("<num>") }
            ]
         }
      },
      planCache: {
         classic: { hits: Long("<num>"), misses: Long("<num>"), replanned: Long("<num>") },
         sbe: { hits: Long("<num>"), misses: Long("<num>"), replanned: Long("<num>") }
      },
      queryFramework: {
         aggregate: {
            classicHybrid: Long("<num>"),
            classicOnly: Long("<num>"),
            cqf: Long("<num>"),
            sbeHybrid: Long("<num>"),
            sbeOnly: Long("<num>")
         },
         find: { classic: Long("<num>"), cqf: Long("<num>"), sbe: Long("<num>") }
      }
   },
   queryExecutor: {
      scanned : Long("<num>"),
      scannedObjects : Long("<num>"),
      collectionScans : {
         nonTailable : Long("<num>"),
         total : Long("<num>")
      },
      profiler : {
         collectionScans : {
            nonTailable : Long("<num>"),
            tailable : Long("<num>"),
            total : Long("<num>")
         }
      }
   },
   record : {
      moves : Long("<num>")
   },
   repl : {
      executor : {
         pool : {
            inProgressCount : <num>
         },
         queues : {
            networkInProgress : <num>,
            sleepers : <num>
         },
         unsignaledEvents : <num>,
         shuttingDown : <boolean>,
         networkInterface : <string>
      },
      apply : {
         attemptsToBecomeSecondary : Long("<num>"),
         batchSize: <num>,
         batches : {
            num : <num>,
            totalMillis : <num>
         },
         ops : Long("<num>")
      },
      write : {
         batchSize: <num>,
         batches : {
            num : <num>,
            totalMillis : <num>
         }
      },
      buffer : {
         write: {
            count : Long("<num>"),
            maxSizeBytes : Long("<num>"),
            sizeBytes : Long("<num>")
         },
         apply: {
            count : Long("<num>"),
            sizeBytes : Long("<num>"),
            maxSizeBytes : Long("<num>"),
            maxCount: Long("<num>")
         },
      },
      initialSync : {
         completed : Long("<num>"),
         failedAttempts : Long("<num>"),
         failures : Long("<num>")
      },
      network : {
         bytes : Long("<num>"),
         getmores : {
            num : <num>,
            totalMillis : <num>
         },
         notPrimaryLegacyUnacknowledgedWrites : Long("<num>"),
         notPrimaryUnacknowledgedWrites : Long("<num>"),
         oplogGetMoresProcessed : {
            num : <num>,
            totalMillis : <num>
         },
         ops : Long("<num>"),
         readersCreated : Long("<num>"),
         replSetUpdatePosition : {
            num : Long("<num>")
         }
      },
      reconfig : {
         numAutoReconfigsForRemovalOfNewlyAddedFields : Long("<num>")
      },
      stateTransition : {
         lastStateTransition : <string>,
         totalOperationsKilled : Long("<num>"),
         totalOperationsRunning : Long("<num>")
      },
      syncSource : {
         numSelections : Long("<num>"),
         numTimesChoseSame : Long("<num>"),
         numTimesChoseDifferent : Long("<num>"),
         numTimesCouldNotFind : Long("<num>")
      },
      waiters : {
         opTime : Long("<num>"),
         replication : Long("<num>"),
         replCoordMutexTotalWaitTimeInOplogServerStatusMillis: Long("<num>")
      }
   },
   storage : {
      freelist : {
         search : {
            bucketExhausted : <num>,
            requests : <num>,
            scanned : <num>
         }
      }
   },
   ttl : {
      deletedDocuments : Long("<num>"),
      passes : Long("<num>"),
      subPasses : Long("<num>")
   }
}

metrics

A document that returns various statistics that reflect the current use and state of a running mongod instance.

metrics.abortExpiredTransactions

Document that returns statistics on the current state of the abortExpiredTransactions thread.

metrics.abortExpiredTransactions.passes

Indicates the number of successful passes aborting transactions older than the transactionLifetimeLimitSeconds parameter.

If the passes value stops incrementing, it indicates that the abortExpiredTransactions thread may be stuck.

metrics.abortExpiredTransactions.successfulKills

Number of expired transactions successfully ended by MongoDB.

A session is checked out from a session pool to run database operations.

AbortExpiredTransactionsSessionCheckoutTimeout sets the maximum number of milliseconds for a session to be checked out when attempting to end an expired transaction.

If the expired transaction is successfully ended, MongoDB increments metrics.abortExpiredTransactions.successfulKills. If the transaction isn't successfully ended because it timed out when attempting to check out a session, MongoDB increments metrics.abortExpiredTransactions.timedOutKills.

New in version 8.1.在版本8.1中新增。 (also available in 8.0.13)

metrics.abortExpiredTransactions.timedOutKills

Number of expired transactions unsuccessfully ended by MongoDB because it timed out when attempting to check out a session.

A session is checked out from a session pool to run database operations.

AbortExpiredTransactionsSessionCheckoutTimeout sets the maximum number of milliseconds for a session to be checked out when attempting to end an expired transaction.

If the expired transaction is successfully ended, MongoDB increments metrics.abortExpiredTransactions.successfulKills. If the transaction isn't successfully ended because it timed out when attempting to check out a session, MongoDB increments metrics.abortExpiredTransactions.timedOutKills.

New in version 8.1.在版本8.1中新增。 (also available in 8.0.13)

metrics.aggStageCounters

A document that reports on the use of aggregation pipeline stages. The fields in metrics.aggStageCounters are the names of aggregation pipeline stages. For each pipeline stage, serverStatus reports the number of times that stage has been executed.

Updated in version 5.2 (and 5.0.6).

metrics.apiVersions

A document that contains:

• The name of each client application
• The Stable API version that each application was configured with within the last 24-hour period

Consider the following when viewing metrics.apiVersions:

• The possible returned values for each appname are:

  • default: The command was issued without a Stable API version specified.
  • 1: The command was issued with Stable API version 1.

  Note

  You may see both return values for an appname because you can specify a Stable API version at the command level. Some of your commands may have been issued with no Stable API version, while others were issued with version 1.

• API version metrics are retained for 24 hours. If no commands are issued with a specific API version from an application in the past 24 hours, that appname and API version will be removed from the metrics. This also applies to the default API version metric.
• Set the appname when connecting to a MongoDB instance by specifying the appname in the connection URI. ?appName=ZZZ sets the appname to ZZZZ.
• Drivers accessing the Stable API can set a default appname.
• If no appname is configured, a default value will be automatically populated based on the product. For example, for a MongoDB Compass connection with no appname in the URI, the metric returns: 'MongoDB Compass': [ 'default' ].

New in version 5.0..在版本5.0.中新增。/p>

metrics.operatorCounters

A document that reports on the use of aggregation pipeline operators and expressions.

metrics.operatorCounters.expressions

A document with a number that indicates how often Expressions ran.

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

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

New in version 5.0.在版本5.0中新增。

metrics.operatorCounters.match

A document with a number that indicates how often match expressions ran.

Match expression operators also increment as part of an aggregation pipeline $match stage. If the $match stage uses the $expr operator, the counter for $expr increments, but the component counters do not increment.

Consider the following query:

db.matchCount.aggregate(
   [
      { $match:
         {  $expr: { $gt: [ "$_id", 0 ] } }
      }
   ]
)

The counter for $expr increments when the query runs. The counter for $gt does not.

metrics.changeStreams.largeEventsSplit

The number of change stream events larger than 16 MB that were split into smaller fragments. Events are only split if you use the $changeStreamSplitLargeEvent pipeline stage.

New in version 7.0.在版本7.0中新增。 (Also available in 6.0.9)

metrics.changeStreams

A document that reports information about change stream events larger than 16 MB.

New in version 7.0.在版本7.0中新增。

metrics.changeStreams.largeEventsFailed

The number of change stream events that caused a BSONObjectTooLarge exception because the event was larger than 16 MB. To prevent the exception, see $changeStreamSplitLargeEvent.

New in version 7.0.在版本7.0中新增。 (Also available in 6.0.9 and 5.0.19)

metrics.changeStreams.showExpandedEvents

The number of change stream cursors with the showExpandedEvents option set to true.

The counter for showExpandedEvents increments when you:

• Open a change stream cursor.
• Run the explain command on a change stream cursor.

New in version 7.1.在版本7.1中新增。

metrics.commands

A document that reports on the use of database commands. The fields in metrics.commands are the names of database commands. For each command, the serverStatus reports the total number of executions and the number of failed executions.

metrics.commands includes replSetStepDownWithForce (i.e. the replSetStepDown command with force: true) as well as the overall replSetStepDown. In earlier versions, the command reported only overall replSetStepDown metrics.

metrics.commands.<command>.failed

The number of times <command> failed on this mongod.

metrics.commands.<create or collMod>.validator

For the create and collMod commands, a document that reports on non-empty validator objects passed to the command to specify validation rules or expressions for the collection.

metrics.commands.<create or collMod>.validator.total

The number of times a non-empty validator object was passed as an option to the command on this mongod.

metrics.commands.<create or collMod>.validator.failed

The number of times a call to the command on this mongod failed with a non-empty validator object due to a schema validation error.

metrics.commands.<create or collMod>.validator.jsonSchema

The number of times a validator object with a $jsonSchema was passed as an option to the command on this mongod.

metrics.commands.<command>.total

The number of times <command> executed on this mongod.

metrics.commands.<command>.rejected

The number of times <command> was rejected on this mongod because the command or operation has an associated query setting where the reject field is true.

To set the reject field, use setQuerySettings.

New in version 8.0.在版本8.0中新增。

metrics.commands.update.pipeline

The number of times an aggregation pipeline was used to update documents on this mongod. Subtract this value from the total number of updates to get the number of updates made with document syntax.

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

metrics.commands.findAndModify.pipeline

The number of times findAndModify() was used in an aggregation pipeline to update documents on this mongod.

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

metrics.commands.update.arrayFilters

The number of times an arrayFilter was used to update documents on this mongod.

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

metrics.commands.findAndModify.arrayFilters

The number of times an arrayFilter was used with findAndModify() to update documents on this mongod.

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

metrics.document

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

metrics.document.deleted

The total number of documents deleted.

metrics.document.inserted

The total number of documents inserted.

metrics.document.returned

The total number of documents returned by queries.

metrics.document.updated

The total number of documents matched for update operations. This value is not necessarily the same as the number of documents modified by updates.

metrics.dotsAndDollarsFields

A document with a number that indicates how often insert or update operations ran using a dollar ($) prefixed name. The value does not report the exact number of operations.

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

New in version 5.0.在版本5.0中新增。

metrics.executor

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

metrics.getLastError

A document that reports on write concern use.

metrics.getLastError.wtime

A document that reports write concern operation counts with a w argument greater than 1.

metrics.getLastError.wtime.num

The total number of 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.)

metrics.getLastError.wtime.totalMillis

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

metrics.getLastError.wtimeouts

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

metrics.getLastError.default

A document that reports on when 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:

Provenance	Description描述
clientSupplied	The write concern was specified in the application.
customDefault	The write concern originated from a custom defined default value. See setDefaultRWConcern.
getLastErrorDefaults	The write concern originated from the replica set's settings.getLastErrorDefaults field.
implicitDefault	The write concern originated from the server in absence of all other write concern specifications.

metrics.getLastError.default.unsatisfiable

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

metrics.getLastError.default.wtimeouts

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

metrics.mongos

A document that contains metrics about mongos.

metrics.mongos.cursor

A document that contains metrics for cursors used by mongos.

metrics.mongos.cursor.moreThanOneBatch

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

New in version 5.0.在版本5.0中新增。

metrics.mongos.cursor.totalOpened

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

New in version 5.0.在版本5.0中新增。

metrics.network

New in version 6.3.在版本6.3中新增。

A document that reports server network metrics.

metrics.network.totalEgressConnectionEstablishmentTimeMillis

New in version 6.3.在版本6.3中新增。

The total time in milliseconds to establish server connections.

metrics.network.totalIngressTLSConnections

New in version 6.3.在版本6.3中新增。

The total number of incoming connections to the server that use TLS. The number is cumulative and is the total after the server was started.

metrics.network.totalIngressTLSHandshakeTimeMillis

New in version 6.3.在版本6.3中新增。

The total time in milliseconds that incoming connections to the server have to wait for the TLS network handshake to complete. The number is cumulative and is the total after the server was started.

metrics.network.totalTimeForEgressConnectionAcquiredToWireMicros

New in version 6.3.在版本6.3中新增。

The total time in microseconds that operations wait between acquisition of a server connection and writing the bytes to send to the server over the network. The number is cumulative and is the total after the server was started.

metrics.network.totalTimeToFirstNonAuthCommandMillis

New in version 6.3.在版本6.3中新增。

The total time in milliseconds from accepting incoming connections to the server and receiving the first operation that isn't part of the connection authentication handshake. The number is cumulative and is the total after the server was started.

metrics.network.averageTimeToCompletedTLSHandshakeMicros

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1)

The average time in microseconds that it takes to complete a TLS handshake for incoming connections.

metrics.network.averageTimeToCompletedHelloMicros

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1)

The time in microseconds between the beginning of connection establishment and the completion of the hello command. You can use this metric to tune the ingressConnectionEstablishmentMaxQueueDepth and ingressConnectionEstablishmentRatePerSec to ensure that there is proper time allotted to complete the connection establishment after exiting the queue.

metrics.network.averageTimeToCompletedAuthMicros

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1)

The time in microseconds the SASL auth exchange takes to be completed after the beginning of connection establishment.

metrics.operation

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

metrics.operation.killedDueToClientDisconnect

New in version 7.1.在版本7.1中新增。

Total number of operations cancelled before completion because the client disconnected.

metrics.operation.killedDueToDefaultMaxTimeMSExpired

New in version 8.0.在版本8.0中新增。

Total number of operations that timed out due to the cluster-level default timeout, defaultMaxTimeMS.

metrics.operation.killedDueToMaxTimeMSExpired

New in version 7.2.在版本7.2中新增。

Total number of operations that timed out due to the operation-level timeout, cursor.maxTimeMS().

metrics.operation.killedDueToRangeDeletion

New in version 8.2.在版本8.2中新增。

Total number of operations terminated because of orphan range cleanup. To learn more, see terminateSecondaryReadsOnOrphanCleanup.

metrics.operation.numConnectionNetworkTimeouts

New in version 6.3.在版本6.3中新增。

Total number of operations that failed because of server connection acquisition time out errors.

metrics.operation.scanAndOrder

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

metrics.operation.totalTimeWaitingBeforeConnectionTimeoutMillis

New in version 6.3.在版本6.3中新增。

Total time in milliseconds that operations waited before failing because of server connection acquisition time out errors.

metrics.operation.unsendableCompletedResponses

New in version 7.1.在版本7.1中新增。

Total number of operations that completed server-side but did not send their response to the client because the connection between the client and server failed or disconnected.

metrics.operation.writeConflicts

The total number of queries that encountered write conflicts.

metrics.query.bucketAuto.spilledBytes

The number of in-memory bytes spilled to disk by the $bucketAuto stage.

New in version 8.2.在版本8.2中新增。

metrics.query.bucketAuto.spilledDataStorageSize

The total disk space, in bytes, used by the spilled data from the $bucketAuto stage.

New in version 8.2.在版本8.2中新增。

metrics.query.bucketAuto.spilledRecords

The number of records spilled to disk by the $bucketAuto stage.

New in version 8.2.在版本8.2中新增。

metrics.query.bucketAuto.spills

The number of times the $bucketAuto stage spilled to disk.

New in version 8.2.在版本8.2中新增。

metrics.query.lookup

A document that provides detailed data on the use of the $lookup stage with the slot-based query execution engine. To learn more, see $lookup Optimization.

These metrics are primarily intended for internal use by MongoDB.

New in version 6.1.在版本6.1中新增。/p>

metrics.query.multiPlanner

Provides detailed query planning data for the slot-based query execution engine and the classic query engine. For more information on the slot-based query execution engine see: Slot-Based Query Execution Engine Pipeline Optimizations.

These metrics are primarily intended for internal use by MongoDB.

New in version 6.0.0 and 5.0.9

metrics.query.sort

A document that holds counters related to sort stages.

New in version 6.2.在版本6.2中新增。

metrics.query.sort.spillToDisk

The total number of writes to disk caused by sort stages.

New in version 6.2.在版本6.2中新增。

metrics.query.sort.totalBytesSorted

The total amount of sorted data in bytes.

New in version 6.2.在版本6.2中新增。

metrics.query.sort.totalKeysSorted

The total number of keys used in sorts.

New in version 6.2.在版本6.2中新增。

query.multiPlanner.classicMicros

Aggregates the total number of microseconds spent in the classic multiplanner.

query.multiPlanner.classicWorks

Aggregates the total number of "works" performed in the classic multiplanner.

query.multiPlanner.classicCount

Aggregates the total number of invocations of the classic multiplanner.

query.multiPlanner.sbeMicros

Aggregates the total number of microseconds spent in the slot-based execution engine multiplanner.

query.multiPlanner.sbeNumReads

Aggregates the total number of reads done in the slot-based execution engine multiplanner.

query.multiPlanner.sbeCount

Aggregates the total number of invocations of the slot-based execution engine multiplanner.

query.multiPlanner.histograms.classicMicros

A histogram measuring the number of microseconds spent in an invocation of the classic multiplanner.

query.multiPlanner.histograms.classicWorks

A histogram measuring the number of "works" performed during an invocation of the classic multiplanner.

query.multiPlanner.histograms.classicNumPlans

A histogram measuring the number of plans in the candidate set during an invocation of the classic multiplanner.

query.multiPlanner.histograms.sbeMicros

A histogram measuring the number of microseconds spent in an invocation of the slot-based execution engine multiplanner.

query.multiPlanner.histograms.sbeNumReads

A histogram measuring the number of reads during an invocation of the slot-based execution engine multiplanner.

query.multiPlanner.histograms.sbeNumPlans

A histogram measuring the number of plans in the candidate set during an invocation of the slot-based execution engine multiplanner.

query.planning.fastPath.express

The number of queries that use an optimized index scan plan consisting of one of the following plan stages:

• EXPRESS_CLUSTERED_IXSCAN
• EXPRESS_DELETE
• EXPRESS_IXSCAN
• EXPRESS_UPDATE

For more information on query plans, see Explain Results.

New in version 8.1.在版本8.1中新增。

query.planning.fastPath.idHack

The number of queries that contain the _id field. For these queries, MongoDB uses the default index on the _id field and skips all query plan analysis.

New in version 8.1.在版本8.1中新增。

query.queryFramework.aggregate

A document that reports on the number of aggregation operations run on each query framework. The subfields in query.queryFramework.aggregate indicate the number of times each framework was used to perform an aggregation operation.

query.queryFramework.find

A document that reports on the number of find operations run on each query framework. The subfields in query.queryFramework.find indicate the number of times each framework was used to perform a find operation.

metrics.queryExecutor

A document that reports data from the query execution system.

metrics.queryExecutor.scanned

The total number of index items scanned during queries and query-plan evaluation. This counter is the same as totalKeysExamined in the output of explain().

metrics.queryExecutor.scannedObjects

The total number of documents scanned during queries and query-plan evaluation. This counter is the same as totalDocsExamined in the output of explain().

metrics.queryExecutor.collectionScans

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

metrics.queryExecutor.collectionScans.nonTailable

The number of queries that performed a collection scan that did not use a tailable cursor.

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 tailable cursor.

metrics.queryExecutor.profiler.collectionScans.nonTailable

The number of queries that performed a collection scan on a profile collection that did not use a tailable cursor.

metrics.queryExecutor.profiler.collectionScans.tailable

The number of queries that performed a collection scan on a profile collection that used a tailable cursor.

metrics.queryExecutor.profiler.collectionScans.total

The total number of queries that performed a collection scan on a profile collection. This includes queries that used both tailable and non-tailable cursors.

metrics.record

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

metrics.repl

A document that reports metrics related to the replication process. metrics.repl document appears on all mongod instances, even those that aren't members of replica sets.

metrics.repl.apply

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

metrics.repl.apply.batchSize

The total number of oplog operations applied. The 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 metrics.repl.apply.ops.

metrics.repl.apply.batches

metrics.repl.apply.batches reports on the oplog application process on secondaries members of replica sets. See Multithreaded Replication for more information on the oplog application processes.

metrics.repl.apply.batches.num

The total number of batches applied across all databases.

metrics.repl.apply.batches.totalMillis

The total amount of time in milliseconds the mongod has spent applying operations from the oplog.

metrics.repl.apply.ops

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

Tip

metrics.repl.apply.batchSize

metrics.repl.write

Document that reports on entries written to the oplog.

New in version 8.0.在版本8.0中新增。

metrics.repl.write.batchSize

Total number of entries written to the oplog. This metric updates with the number of entries in each batch as the member finishes writing the batch to the oplog.

New in version 8.0.在版本8.0中新增。

metrics.repl.write.batches

Document that reports on the oplog writing process for secondary members.

New in version 8.0.在版本8.0中新增。

metrics.repl.write.batches.num

Total number of batches written across all databases.

New in version 8.0.在版本8.0中新增。

metrics.repl.write.batches.totalMillis

Total time in milliseconds the member has spent writing entries to the oplog.

New in version 8.0.在版本8.0中新增。

metrics.repl.buffer

MongoDB buffers oplog operations from the replication sync source buffer before applying oplog entries in a batch. metrics.repl.buffer provides a way to track oplog buffers. See Multithreaded Replication for more information on the oplog application process.

Changed in version 8.0.在版本8.0中的更改。

Starting in MongoDB 8.0, secondaries now update the local oplog and apply changes to the database in parallel. For each batch of oplog entries, MongoDB uses two buffers:

• The write buffer receives new oplog entries from the primary. The writer adds these entries to the local oplog and sends them to the applier.
• The apply buffer receives new oplog entries from the writer. The applier uses these entries to update the local database.

This is a breaking change as it deprecates the older metrics.repl.buffer status metrics.

metrics.repl.buffer.apply

Provides information on the status of the oplog apply buffer.

New in version 8.0.在版本8.0中新增。

metrics.repl.buffer.apply.count

The current number of operations in the oplog apply buffer.

New in version 8.0.在版本8.0中新增。

metrics.repl.buffer.apply.maxCount

Maximum number of operations in the oplog apply buffer. mongod sets this value using a constant, which is not configurable.

New in version 8.0.在版本8.0中新增。

metrics.repl.buffer.apply.maxSizeBytes

Maximum size of the apply buffer. mongod sets this size using a constant, which is not configurable.

New in version 8.0.在版本8.0中新增。

metrics.repl.buffer.apply.sizeBytes

The current size of the contents of the oplog apply buffer.

New in version 8.0.在版本8.0中新增。

metrics.repl.buffer.count

Deprecated since version 8.0.

Starting in MongoDB 8.0, secondaries use separate buffers to write and apply oplog entries. For the current number of operations in the oplog buffers, see the apply.count or write.count status metrics.

metrics.repl.buffer.maxSizeBytes

Deprecated since version 8.0.

Starting in MongoDB 8.0, secondaries use separate buffers to write and apply oplog entries. For the maximum size of the buffers, see the apply.maxSizeBytes or write.maxSizeBytes status metrics.

metrics.repl.buffer.sizeBytes

Deprecated since version 8.0.

Starting in MongoDB 8.0, secondaries use separate buffers to write and apply oplog entries. For the current size of the oplog buffers, see the apply.sizeBytes or write.sizeBytes status metrics.

metrics.repl.buffer.write

Provides information on the status of the oplog write buffer.

New in version 8.0.在版本8.0中新增。

metrics.repl.buffer.write.count

The current number of operations in the oplog write buffer.

New in version 8.0.在版本8.0中新增。

metrics.repl.buffer.write.maxSizeBytes

Maximum size of the write buffer. mongod sets this value using a constant, which is not configurable.

New in version 8.0.在版本8.0中新增。

metrics.repl.buffer.write.sizeBytes

The current size of the contents of the oplog write buffer.

New in version 8.0.在版本8.0中新增。

metrics.repl.network

metrics.repl.network reports network use by the replication process.

metrics.repl.network.bytes

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

metrics.repl.network.getmores

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

metrics.repl.network.getmores.num

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.

metrics.repl.network.getmores.totalMillis

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.

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.

metrics.repl.network.notPrimaryLegacyUnacknowledgedWrites

The number of unacknowledged (w: 0) legacy write operations (see Opcodes) that failed because the current mongod is not in PRIMARY state.

metrics.repl.network.notPrimaryUnacknowledgedWrites

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

metrics.repl.network.oplogGetMoresProcessed

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

metrics.repl.network.oplogGetMoresProcessed.num

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

metrics.repl.network.oplogGetMoresProcessed.totalMillis

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

metrics.repl.network.ops

The total number of operations read from the replication source.

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, metrics.repl.network.readersCreated will increment every time MongoDB selects a new source for replication.

metrics.repl.network.replSetUpdatePosition

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

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.

Note

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

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.

New in version 5.0.在版本5.0中新增。

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 SECONDARY, RECOVERING, or ROLLBACK, the primary automatically removes the member's newlyAdded field. The newlyAdded fields are stored in the local.system.replset collection.

New in version 5.0.在版本5.0中新增。

metrics.repl.stateTransition

Information on user operations when the member undergoes one of the following transitions that can stop user operations:

• The member steps up to become a primary.
• The member steps down to become a secondary.
• The member is actively performing a rollback.

metrics.repl.stateTransition.lastStateTransition

The transition being reported:

State Change	Description描述
"stepUp"	The member steps up to become a primary.
"stepDown"	The member steps down to become a secondary.
"rollback"	The member is actively performing a rollback.
""	The member has not undergone any state changes.

metrics.repl.stateTransition.totalOperationsKilled

The total number of operations stopped during the mongod instance's state change.

New in version 7.3.在版本7.3中新增。 totalOperationsKilled replaces userOperationsKilled

metrics.repl.stateTransition.totalOperationsRunning

The total number of operations that remained running during the mongod instance's state change.

New in version 7.3.在版本7.3中新增。 totalOperationsRunning replaces userOperationsRunning

metrics.repl.stateTransition.userOperationsKilled

Deprecated since version 7.3: totalOperationsKilled replaces userOperationsKilled.

metrics.repl.stateTransition.userOperationsRunning

Deprecated since version 7.3: totalOperationsRunning replaces userOperationsRunning.

metrics.repl.syncSource

Information on a replica set node's sync source selection process.

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.

metrics.repl.syncSource.numTimesChoseSame

Number of times a node kept its original sync source after re-evaluating if its current sync source was optimal.

metrics.repl.syncSource.numTimesChoseDifferent

Number of times a node chose a new sync source after re-evaluating if its current sync source was optimal.

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.

metrics.repl.timestamps

A document that reports on the replication timestamps.

New in version 8.1.在版本8.1中新增。

metrics.repl.timestamps.oldestTimestamp

The timestamp for the oldest snapshot. A snapshot is a copy of the data in a mongod instance at a specific point in time.

New in version 8.1.在版本8.1中新增。

metrics.repl.waiters.replication

The number of threads waiting for replicated or journaled write concern acknowledgments.

New in version 7.3.在版本7.3中新增。

metrics.repl.waiters.opTime

The number of threads queued for local replication optime assignments.

New in version 7.3.在版本7.3中新增。

metrics.repl.waiters.replCoordMutexTotalWaitTimeInOplogServerStatusMillis

The average wait time in milliseconds to acquire the replication coordinator mutex. MongoDB measures this time when it generates the server status oplog section. This metric helps you identify potential replication performance issues related to mutex contention.

New in version 8.2.在版本8.2中新增。

metrics.storage.freelist.search.bucketExhausted

The number of times that mongod has examined the free list without finding a large record allocation.

metrics.storage.freelist.search.requests

The number of times mongod has searched for available record allocations.

metrics.storage.freelist.search.scanned

The number of available record allocations mongod has searched.

metrics.ttl

A document that reports on the operation of the resource use of the ttl index process.

metrics.ttl.deletedDocuments

The total number of documents deleted from collections with a ttl index.

metrics.ttl.invalidTTLIndexSkips

Number of TTL deletes skipped due to a TTL secondary index being present, but not valid for TTL deletion.

• 0 indicates all secondary TTL indexes are eligible for TTL deletion.
• A non-zero value indicates there is an invalid secondary TTL index.

If there is an invalid secondary TTL index, you must manually modify the secondary index to use automatic TTL deletion.

New in version 8.1.在版本8.1中新增。

metrics.ttl.passes

Number of passes performed by the TTL background process to check for expired documents. A pass is complete when the TTL monitor has deleted as many candidate documents as it can find from all TTL indexes. For more information on the TTL index deletion process, see Deletion Process.

metrics.ttl.subPasses

Number of sub-passes performed by the TTL background process to check for expired documents. For more information on the TTL index deletion process, see Deletion Process.

metrics.cursor

A document that contains data regarding cursor state and use.

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 getMore command.

New in version 5.0.在版本5.0中新增。

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.

metrics.cursor.totalOpened

The total number of cursors that have been opened since the server process started, including cursors currently open. Differs from metrics.cursor.open.total, which is the number of currently open cursors only.

New in version 5.0.在版本5.0中新增。

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 killCursors command or the cursor has no remaining objects in the batch.

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

New in version 5.0.在版本5.0中新增。

metrics.cursor.lifespan.greaterThanOrEqual10Minutes

The number of cursors with a lifespan >= 10 minutes.

New in version 5.0.在版本5.0中新增。

metrics.cursor.lifespan.lessThan10Minutes

The number of cursors with a lifespan >= 1 minute to < 10 minutes.

New in version 5.0.在版本5.0中新增。

metrics.cursor.lifespan.lessThan15Seconds

The number of cursors with a lifespan >= 5 seconds to < 15 seconds.

New in version 5.0.在版本5.0中新增。

metrics.cursor.lifespan.lessThan1Minute

The number of cursors with a lifespan >= 30 seconds to < 1 minute.

New in version 5.0.在版本5.0中新增。

metrics.cursor.lifespan.lessThan1Second

The number of cursors with a lifespan < 1 second.

New in version 5.0.在版本5.0中新增。

metrics.cursor.lifespan.lessThan30Seconds

The number of cursors with a lifespan >= 15 seconds to < 30 seconds.

New in version 5.0.在版本5.0中新增。

metrics.cursor.lifespan.lessThan5Seconds

The number of cursors with a lifespan >= 1 second to < 5 seconds.

New in version 5.0.在版本5.0中新增。

metrics.cursor.open

A document that contains data regarding open cursors.

metrics.cursor.open.noTimeout

The number of open cursors with the option DBQuery.Option.noTimeout set to prevent timeout after a period of inactivity.

metrics.cursor.open.pinned

The number of "pinned" open cursors.

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.

metrics.cursor.open.singleTarget

The total number of cursors that only target a single shard. Only mongos instances report metrics.cursor.open.singleTarget values.

metrics.cursor.open.multiTarget

The total number of cursors that only target more than one shard. Only mongos instances report metrics.cursor.open.multiTarget values.

mirroredReads

Available on mongod only.

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

mirroredReads

Available on mongod only.

A document that reports on mirrored reads. To return mirroredReads information, you must explicitly specify the inclusion:

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

mirroredReads.processedAsSecondary

New in version 6.2.在版本6.2中新增。

The number of mirrored reads processed by this member while a secondary.

Tip

mirrorReads Parameter

mirroredReads.seen

The number of operations that support mirroring received by this member.

Tip

mirrorReads Parameter

mirroredReads.sent

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.

Tip

mirrorReads Parameter

network

network : {
   egress : {
      bytesIn : Long("<num>"),
      bytesOut : Long("<num>"),
      physicalBytesIn : Long("<num>"),
      physicalBytesOut : Long("<num>"),
      numRequests : Long("<num>"),
   }
   bytesIn : Long("<num>"),
   bytesOut : Long("<num>"),
   physicalBytesIn : Long("<num>"),
   physicalBytesOut : Long("<num>"),
   numSlowDNSOperations : Long("<num>"),
   numSlowSSLOperations : Long("<num>"),
   numRequests : Long("<num>"),
   tcpFastOpen : {
      kernelSetting : Long("<num>"),
      serverSupported : <bool>,
      clientSupported : <bool>,
      accepted : Long("<num>")
   },
   compression : {
      snappy : {
         compressor : { bytesIn : Long("<num>"), bytesOut : Long("<num>") },
         decompressor : { bytesIn : Long("<num>"), bytesOut : Long("<num>") }
      },
      zstd : {
         compressor : { bytesIn : Long("<num>"), bytesOut : Long("<num>") },
         decompressor : { bytesIn : Long("<num>"), bytesOut : Long("<num>") }
      },
      zlib : {
         compressor : { bytesIn : Long("<num>"), bytesOut : Long("<num>") },
         decompressor : { bytesIn : Long("<num>"), bytesOut : Long("<num>") }
      }
   },
   serviceExecutors : {
      passthrough : {
         threadsRunning : <num>,
         clientsInTotal : <num>,
         clientsRunning : <num>,
         clientsWaitingForData : <num>
      },
      fixed : {
         threadsRunning : <num>,
         clientsInTotal : <num>,
         clientsRunning : <num>,
         clientsWaitingForData : <num>
      }
   },
   listenerProcessingTime : { durationMicros : <num> }  // Added in MongoDB 6.3
}

network

A document that reports data on MongoDB's network use. These statistics measure ingress and egress connections, specifically the traffic seen by the mongod or mongos over network connections initiated by clients or other mongod or mongos instances.

network.egress

Reports data on the traffic from egress connections initiated by this mongod or mongos instance. In most cases, the egress connections are mongos communicating with mongod for sharding, or mongod communicating with mongod for replication. It is also possible that mongod or mongos are communicating with external services, such as mongot.

network.egress.bytesIn

The total number of logical bytes that mongod or mongos instances have received over network connections that they have initiated to other nodes/services. Logical bytes are the exact number of bytes that a given file contains.

network.egress.bytesOut

The total number of logical bytes that mongod or mongos instances have sent over network connections that they have initiated to other nodes/services. Logical bytes correspond to the number of bytes that a given file contains.

network.egress.physicalBytesIn

The total number of physical bytes that mongod or mongos instances has received over network connections that they have initiated to other nodes/services. Physical bytes are the number of bytes that actually reside on disk.

network.egress.physicalBytesOut

The total number of physical bytes that mongod or mongos instances have sent over network connections that they have initiated to other nodes/services. Physical bytes are the number of bytes that actually reside on disk.

network.egress.numRequests

The total number of distinct requests that mongod or mongos have sent and received responses to. Use this value to provide context for the network.egress.bytesIn and network.egress.bytesOut values to ensure that MongoDB's network utilization is consistent with expectations and application use.

network.bytesIn

The total number of logical bytes that the server has received over network connections initiated by clients or other mongod or mongos instances. Logical bytes are the exact number of bytes that a given file contains.

network.bytesOut

The total number of logical bytes that the server has sent over network connections initiated by clients or other mongod or mongos instances. Logical bytes correspond to the number of bytes that a given file contains.

network.physicalBytesIn

The total number of physical bytes that the server has received over network connections initiated by clients or other mongod or mongos instances. Physical bytes are the number of bytes that actually reside on disk.

network.physicalBytesOut

The total number of physical bytes that the server has sent over network connections initiated by clients or other mongod or mongos instances. Physical bytes are the number of bytes that actually reside on disk.

network.numSlowDNSOperations

The total number of DNS resolution operations which took longer than 1 second.

network.numSlowSSLOperations

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

network.numRequests

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

network.tcpFastOpen

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

network.tcpFastOpen.kernelSetting

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.

network.tcpFastOpen.serverSupported

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

network.tcpFastOpen.clientSupported

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

network.tcpFastOpen.accepted

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

network.compression

A document that reports on the amount of data compressed and decompressed by each network compressor library.

network.compression.snappy

A document that returns statistics on the number of bytes that have been compressed and decompressed with the snappy library.

network.compression.zstd

A document that returns statistics on the number of bytes that have been compressed and decompressed with the zstd library.

network.compression.zlib

A document that returns statistics on the number of bytes that have been compressed and decompressed with the zlib library.

network.serviceExecutors

New in version 5.0.在版本5.0中新增。

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

network.serviceExecutors.passthrough

New in version 5.0.在版本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.

network.serviceExecutors.passthrough.threadsRunning

New in version 5.0.在版本5.0中新增。

Number of threads running in the passthrough service executor.

network.serviceExecutors.passthrough.clientsInTotal

New in version 5.0.在版本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.

network.serviceExecutors.passthrough.clientsRunning

New in version 5.0.在版本5.0中新增。

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

network.serviceExecutors.passthrough.clientsWaitingForData

New in version 5.0.在版本5.0中新增。

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

network.serviceExecutors.fixed

New in version 5.0.在版本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.

network.serviceExecutors.fixed.threadsRunning

New in version 5.0.在版本5.0中新增。

Number of threads running in the fixed service executor.

network.serviceExecutors.fixed.clientsInTotal

New in version 5.0.在版本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.

network.serviceExecutors.fixed.clientsRunning

New in version 5.0.在版本5.0中新增。

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

network.serviceExecutors.fixed.clientsWaitingForData

New in version 5.0.在版本5.0中新增。

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

network.listenerProcessingTime

New in version 6.3.在版本6.3中新增。

A document that reports the total time the database listener spends allocating incoming database connection requests to dedicated threads.

network.listenerProcessingTime.durationMicros

New in version 6.3.在版本6.3中新增。

Total time in microseconds the database listener spends allocating incoming database connection requests to dedicated threads that perform database operations.

opLatencies

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

opLatencies

A document containing operation latencies for the instance as a whole. See latencyStats Document for a description of this document.

Starting in MongoDB 6.2, the opLatencies metric reports for both mongod and mongos instances. Latencies reported by mongos include operation latency time and communication time between the mongod and mongos instances.

To include the histogram in the opLatencies output, run the following command:

db.runCommand( { serverStatus: 1, opLatencies: { histograms: true } } ).opLatencies

opLatencies.reads

Latency statistics for read requests.

opLatencies.writes

Latency statistics for write operations.

opLatencies.commands

Latency statistics for database commands.

opLatencies.transactions

Latency statistics for database transactions.

opWorkingTime

opWorkingTime : {
   commands : <document>,
   reads : <document>,
   writes : <document>,
   transactions : <document>
}

opWorkingTime

Document that includes information on operation execution for the instance. See latencyStats Document for a description of this document.

The fields under opWorkingTime are measured in workingMillis, which is the amount of time that MongoDB spends working on that operation. This means that factors such as waiting for locks and flow control don't affect opWorkingTime.

To include the histogram in the opWorkingTime output, run the following command:

db.runCommand( { serverStatus: 1, opWorkingTime: { histogram: true } } ).opWorkingTime

New in version 8.0.在版本8.0中新增。

opWorkingTime.commands

Document that reports execution statistics for database commands.

New in version 8.0.在版本8.0中新增。

opWorkingTime.reads

Document that reports execution statistics for read operations.

New in version 8.0.在版本8.0中新增。

opWorkingTime.writes

Document that reports execution statistics for write operations.

New in version 8.0.在版本8.0中新增。

opWorkingTime.transactions

Document that reports execution statistics for transactions.

New in version 8.0.在版本8.0中新增。

opReadConcernCounters

Only for mongod instances

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

opReadConcernCounters

Removed in version 5.0. Replaced by readConcernCounters.

A document that reports on the read concern level specified by query operations to the mongod instance since it last started.

Specified w	Description描述
"available"	Number of query operations that specified read concern level "available".
"linearizable"	Number of query operations that specified read concern level "linearizable".
"local"	Number of query operations that specified read concern level "local".
"majority"	Number of query operations that specified read concern level "majority".
"snapshot"	Number of query operations that specified read concern level "snapshot".
"none"	Number of query operations that did not specify a read concern level and instead used the default read concern level.

The sum of the opReadConcernCounters equals opcounters.query.

opWriteConcernCounters

Only for mongod instances

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

opWriteConcernCounters

A document that reports on the write concerns specified by write operations to the mongod instance since it last started.

More specifically, the opWriteConcernCounters reports on the w: <value> 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

Only available when reportOpWriteConcernCountersInServerStatus parameter is set to true (false by default).

opWriteConcernCounters.insert

A document that reports on the w: <value> specified by insert operations to the mongod instance since it last started:

Note

Only available when reportOpWriteConcernCountersInServerStatus parameter is set to true (false by default).

insert : {
   wmajority : Long("<num>"),
   wnum : {
      <num> :  Long("<num>"),
      ...
   },
   wtag : {
      <tag1> :  Long("<num>"),
      ...
   },
   none : Long("<num>"),
   noneInfo : {
      CWWC : {
         wmajority : Long("<num>"),
         wnum : {},
         wtag : {}
      },
      implicitDefault : {
         wmajority : Long("<num>")
         wnum : {}
      }
   }
},

Specified w	Description描述
"wmajority"	Number of insert operations that specified w: "majority".
"wnum"	Number of insert operations that specified w: <num>. The counts are grouped by the specific``<num>``.
"wtag"	Number of insert operations that specified w: <tag>. 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 "majority".
"noneInfo"	Number of non-transaction query operations that use default write concerns. The metrics track usage of the cluster wide write concern (the global default write concern) and the implicit-default write concern. The sum of the values in opWriteConcernCounters.noneInfo should equal the value of opWriteConcernCounters.none.

The sum of the opWriteConcernCounters.insert equals opcounters.insert.

opWriteConcernCounters.update

A document that reports on the w: <value> specified by update operations to the mongod instance since it last started:

Note

Only available when reportOpWriteConcernCountersInServerStatus parameter is set to true (false by default).

update : {
   wmajority : Long("<num>"),
   wnum : {
      <num> :  Long("<num>"),
      ...
   },
   wtag : {
      <tag1> :  Long("<num>"),
      ...
   },
   none : Long("<num>"),
   noneInfo : {
      CWWC : {
         wmajority : Long("<num>"),
         wnum : {},
         wtag : {}
      },
      implicitDefault : {
         wmajority : Long("<num>")
         wnum : {}
      }
   }
},

Specified w	Description描述
"wmajority"	Number of update operations that specified w: "majority".
"wnum"	Number of update operations that specified w: <num>. The counts are grouped by the specific <num>.
"wtag"	Number of update operations that specified w: <tag>. 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.
"noneInfo"	Number of non-transaction query operations that use default write concerns. The metrics track usage of the cluster wide write concern (the global default write concern) and the implicit-default write concern. The sum of the values in opWriteConcernCounters.noneInfo should equal the value of opWriteConcernCounters.none.

The sum of the opWriteConcernCounters.update equals opcounters.update.

opWriteConcernCounters.delete

A document that reports on the w: <value> specified by delete operations to the mongod instance since it last started:

Note

Only available when reportOpWriteConcernCountersInServerStatus parameter is set to true (false by default).

delete : {
   wmajority :  Long("<num>"),
   wnum : {
      <num> :  Long("<num>"),
      ...
   },
   wtag : {
      <tag1> :  Long("<num>"),
      ...
   },
   none : Long("<num>"),
   noneInfo : {
      CWWC : {
         wmajority : Long("<num>"),
         wnum : {},
         wtag : {}
      },
      implicitDefault : {
         wmajority : Long("<num>")
         wnum : {}
      }
   }
}

Specified w	Description描述
"wmajority"	Number of delete operations that specified w: "majority".
"wnum"	Number of delete operations that specified w: <num>. The counts are grouped by the specific <num>.
"wtag"	Number of delete operations that specified w: <tag>. 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.
"noneInfo"	Number of non-transaction query operations that use default write concerns. The metrics track usage of the cluster wide write concern (the global default write concern) and the implicit-default write concern. The sum of the values in opWriteConcernCounters.noneInfo should equal the value of opWriteConcernCounters.none.

The sum of the opWriteConcernCounters.delete equals opcounters.delete.

opcounters

opcounters : {
   insert : Long("<num>"),
   query : Long("<num>"),
   update : Long("<num>"),
   delete : Long("<num>"),
   getmore : Long("<num>"),
   command : Long("<num>"),
},

opcounters

A document that reports on database operations by type since the 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 opcounters treats operations that affect multiple documents, such as bulk insert or multi-update operations, as a single operation. See metrics.document for more granular document-level operation tracking.

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

opcounters.insert

The total number of insert operations received since the mongod instance last started.

opcounters.query

The total number of queries received since the mongod instance last started. Starting in MongoDB 7.1, aggregations count as query operations and increment this value.

opcounters.update

The total number of update operations received since the mongod instance last started.

opcounters.delete

The total number of delete operations since the mongod instance last started.

opcounters.getmore

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

opcounters.command

The total number of commands issued to the database since the mongod instance last started.

opcounters.command counts all commands except the following:

• insert
• update
• delete
• aggregate

opcounters.deprecated

opQuery counts the number of requests for opcodes that are deprecated in MongoDB 5.0 but are temporarily supported. This section only appears in the db.serverStatus() output when a deprecated opcode has been used.

The counter is reset when mongod starts.

deprecated: {
   opQuery: Long("<num>"),
}

opcountersRepl

The returned opcountersRepl.* values are type NumberLong.

opcountersRepl : {
   insert : Long("<num>"),
   query : Long("<num>"),
   update : Long("<num>"),
   delete : Long("<num>"),
   getmore : Long("<num>"),
   command : Long("<num>"),
},

opcountersRepl

A document that reports on database replication operations by type since the 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 opcounters values because of how MongoDB serializes operations during replication. See 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.

The returned opcountersRepl.* values are type NumberLong.

opcountersRepl.insert

The total number of replicated insert operations since the mongod instance last started.

The returned opcountersRepl.* values are type NumberLong.

opcountersRepl.query

The total number of replicated queries since the mongod instance last started.

The returned opcountersRepl.* values are type NumberLong.

opcountersRepl.update

The total number of replicated update operations since the mongod instance last started.

The returned opcountersRepl.* values are type NumberLong.

opcountersRepl.delete

The total number of replicated delete operations since the mongod instance last started.

The returned opcountersRepl.* values are type NumberLong.

opcountersRepl.getmore

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

The returned opcountersRepl.* values are type NumberLong.

opcountersRepl.command

The total number of replicated commands issued to the database since the mongod instance last started.

The returned opcountersRepl.* values are type NumberLong.

oplogTruncation

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

oplogTruncation

A document that reports on oplog truncations.

The field only appears when the current instance is a member of a replica set and uses either the WiredTiger Storage Engine or In-Memory Storage Engine for Self-Managed Deployments.

Available in the WiredTiger Storage Engine.

oplogTruncation.totalTimeProcessingMicros

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

totalTimeProcessingMicros is only meaningful if the mongod instance started on existing data files (i.e. not meaningful for In-Memory Storage Engine for Self-Managed Deployments).

See oplogTruncation.processingMethod

Available in the WiredTiger Storage Engine.

oplogTruncation.processingMethod

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

processingMethod is only meaningful if the mongod instance started on existing data files (i.e. not meaningful for In-Memory Storage Engine for Self-Managed Deployments).

Available in the WiredTiger Storage Engine.

oplogTruncation.oplogMinRetentionHours

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

Only visible if the mongod is a member of a replica set and:

• The mongod was started with the --oplogMinRetentionHours command line option or the storage.oplogMinRetentionHours configuration file option,

  or

• The minimum retention period was configured after startup using replSetResizeOplog.

oplogTruncation.totalTimeTruncatingMicros

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

Available in the WiredTiger Storage Engine.

oplogTruncation.truncateCount

The cumulative number of oplog truncations.

Available in the WiredTiger Storage Engine.

planCache

planCache : {
   totalQueryShapes : Long("<num>"),
   totalSizeEstimateBytes : Long("<num>"),
   classic : {
      hits : Long("<num>"),
      misses : Long("<num>"),
      replanned : Long("<num>"),
      replanned_plan_is_cached_plan : Long("<num>"),
      skipped : Long("<num>")
   },
   sbe : {
      hits : Long("<num>"),
      misses: Long("<num>"),
      replanned : Long("<num>"),
      replanned_plan_is_cached_plan : Long("<num>"),
      skipped : Long("<num>")
   }
}

planCache

A document that reports query plan cache statistics.

planCache.totalQueryShapes

Approximate number of plan cache query shapes

Prior to version 7.2, information on the number of plan cache query shapes was stored in the query.planCacheTotalQueryShapes field.

New in version 7.2.在版本7.2中新增。

planCache.totalSizeEstimateBytes

Total size of the plan cache in bytes.

Prior to version 7.2, information on the plan cache size was stored in the query.planCacheTotalSizeEstimateBytes field.

New in version 7.2.在版本7.2中新增。

planCache.classic.hits

Number of classic execution engine query plans found in the query cache and reused to avoid the query planning phase.

planCache.classic.misses

Number of classic execution engine query plans which were not found in the query cache and went through the query planning phase.

planCache.classic.replanned

Number of classic execution engine query plans that were discarded and re-optimized.

New in version 8.0.在版本8.0中新增。 (Also available in 7.0.22)

planCache.classic.replanned_plan_is_cached_plan

Number of times the server performed a replan operation for the classic execution engine that produced a plan identical to one already in the query cache.

New in version 8.2.在版本8.2中新增。

planCache.classic.skipped

Number of classic execution engine query plans that were not found in the query cache because the query is ineligible for caching.

New in version 7.3.在版本7.3中新增。

planCache.sbe.hits

Number of slot-based execution engine query plans found in the query cache and reused to avoid the query planning phase.

planCache.sbe.misses

Number of slot-based execution engine plans which were not found in the query cache and went through the query planning phase.

planCache.sbe.replanned

Number of slot-based execution engine query plans that were discarded and re-optimized.

New in version 8.0.在版本8.0中新增。 (Also available in 7.0.22)

planCache.sbe.replanned_plan_is_cached_plan

Number of times the server performed a replan operation for the slot-based execution engine that produced a plan identical to one already in the query cache.

New in version 8.2.在版本8.2中新增。

planCache.sbe.skipped

Number of slot-based execution engine query plans that were not found in the query cache because the query is ineligible for caching.

New in version 7.3.在版本7.3中新增。

profiler

profiler: {
   totalWrites: <integer>,
   activeWriters: <integer>
}

profiler.totalWrites

Total number of writes to profile collections on all databases.

profiler.activeWriters

The instantaneous number of operations writing to a profile collection on all databases.

queryStats

queryStats: {
   numEvicted: Long("<num>"),
   numRateLimitedRequests: Long("<num>"),
   queryStatsStoreSizeEstimateBytes: Long("<num>"),
   numQueryStatsStoreWriteErrors: Long("<num>"),
   numHmacApplicationErrors: Long("<num>")
},

queryStats

A document that contains metrics for the $queryStats aggregation stage.

queryStats.numEvicted

Number of queries that the $queryStats virtual collection has evicted due to space contraints.

queryStats.numRateLimitedRequests

Number of times that query stats were not recorded for a query due to rate limiting.

queryStats.queryStatsStoreSizeEstimateBytes

Current estimated size of objects in the $queryStats virtual collection.

queryStats.numQueryStatsStoreWriteErrors

Number of times this MongoDB process failed to store a new query stats key. Generally, these failures happen when the $queryStats virtual collection runs out of space.

queryStats.numHmacApplicationErrors

Number of times this MongoDB process failed to compute a one-way tokenized query stats key when $queryStats was called with the transformIdentifiers option.

queryAnalyzers

queryAnalyzers: {
  activeCollections: <integer>,
  totalCollections: <integer>,
  totalSampledReadsCount: <integer>,
  totalSampledWritesCount: <integer>,
  totalSampledReadsBytes: <integer>,
  totalSampledWritesBytes: <integer>
}

queryAnalyzers.activeCollections

Number of collections the query analyzer actively samples.

queryAnalyzers.totalCollections

Total number of sampled collections.

queryAnalyzers.totalSampledReadsCount

Total number of sampled read queries.

queryAnalyzers.totalSampledWritesCount

Total number of sampled write queries.

queryAnalyzers.totalSampledReadsBytes

Total size of sampled read queries, in bytes. This metric is only available when running serverStatus on mongod.

queryAnalyzers.totalSampledWritesBytes

Total size of sampled write queries, in bytes. This metric is only available when running serverStatus on mongod.

queues

As an operation proceeds through its stages, it may enter a queue if the number of concurrent operations at the current stage exceeds a maximum threshold. This prevents excessive resource contention and provides observability into the state of the database.

queues: {
   execution: {
      write: {
         out: Long("<num>"),
         available: Long("<num>"),
         totalTickets: Long("<num>"),
         exempt: {
            addedToQueue: Long("<num>"),
            removedFromQueue: Long("<num>"),
            queueLength: Long("<num>"),
            startedProcessing: Long("<num>"),
            processing: Long("<num>"),
            finishedProcessing: Long("<num>"),
            totalTimeProcessingMicros: Long("<num>"),
            canceled: Long("<num>"),
            newAdmissions: Long("<num>"),
            totalTimeQueuedMicros: Long("<num>")
         },
         normalPriority: {
            addedToQueue: Long("<num>"),
            removedFromQueue: Long("<num>"),
            queueLength: Long("<num>"),
            startedProcessing: Long("<num>"),
            processing: Long("<num>"),
            finishedProcessing: Long("<num>"),
            totalTimeProcessingMicros: Long("<num>"),
            canceled: Long("<num>"),
            newAdmissions: Long("<num>"),
            totalTimeQueuedMicros: Long("<num>")
         }
      },
      read: {
         out: Long("<num>"),
         available: Long("<num>"),
         totalTickets: Long("<num>"),
         exempt: {
            addedToQueue: Long("<num>"),
            removedFromQueue: Long("<num>"),
            queueLength: Long("<num>"),
            startedProcessing: Long("<num>"),
            processing: Long("<num>"),
            finishedProcessing: Long("<num>"),
            totalTimeProcessingMicros: Long("<num>"),
            canceled: Long("<num>"),
            newAdmissions: Long("<num>"),
            totalTimeQueuedMicros: Long("<num>")
         },
         normalPriority: {
            addedToQueue: Long("<num>"),
            removedFromQueue: Long("<num>"),
            queueLength: Long("<num>"),
            startedProcessing: Long("<num>"),
            processing: Long("<num>"),
            finishedProcessing: Long("<num>"),
            totalTimeProcessingMicros: Long("<num>"),
            canceled: Long("<num>"),
            newAdmissions: Long("<num>"),
            totalTimeQueuedMicros: Long("<num>")
         }
      },
      monitor: {
         timesDecreased: Long("<num>"),
         timesIncreased: Long("<num>"),
         totalAmountDecreased: Long("<num>"),
         totalAmountIncreased: Long("<num>"),
         resizeDurationMicros: Long("<num>")
      }
   },
   ingress: {
      out: Long("<num>"),
      available: Long("<num>"),
      totalTickets: Long("<num>"),
      exempt: {
         addedToQueue: Long("<num>"),
         removedFromQueue: Long("<num>"),
         queueLength: Long("<num>"),
         startedProcessing: Long("<num>"),
         processing: Long("<num>"),
         finishedProcessing: Long("<num>"),
         totalTimeProcessingMicros: Long("<num>"),
         canceled: Long("<num>"),
         newAdmissions: Long("<num>"),
         totalTimeQueuedMicros: Long("<num>")
      },
      normalPriority: {
         addedToQueue: Long("<num>"),
         removedFromQueue: Long("<num>"),
         queueLength: Long("<num>"),
         startedProcessing: Long("<num>"),
         processing: Long("<num>"),
         finishedProcessing: Long("<num>"),
         totalTimeProcessingMicros: Long("<num>"),
         canceled: Long("<num>"),
         newAdmissions: Long("<num>"),
         totalTimeQueuedMicros: Long("<num>")
      }
   },
   ingressSessionEstablishment: { // Added in MongoDB 8.2
      "addedToQueue": Long("<num>"),
      "removedFromQueue": Long("<num>"),
      "interruptedInQueue": Long("<num>")
      "rejectedAdmissions": Long("<num>"),
      "exemptedAdmissions": Long("<num>"),
      "successfulAdmissions": Long("<num>"),
      "attemptedAdmissions": Long("<num>"),
      "averageTimeQueuedMicros": Long("<num>"),
      "totalAvailableTokens": Long("<num>")
   }
}

queues.execution

New in version 8.0.在版本8.0中新增。

A document that returns monitoring and queue information for operations waiting to be scheduled for execution within the storage layer (concurrent transactions).

These settings are MongoDB-specific. To change the settings for concurrent reads and write transactions (read and write tickets), see storageEngineConcurrentReadTransactions and storageEngineConcurrentWriteTransactions.

Important

Starting in version 7.0, MongoDB uses a default algorithm to dynamically adjust the maximum number of concurrent storage engine transactions (including both read and write tickets) to optimize database throughput during overload.

The following table summarizes how to identify overload scenarios for MongoDB post-7.0 and for earlier releases:

Version	Diagnosing Overload Scenarios
7.0 and later	A large number of queued operations that persists for a prolonged period of time likely indicates an overload. A concurrent storage engine transaction (ticket) availability of 0 for a prolonged period of time does not indicate an overload.
6.0 and earlier	A large number of queued operations that persists for a prolonged period of time likely indicates an overload. A concurrent storage engine transaction (ticket) availibility of 0 for a prolonged period of time likely indicates an overload.

queues.execution.write

A document that returns Queue Information for concurrent read transactions (read tickets) allowed into the WiredTiger storage engine.

queues.execution.read

A document that returns Queue Information for concurrent write transactions (write tickets) allowed into the WiredTiger storage engine.

queues.execution.monitor

A document that returns monitoring metrics for adjustments that the system has made to the number of allowed concurrent transactions (tickets).

queues.execution.monitor.timesDecreased

The number of times the queue size was decreased.

queues.execution.monitor.timesIncreased

The number of times the queue size was increased.

queues.execution.monitor.totalAmountDecreased

The total amount of operations the queue decreased by.

queues.execution.monitor.totalAmountIncreased

The total number of operations the queue increased by.

queues.execution.monitor.resizeDurationMicros

The cumulative time in milliseconds that the system spent resizing the queue.

queues.ingress

New in version 8.0.在版本8.0中新增。

A document that returns Queue Information for ingress admission control. Use these values to protect and mitigate against resource overload by limiting the number of operations waiting for entry to the database from the network.

The maximum number of allowed concurrent operations is constrained by ingressAdmissionControllerTicketPoolSize.

queues.ingressSessionEstablishment

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

A document that contains information about the ingress session establishment queue. This includes metrics related to connections established and processed through the connection establishment rate limiter.

queues.ingressSessionEstablishment.addedToQueue

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

The number of incoming connections that the server adds to the ingress session establishment queue. This metric tracks connections that are processed through the rate limiter queue when the rate limiter is enabled.

queues.ingressSessionEstablishment.removedFromQueue

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

The number of incoming connections that the server removes from the ingress session establishment queue after acquiring a connection establishment token. This metric tracks connections that have completed their wait in the rate limiter queue.

queues.ingressSessionEstablishment.interruptedInQueue

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

The number of incoming connections that halt while waiting in the queue, typically due to client disconnects or server shutdown.

queues.ingressSessionEstablishment.rejectedAdmissions

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

The number of incoming connection attempts that the server rejects because the queue depth exceeded the ingressConnectionEstablishmentMaxQueueDepth limit. When this happens, the server immediately closes the connection rather than queuing it.

queues.ingressSessionEstablishment.exemptedAdmissions

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

The number of incoming connection attempts that bypass the rate limiter due to being on the ingressConnectionEstablishmentRateLimiterBypass list. Connections from IP addresses or CIDR ranges specified in ingressConnectionEstablishmentRateLimiterBypass are not subject to rate limiting.

queues.ingressSessionEstablishment.successfulAdmissions

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

The total number of incoming connection attempts that the rate limiter successfully processes, either immediately or after waiting in the queue.

queues.ingressSessionEstablishment.attemptedAdmissions

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

The total number of incoming connection attempts on the rate limiter.

queues.ingressSessionEstablishment.averageTimeQueuedMicros

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

The average time in microseconds that connections spend waiting in the queue before the server processes them. This metric uses an exponentially-weighted moving average formula and can be used to tune the ingressConnectionEstablishmentMaxQueueDepth. The value roughly equals (maxQueueDepth / establishRatePerSec) * 1e6.

queues.ingressSessionEstablishment.totalAvailableTokens

New in version 8.2.在版本8.2中新增。 (also available in 8.1.1, 8.0.12, and 7.0.23)

The current number of available tokens in the token bucket. This represents the capacity for immediately processing new connections without queuing. When this value is 0, new connections must wait in the queue, or are rejected if the queue is full.

Queue Information

out: Long("<num>"),
available: Long("<num>"),
totalTickets: Long("<num>"),
exempt: {
   addedToQueue: Long("<num>"),
   removedFromQueue: Long("<num>"),
   queueLength: Long("<num>"),
   startedProcessing: Long("<num>"),
   processing: Long("<num>"),
   finishedProcessing: Long("<num>"),
   totalTimeProcessingMicros: Long("<num>"),
   canceled: Long("<num>"),
   newAdmissions: Long("<num>"),
   totalTimeQueuedMicros: Long("<num>")
},
normalPriority: {
   addedToQueue: Long("<num>"),
   removedFromQueue: Long("<num>"),
   queueLength: Long("<num>"),
   startedProcessing: Long("<num>"),
   processing: Long("<num>"),
   finishedProcessing: Long("<num>"),
   totalTimeProcessingMicros: Long("<num>"),
   canceled: Long("<num>"),
   newAdmissions: Long("<num>"),
   totalTimeQueuedMicros: Long("<num>")
}

out

The number of currently held tickets.

available

The number of available tickets.

totalTickets

The size of the ticket pool.

exempt

A document that returns metrics for operations exempt from the queue.

exempt.startedProcessing

The total number of operations that acquired an admission ticket.

exempt.processing

The total number of operations that are currently being processed.

exempt.finishedProcessing

The total number of operations that released their admission ticket.

exempt.totalTimeProcessingMicros

The total time operations held their admission tickets.

exempt.canceled

The total number of operations that timed out in the queue.

exempt.newAdmissions

The total number of new admissions to the queue.

exempt.totalTimeQueuedMicros

The total time operations spent waiting on the queue.

normalPriority

A document that returns metrics for operations subject to the queue.

normalPriority.addedToQueue

The total number of operations added to the queue.

normalPriority.removedFromQueue

The total number of operations removed from the queue.

normalPriority.queueLength

The total number of operations in the queue.

normalPriority.startedProcessing

The total number of operations that acquired an admission ticket.

normalPriority.processing

The total number of operations that are currently being processed.

normalPriority.finishedProcessing

The total number of operations that released their admission ticket.

normalPriority.totalTimeProcessingMicros

The total time operations held their admission tickets.

normalPriority.canceled

The total number of operations that timed out in the queue.

normalPriority.newAdmissions

The total number of new admissions to the queue.

normalPriority.totalTimeQueuedMicros

The total time operations spent waiting on the queue.

querySettings

querySettings: {
  count: <num>,
  rejectCount: <num>,
  size: <num>
}

querySettings

Document with configuration counts and usage for query settings.

Starting in MongoDB 8.0, use query settings instead of adding index filters. Index filters are deprecated starting in MongoDB 8.0.

Query settings have more functionality than index filters. Also, index filters aren't persistent and you cannot easily create index filters for all cluster nodes. To add query settings and explore examples, see setQuerySettings.

querySettings.count

Total number of query settings.

querySettings.rejectCount

Total number of query settings that have the reject field set to true. To set the reject field, use setQuerySettings.

querySettings.size

Total size in bytes for query settings.

readConcernCounters

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

readConcernCounters

A document that reports on the read concern level specified by query operations. This document contains the readConcernCounters.nonTransactionOps and readConcernCounters.transactionOps documents.