DOCS-12403: reportOpWriteConcernCountersInServerStatus flag

Author: Kay Kim

source/includes/extracts-server-status-projection-base.yaml

@@ -22,7 +22,9 @@ content: |
 
     - :serverstatus:`opReadConcernCounters`
 
-    - :serverstatus:`opWriteConcernCounters`
+    - :serverstatus:`opWriteConcernCounters` (Requires
+      :parameter:`reportOpWriteConcernCountersInServerStatus` parameter
+      set to ``true``).
 
     - :serverstatus:`metrics.repl.apply.batchSize`
 

source/includes/extracts-server-status-projection.yaml

@@ -25,4 +25,12 @@ inherit:
   file: extracts-server-status-projection-base.yaml
 replacement:
   operationName: ":method:`db.serverStatus()`"
+---
+ref: serverStatus-opWriteConcernCounters
+content: |
+
+   Only available when
+   :parameter:`reportOpWriteConcernCountersInServerStatus` parameter is
+   set to ``true`` (``false`` by default).
+
 ...

source/reference/command/serverStatus.txt

@@ -762,8 +762,6 @@ opWriteConcernCounters
 
 .. serverstatus:: opWriteConcernCounters
 
-   .. versionadded:: 4.0.6
-
    A document that reports on the :doc:`write concerns
    </reference/write-concern>` specified by write operations to the
    :binary:`~bin.mongod` instance since it last started.
@@ -774,6 +772,10 @@ opWriteConcernCounters
    (``wtimeout``) of the write concerns does not affect the count. The
    count is incremented even if the operation times out.
 
+   .. note::
+
+      .. include:: /includes/extracts/serverStatus-opWriteConcernCounters.rst
+
 .. serverstatus:: opWriteConcernCounters.insert
 
    .. versionadded:: 4.0.6
@@ -782,6 +784,10 @@ opWriteConcernCounters
    by insert operations to the :binary:`~bin.mongod` instance since it
    last started:
 
+   .. note::
+
+      .. include:: /includes/extracts/serverStatus-opWriteConcernCounters.rst
+
    .. code-block:: javascript
 
       "insert" : {
@@ -837,6 +843,10 @@ opWriteConcernCounters
    by update operations to the :binary:`~bin.mongod` instance since it
    last started:
 
+   .. note::
+
+      .. include:: /includes/extracts/serverStatus-opWriteConcernCounters.rst
+
    .. code-block:: javascript
 
       "update" : {
@@ -891,6 +901,10 @@ opWriteConcernCounters
    by delete operations to the :binary:`~bin.mongod` instance since it
    last started:
 
+   .. note::
+
+      .. include:: /includes/extracts/serverStatus-opWriteConcernCounters.rst
+
    .. code-block:: javascript
 
       "delete" : {

source/reference/parameters.txt

@@ -735,6 +735,31 @@ General Parameters
 
    .. include:: /includes/fact-index-build-memory-limit.rst
 
+
+.. parameter:: reportOpWriteConcernCountersInServerStatus
+
+   .. versionadded:: 4.0.6
+
+   *Default*: false
+
+   A boolean flag that determines whether the
+   :method:`db.serverStatus()` method and :dbcommand:`serverStatus`
+   command return :serverstatus:`opWriteConcernCounters` information. [#perf]_ 
+
+   You can only set
+   :parameter:`reportOpWriteConcernCountersInServerStatus` during
+   startup in the config file or on the command line. For example:
+
+   .. code-block:: sh
+
+      mongod --setParameter reportOpWriteConcernCountersInServerStatus=true
+
+   .. [#perf]
+
+      Enabling :parameter:`reportOpWriteConcernCountersInServerStatus`
+      can have a negative performance impact; specificaly, when running
+      *without* TLS.
+
 .. parameter:: watchdogPeriodSeconds
 
    .. versionadded:: 3.6