DOCS-14119 Track maxConns

source/reference/command/serverStatus.txt

@@ -219,13 +219,13 @@ asserts
    A document that reports on the number of assertions raised since the
    MongoDB process started. While assert errors are typically uncommon,
    if there are non-zero values for the :data:`asserts`, you should
-   check the log file for more information. In many cases, these errors
-   are trivial, but are worth investigating.
+   examine the log file for more information. In many cases, these
+   errors are trivial, but are worth investigating.
 
 .. serverstatus:: asserts.regular
 
    The number of regular assertions raised since the MongoDB process
-   started. Check the log file for more information about these
+   started. Examine the log file for more information about these
    messages.
 
 .. serverstatus:: asserts.warning
@@ -240,7 +240,7 @@ asserts
 .. serverstatus:: asserts.msg
 
    The number of message assertions raised since the MongoDB process
-   started. Check the log file for more information about these
+   started. Examine the log file for more information about these
    messages.
 
 .. serverstatus:: asserts.user
@@ -249,7 +249,7 @@ asserts
    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. Check the MongoDB log for more information.
+   or deployment. Examine the MongoDB log for more information.
 
 .. serverstatus:: asserts.rollovers
 
@@ -271,6 +271,7 @@ connections
       "available" : <num>,
       "totalCreated" : <num>,
       "active" : <num>,
+      "threaded" : <num>,
       "exhaustIsMaster" : <num>,
       "awaitingTopologyChanges" : <num>
    },
@@ -284,7 +285,7 @@ connections
 .. serverstatus:: connections.current
 
    The number of incoming connections from clients to the database
-   server . This number includes the current shell session. Consider
+   server. This number includes the current shell session. Consider
    the value of :serverstatus:`connections.available` to add more
    context to this datum.
 
@@ -313,6 +314,13 @@ connections
 
    .. versionadded:: 4.0.7
 
+.. serverstatus:: connections.threaded
+
+   The number of incoming connections from clients that are assigned
+   to threads that service client requests.
+
+   .. versionadded:: 5.0
+
 .. serverstatus:: connections.exhaustIsMaster
 
    The number of connections whose last request was an
@@ -358,8 +366,7 @@ information.
 
 .. serverstatus:: defaultRWConcern
 
-   The last known global default read or write concern 
-   settings.
+   The last known global default read or write concern settings.
 
    .. versionadded:: 4.4
 
@@ -429,12 +436,12 @@ information.
 
 .. serverstatus:: defaultRWConcern.updateWallClockTime
 
-   The wall clock time when the instance last updated its copy of 
-   any global read or write concern settings. If the 
-   :serverstatus:`defaultRWConcern.defaultReadConcern` and 
-   :serverstatus:`defaultRWConcern.defaultWriteConcern` fields are 
-   absent, this field indicates the time when the 
-   defaults were last unset.
+   The wall clock time when the instance last updated its copy of any
+   global read or write concern settings. If the
+   :serverstatus:`defaultRWConcern.defaultReadConcern` and
+   :serverstatus:`defaultRWConcern.defaultWriteConcern` fields are
+   absent, this field indicates the time when the defaults were last
+   unset.
 
    .. versionadded:: 4.4
 
@@ -520,7 +527,7 @@ primary:
 .. serverstatus:: electionMetrics.catchUpTakeover
 
    Metrics on elections called by the :binary:`~bin.mongod` instance
-   because it is more-up-to-date than the primary.
+   because it is more current than the primary.
 
    The :serverstatus:`~electionMetrics.catchUpTakeover` includes both the number of
    elections called and the number of elections that succeeded.
@@ -556,7 +563,7 @@ primary:
 .. serverstatus:: electionMetrics.numStepDownsCausedByHigherTerm
 
    Number of times the :binary:`~bin.mongod` instance stepped down
-   because it saw a higher term (i.e. other member/members have
+   because it saw a higher term (specifically, other member(s)
    participated in additional elections).
 
    *Available starting in 4.2.1 (and 4.0.13)*
@@ -581,7 +588,7 @@ primary:
 
    Number of times the :binary:`~bin.mongod` instance as the
    newly-elected primary concluded its catchup process because it was
-   already caught up when elected
+   already caught up when elected.
 
    *Available starting in 4.2.1 (and 4.0.13)*
 
@@ -609,9 +616,9 @@ primary:
 
 .. serverstatus:: electionMetrics.numCatchUpsFailedWithNewTerm
 
-   Number of times the newly-elected primary's catchup process
-   concluded because another member(s) had a higher term (i.e. other
-   member/members have participated in additional elections).
+   Number of times the newly-elected primary's catchup process concluded
+   because another member(s) had a higher term (specifically, other
+   member(s) participated in additional elections).
 
    *Available starting in 4.2.1 (and 4.0.13)*
 
@@ -647,8 +654,8 @@ extra_info
 
 .. serverstatus:: extra_info
 
-   A document that provides additional information regarding the
-   underlying system.
+   A document that provides additional information about the underlying
+   system.
 
 .. serverstatus:: extra_info.note
 
@@ -2871,7 +2878,7 @@ shardedIndexConsistency
    collection does not have the exact same indexes (including the index
    options) on each shard that contains chunks for the collection.
 
-   To check if a sharded collection has inconsistent indexes, see
+   To investigate if a sharded collection has inconsistent indexes, see
    :ref:`manage-indexes-find-inconsistent-indexes`.
 
    The returned metrics are meaningful only when run on the primary of
@@ -4697,8 +4704,8 @@ metrics
 
 .. serverstatus:: metrics.storage.freelist.search.bucketExhausted
 
-   The number of times that :binary:`~bin.mongod` has checked the free list
-   without finding a suitably large record allocation.
+   The number of times that :binary:`~bin.mongod` has examined the free
+   list without finding a suitably large record allocation.
 
 .. serverstatus:: metrics.storage.freelist.search.requests
 
@@ -4800,8 +4807,9 @@ watchdog
 
 .. serverstatus:: watchdog.monitorGeneration
 
-   The number of times the status of all filesystems used by :binary:`~bin.mongod`
-   has been checked. This is incremented once every ``monitoringPeriod``.
+   The number of times the status of all filesystems used by
+   :binary:`~bin.mongod` has been examined. This is incremented once
+   every ``monitoringPeriod``.
 
 .. serverstatus:: watchdog.monitorPeriod
 

source/release-notes/5.0.txt

@@ -229,6 +229,13 @@ output:
                (:serverstatus:`readConcernCounters` replaces
                :serverstatus:`opReadConcernCounters`)
 
+   Number of Threaded Connections
+      .. list-table::
+
+         * - | :serverstatus:`connections.threaded`, which reports the
+               number of incoming connections from clients that are
+               assigned to threads that service client requests
+
 Additional ``dbStats`` Free Space Statistics
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~