DOCS-889 changes to database profiler in 2.2

Author: Bob Grabar

source/reference/database-profiler.txt

@@ -118,6 +118,8 @@ operation.
 
 .. stats:: ntoreturn
 
+   .. versionchanged:: 2.2
+
    The number of documents the operation specified to return. For
    example, the :dbcommand:`profile` command would return one document
    (a results document) so the :status:`ntoreturn` value would be ``1``. The
@@ -129,8 +131,14 @@ operation.
    :method:`find() <db.collection.find()>` command with no limit
    specified.
 
+   In version 2.0, this information was provided for ``query`` and
+   ``command`` operations. In 2.2, this information is also provided for
+   ``getmore`` operations.
+
 .. stats:: ntoskip
 
+   .. versionadded:: 2.2
+
    The number of documents the :method:`skip() <cursor.skip()>` method
    specified to skip.
 
@@ -156,21 +164,29 @@ operation.
 
 .. stats:: nmoved
 
+   .. versionadded:: 2.2
+
    The number of documents moved on disk by the operation.
 
 .. stats:: nupdated
 
+   .. versionadded:: 2.2
+
    The number of documents updated by the operation.
 
 .. stats:: keyUpdates
 
+   .. versionadded:: 2.2
+
    The number of :doc:`index </indexes>` keys the update changed in
    the operation. Changing an index key
    carries a small performance cost because the database must remove the old
    key and inserts a new key into the B-tree index.
 
 .. stats:: numYield
 
+   .. versionadded:: 2.2
+
    The number of times the operation yielded to allow other operations
    to complete. Typically, operations yield when they need access to
    data that MongoDB has not yet fully read into memory. This allows
@@ -180,6 +196,8 @@ operation.
 
 .. stats:: lockStats
 
+   .. versionadded:: 2.2
+
    The time in microseconds the operation spent acquiring and holding
    locks. This field reports data for the following lock types: