DOCS-14398 BACKPORT (#693)

Author: Dave

source/reference/database-profiler.txt

@@ -517,6 +517,34 @@ operation.
    For more information on lock modes, see
    :ref:`faq-concurrency-locking`.
 
+.. data:: system.profile.authorization
+
+   .. versionadded:: 5.0.0
+
+   The number of times the user cache is accessed for each operation.
+   These metrics are only displayed when an operation has accessed the
+   user cache at least once. 
+
+   These metrics are only available when :ref:`slow operation logging
+   <log-message-slow-ops>` or :ref:`database profiling <profiler>` is
+   enabled.
+   
+   :data:`system.profile.authorization` is not included in
+   :method:`db.currentOp()` output.
+
+   .. data:: system.profile.authorization.startedUserCacheAcquisitionAttempts
+
+      The number of times the operation tried to access the user cache.
+
+   .. data:: system.profile.authorization.completedUserCacheAcquisitionAttempts
+   
+      The number of times the operation retrieved user data from the
+      user cache.
+
+   .. data:: system.profile.authorization.userCacheWaitTimeMicros
+   
+      The total time the operation spent waiting for user cache
+      responses.
 
 .. data:: system.profile.storage
 

source/reference/log-messages.txt

@@ -1414,3 +1414,22 @@ The following example log message contains a ``resolvedViews`` field for
          }
       }
    }
+
+Authorization
+~~~~~~~~~~~~~
+
+Starting in MongoDB 5.0, :ref:`log messages for slow queries
+<log-message-slow-ops>` include a
+:data:`system.profile.authorization` section. These metrics help
+determine if a request is delayed because of contention for the user
+authorization cache. 
+
+.. code-block:: javascript
+   :copyable: false
+
+   "authorization": {
+      "startedUserCacheAcquisitionAttempts": 1,
+      "completedUserCacheAcquisitionAttempts": 1,
+      "userCacheWaitTimeMicros": 508
+    },
+