New Database Trigger Options

source/reference/config/triggers.txt

@@ -172,12 +172,9 @@ configuration files:
 
        .. note::
 
-          Regardless of this setting:
-
-          - ``INSERT`` and ``REPLACE`` events always include the
-            ``fullDocument`` field.
-
-          - ``DELETE`` events never include the ``fullDocument`` field.
+          Regardless of this setting, ``INSERT`` and ``REPLACE`` events always 
+          include the``fullDocument`` field. ``DELETE`` events never include the 
+          ``fullDocument`` field.
 
    * - | ``config.full_document_before_change``
        | Boolean

source/triggers/database-triggers.txt

@@ -10,8 +10,10 @@ Database Triggers
    :depth: 2
    :class: singlecol
 
-Database Triggers allow you to execute server-side logic whenever a
-document is added, updated, or removed in a linked MongoDB Atlas cluster.
+Database Triggers allow you to execute server-side logic whenever a database 
+change occurs on a linked MongoDB Atlas cluster. You can configure triggers on 
+individual collections, entire databases, and on an entire cluster.
+
 Unlike SQL data triggers, which run on the database server, triggers run
 on a serverless compute layer that scales independently of the database
 server. Triggers automatically call :ref:`Atlas Functions <functions>`
@@ -30,18 +32,6 @@ single change stream for each collection with at least one enabled
 trigger. If multiple triggers are enabled for a collection they all
 share the same change stream.
 
-You control which operations cause a trigger to fire as well as what
-happens when it does. For example, you can run a function whenever a
-specific field of a document is updated. The function can access the
-entire change event, so you always know what changed. You can also pass
-the change event to :ref:`AWS EventBridge <aws-eventbridge>` to handle
-the event outside of Atlas.
-
-Triggers support :manual:`$match
-</reference/operator/aggregation/match>` expressions to filter change
-events and :manual:`$project </reference/operator/aggregation/project>`
-expressions to limit the data included in each event.
-
 .. important:: Change Stream Limitations
 
    There are limits on the total number of change streams you can open
