DOCS-14181 audit dropCollection views

Author: mungitoperrito

source/reference/audit-message.txt

@@ -133,6 +133,7 @@ associated ``param`` details and the ``result`` values, if any.
 
 .. list-table::
    :header-rows: 1
+   :widths: 20 50 30
 
    * - ``atype``
 
@@ -244,10 +245,22 @@ associated ``param`` details and the ``result`` values, if any.
      - .. code-block:: none
           :copyable: false
 
-          { ns: <database>.<collection> }
+          {
+             ns: <database>.<collection>,
+             viewOn: <database>.<collection>,
+             pipeline: []
+          }
 
+       Starting in MongoDB v5.0 ``dropCollection`` adds an audit event
+       when a :ref:`view <3.4-reference-views>` is dropped as well as
+       when a :term:`collection` is dropped.  The ``pipeline``
+       parameter defines the ``view`` referenced in ``viewOn``.
 
-     - ``0`` - Success
+     - | ``0`` - Success
+       | ``26`` - ``NamespaceNotFound``
+
+       If the collection or view does not exist, the audit message shows
+       the return code as ``result: 26``. 
 
    * - :authaction:`dropDatabase`
 
@@ -256,7 +269,6 @@ associated ``param`` details and the ``result`` values, if any.
 
           { ns: <database> }
 
-
      - ``0`` - Success
 
    * - :authaction:`dropIndex`

source/release-notes/5.0.txt

@@ -241,6 +241,9 @@ Starting in MongoDB 5.0, ``startup`` and ``logout`` audit action types
 are available in 
 :doc:`System Event Audit Messages </reference/audit-message>`.
 
+The ``dropCollection`` audit action type (``atype``) adds an audit
+event when a :ref:`view <3.4-reference-views>` is dropped. 
+
 ``mongosShutdownTimeoutMillisForSignaledShutdown`` Parameter
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~