DOCS-14042 change field to notPrimaryLegacyUnacknowledgedWrites

Author: mungitoperrito

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

@@ -15,6 +15,14 @@ content: |
 ref: _serverStatus-output-changes
 content: |
 
+  - Starting in MongoDB 4.4.3, {{operationName}}:
+
+    - Changed ``notMasterLegacyUnacknowledgedWrites`` to 
+      :serverstatus:`~metrics.repl.network.notPrimaryLegacyUnacknowledgedWrites`
+
+    - Changed ``notMasterUnacknowledgedWrites`` to
+      :serverstatus:`~metrics.repl.network.notPrimaryUnacknowledgedWrites` 
+
   - Starting in MongoDB 4.4.2, {{operationName}}:
 
     - Added new metrics to track use of Aggregation Pipeline methods:

source/reference/command/serverStatus.txt

@@ -4006,8 +4006,8 @@ metrics
                "num" : <num>,
                "totalMillis" : <num>
             },
-            "notMasterLegacyUnacknowledgedWrites" : <NumberLong>,
             "notPrimaryUnacknowledgedWrites" : <NumberLong>,
+            "notPrimaryLegacyUnacknowledgedWrites" : <NumberLong>,
             "oplogGetMoresProcessed" : {
                "num" : <NumberLong>,
                "totalMillis" : <NumberLong>
@@ -4399,12 +4399,15 @@ metrics
 
    .. versionadded:: 4.4
 
-.. serverstatus:: metrics.repl.network.notMasterLegacyUnacknowledgedWrites
+.. serverstatus:: metrics.repl.network.notPrimaryLegacyUnacknowledgedWrites
 
    The number of unacknowledged (``w: 0``) legacy write operations (see
    :ref:`wp-request-opcodes`) that failed because the current
    :binary:`~bin.mongod` is not in :replstate:`PRIMARY` state.
 
+   This field name was changed in MongoDB 4.4.3. Previously, this field
+   was named ``notMasterLegacyUnacknowledgedWrites``.
+
    .. versionadded:: 4.2
 
 .. serverstatus:: metrics.repl.network.notPrimaryUnacknowledgedWrites