@@ -53,6 +43,27 @@ expressions to limit the data included in each event.
    <serverless-caveats>` or :ref:`{+adf-instance+}
    <data-federation-caveats>` because they do not support change streams.
 
+You control which operations cause a trigger to fire as well as what
+happens when it does. For example, you can run a function whenever a
+specific field of a document is updated. The function can access the
+entire change event, so you always know what changed. You can also pass
+the change event to :ref:`AWS EventBridge <aws-eventbridge>` to handle
+the event outside of Atlas.
+
+Triggers support :manual:`$match </reference/operator/aggregation/match>` 
+expressions to filter change events and :manual:`$project </reference/operator/aggregation/project>` 
+expressions to limit the data included in each event.
+
+.. _trigger-recursion:
+
+.. warning::
+
+   It is possible to configure triggers that cause other triggers to fire on the 
+   same collection, database, or cluster, resulting in recursion. Examples 
+   include a database trigger writing to a collection within the same 
+   database, or a cluster-level logger writing database logs to another database 
+   in the same cluster.
+
 .. _create-a-database-trigger:
 
 Create a Database Trigger
@@ -104,6 +115,9 @@ Configuration
 
 Database Triggers have the following configuration options:
 
+Trigger Details
+~~~~~~~~~~~~~~~
+
 .. list-table::
    :header-rows: 1
    :widths: 15 30
@@ -137,81 +151,144 @@ Database Triggers have the following configuration options:
 
        .. include:: /includes/trigger-event-ordering.rst
 
-Within the :guilabel:`Trigger Source Details` section, the following configuration 
-options are available:
-
-.. list-table::
-   :header-rows: 1
-   :widths: 15 30
-
-   * - Field
-     - Description
-
-   * - :guilabel:`Cluster Name`
-
-     - The name of the MongoDB Service that the Trigger is
-       associated with.
-
-   * - :guilabel:`Database Name`
+Trigger Source Details
+~~~~~~~~~~~~~~~~~~~~~~
 
-     - The MongoDB database that contains the watched
-       collection.
+Within the :guilabel:`Trigger Source Details` section, you first select the 
+:guilabel:`Source Type`, based on the level of granularity you want. Your 
+options are:
 
-   * - :guilabel:`Collection Name`
+- :guilabel:`Collection`, when a change occurs on a specified collection
+- :guilabel:`Database`, when a change occurs on any collection in a 
+  specified database
+- :guilabel:`Deployment`, when deployment changes occur on a specified 
+  cluster. If you select the Deployment source type, the following 
+  databases are **not watched** for changes:
 
-     - The name of the collection that the Trigger watches for
-       change events.
-
-   * - :guilabel:`Operation Type`
+  - The admin databases ``admin``, ``local``, and ``config``
+  - The sync databases ``__realm_sync`` and ``__realm_sync_<app_id>``
+
+Depending on which source type you are using, the additional options differ. The 
+following table describes these options.
 
-     - Checkboxes of :ref:`database operation types <database-event-operation-types>` 
-       that cause the Trigger to fire. Select the operation types you want the 
-       trigger to respond to.
+.. list-table::
+   :header-rows: 1
+   :widths: 15 30
 
-       .. warning::
+   * - Source Type
+     - Options
 
-          Update operations executed from MongoDB Compass or the MongoDB Atlas
-          Data Explorer fully replace the previous document. As a result,
-          update operations from these clients will generate **Replace**
-          change events rather than **Update** events.
+   * - :guilabel:`Collection`
+     - | 
 
-   * - :guilabel:`Full Document`
+       - :guilabel:`Cluster Name`. The name of the MongoDB cluster that the 
+           Trigger is associated with.
+
+       - :guilabel:`Database Name`. The MongoDB database that contains the watched
+         collection.
 
-     - If enabled, **Update** change events include the latest
-       :manual:`majority-committed </reference/read-concern-majority/>`
-       version of the modified document *after* the change was applied in
-       the ``fullDocument`` field.
+       - :guilabel:`Collection Name`. The MongoDB collection to watch.
 
-       .. note::
+       - :guilabel:`Operation Type`. The collection operation types 
+         that cause the Trigger to fire. Select the operation types you want the 
+         trigger to respond to. Options include:
+
+         - Create Collection
+         - Modify Collection
+         - Rename Collection
+         - Shard Collection
+         - Drop Collection
+
+         .. note::
+
+           Update operations executed from MongoDB Compass or the MongoDB Atlas
+           Data Explorer fully replace the previous document. As a result,
+           update operations from these clients will generate **Replace**
+           change events rather than **Update** events.
+
+       - :guilabel:`Full Document`. If enabled, **Update** change events include 
+         the latest :manual:`majority-committed </reference/read-concern-majority/>`
+         version of the modified document *after* the change was applied in
+         the ``fullDocument`` field.
+
+         .. note::
+
+            Regardless of this setting, **Insert** and **Replace** events always 
+            include the ``fullDocument`` field. **Delete** events never include 
+            the ``fullDocument`` field.
+
+       - :guilabel:`Document Preimage`. Disabled for Collection and Database 
+         sources to limit unnecessary watches on the cluster for a new 
+         collection being created.
 
-          Regardless of this setting:
-
-          - **Insert** and **Replace** events always include the
-            ``fullDocument`` field.
-
-          - **Delete** events never include the ``fullDocument`` field.
+   * - :guilabel:`Database`
+     - | 
 
-   * - :guilabel:`Document Preimage`
+       - :guilabel:`Cluster Name`. The name of the MongoDB cluster that the 
+         Trigger is associated with.
+
+       - :guilabel:`Database Name`. The MongoDB database to watch.
+
+       - :guilabel:`Operation Type`. The :ref:`database operation types 
+         <database-event-operation-types>` that cause the Trigger to fire. 
+         Select the operation types you want the  trigger to respond to. 
+         Options include:
+
+         - Create Collection
+         - Modify Collection
+         - Rename Collection
+         - Shard Collection
+         - Drop Collection
+
+         .. note::
+
+           Update operations executed from MongoDB Compass or the MongoDB Atlas
+           Data Explorer fully replace the previous document. As a result,
+           update operations from these clients will generate **Replace**
+           change events rather than **Update** events.
+
+       - :guilabel:`Full Document`. If enabled, **Update** change events include 
+         the latest :manual:`majority-committed </reference/read-concern-majority/>`
+         version of the modified document *after* the change was applied in
+         the ``fullDocument`` field.
+
+         .. note::
+
+            Regardless of this setting, **Insert** and **Replace** events always 
+            include the ``fullDocument`` field. **Delete** events never include 
+            the ``fullDocument`` field.
+
+       - :guilabel:`Document Preimage`. Disabled for Collection and Database 
+         sources to limit unnecessary watches on the cluster for a new 
+         collection being created.
 
-     - If enabled, change events include a copy of the modified document
-       from immediately *before* the change was applied in the
-       ``fullDocumentBeforeChange`` field. All change events except for
-       **Insert** events include the document preimage. Document preimages are 
-       supported on non-sharded Atlas clusters running MongoDB 4.4+, and 
-       on sharded Atlas clusters running MongoDB 5.3 and later.
+   * - :guilabel:`Deployment`
+     - | 
 
-       .. tip:: Performance Optimization
+       - :guilabel:`Cluster Name`. The name of the MongoDB cluster that the 
+         Trigger is associated with.
+
+       - :guilabel:`Operation Type`. The operation types 
+         that occur in the cluster that cause the Trigger to fire. Select the 
+         operation types you want the  trigger to respond to. Options include:
+
+         - Drop Database
+         - Create Collection
+         - Modify Collection
+         - Rename Collection
+         - Shard Collection
+         - Drop Collection
 
-          Preimages require additional storage overhead that may affect
-          performance. If you're not using preimages on a collection,
-          you should disable preimages. To learn more, see :ref:`Disable
-          Collection-Level Preimages
-          <database-triggers-disable-collection-level-preimages>`.
+Function
+~~~~~~~~
 
 Within the :guilabel:`Function` section, you choose what action is taken when 
 the trigger fires. You can choose to run a :ref:`function <functions>` or use 
 :ref:`AWS EventBridge <aws-eventbridge>`. 
 
+Advanced
+~~~~~~~~
+
 Within the :guilabel:`Advanced` section, the following **optional** configuration 
 options are available:
 
@@ -287,7 +364,6 @@ following operation types:
    * - **Replace**
      - Represents a new document that replaced a document in the collection.
 
-
 Database change event objects have the following general form:
 
 .. code-block:: json