Merge branch 'develop' into CEXT-3774-release

Author: keharper

src/pages/_images/events/event-list.png

@@ -16,9 +16,9 @@ Adobe Commerce is capable of emitting thousands of different observer and plugin
 
 You can use the Commerce Admin or the command line to find supported events and their payloads:
 
-*  In the Admin, select **System** > Events > **Events** to display the _Event list_ page.
+*  In the Admin, select **System** > Events > **Events List** to display the _Events list_ page.
 
-   ![Event list page](../_images/events/event-list.png)
+   ![Events list page](../_images/events/event-list.png)
 
    The left navigation contains a list of enabled modules on your system. Click on a module name to display a list of supported events. When you select an event, the main panel of the Admin displays the event's payload.
 

src/pages/_images/events/event-status-grid.png

@@ -12,8 +12,12 @@ This topic describes how to resolve frequently encountered issues with Adobe I/O
 
 ## Events are not showing in App Builder event registration
 
-If Commerce is correctly [configured](configure-commerce.md), but triggered events aren't being received, check if the events exist in the Commerce `event_data` table.
-The `event_data` table temporarily stores events before transforming them into Adobe I/O events. The table contains a status column that can have the following values:
+If Commerce is correctly [configured](configure-commerce.md), but triggered events aren't being received, check the the _Events Status_ grid, located at **System** > Events > **Events Status** in the Commerce Admin, to view the status of triggered events that are present in the Commerce `event_data` database table.
+
+![Events Status grid](../_images/events/event-status-grid.png)
+
+You can perform additional troubleshooting by retrieving the contents of the `event_data` table, which contains information that is not displayed in the grid.
+This table temporarily stores events before transforming them into Adobe I/O events. The table contains a status column that can have the following values:
 
 Status ID | Status
 --- | ---
@@ -26,11 +30,11 @@ You can use the following SQL query to select all events from the `event_data` t
 
 `SELECT * FROM event_data`
 
-Use the query results to determine the next troubleshooting step.
+Use the SQL query results or the content of the _Events Status_ grid to determine the next troubleshooting step.
 
-### The table is empty
+### The table or grid is empty
 
-If the `event_data` table is empty, use the following procedure to diagnose the problem:
+If the `event_data` table or the _Events Status_ grid is empty, use the following procedure to diagnose the problem:
 
 1. Run `bin/magento events:list` to ensure that you have subscribed events.
 
@@ -48,14 +52,14 @@ If the `event_data` table is empty, use the following procedure to diagnose the
          ENABLE_EVENTING: true
    ```
 
-### The event status is `0`
+### The event status is `0` or `Waiting`
 
-Events are sent by crons. If the status of an event in the `event_data` is still `0` after a long period, then the crons are not configured correctly.
+Events are sent by crons. If the status of an event is still `0` in the `event_data` table or `Waiting` in the _Events Status_ grid after a long period, then the crons are not configured correctly.
 In a Cloud environment, check the logs. Cron execution might have been killed due to lack of space in the environment or other reasons.
 
-### The event status is `2`
+### The event status is `2` or `Failure`
 
-The event status `2` indicates there was an error during transmission. Additional information can be found in the `info` column of the table or in the `system.log` file.
+An event status of `2` in the `event_data` table, or `Failure` in the _Events Status_ grid, indicates there was an error during transmission. Additional information can be found in the `info` column of the table or in the `system.log` file.
 The following CLI command can show only logs related to the event batch sending.
 
 ```bash

src/pages/_images/webhooks/database-logging-configuration.png

@@ -35,6 +35,8 @@ You will typically need to send authorization tokens and other connection parame
 </hook>
 ```
 
+The `x-adobe-commerce-request-id` is added automatically to each request and is used to track the request in the system. You can filter logs by this ID to find all logs related to a specific request.
+
 This example defines two headers:
 
 Name | Value

src/pages/_images/webhooks/database-logging.png

@@ -27,7 +27,7 @@ The resolution of a remote call also determines whether you should implement a w
 
 Use these guidelines to develop your own webhooks:
 
-1. Identify the Adobe Commerce event that triggers a webhook. Adobe Commerce merchants can browse the available events from the Admin by selecting **System** > Events > **Events** to display the Event list page.
+1. Identify the Adobe Commerce event that triggers a webhook. Adobe Commerce merchants can browse the available events from the Admin by selecting **System** > Events > **Events** to display the Events list page.
 
 1. Understand the default payload of the corresponding webhook by running the [`bin/magento webhooks:info` command](commands.md#display-the-payload-of-a-webhook).
 

src/pages/events/module-development.md

@@ -200,4 +200,22 @@ An optional hook was executed with a response code other than 2xx within the sof
 A required hook was executed with a response code other than 2xx within the soft and hard time limits. | Add error log entry<br/>Throw an exception
 An optional hook is aborted due to reaching the hard timeout limit. | Add error log entry
 A required hook is aborted due to reaching the hard timeout limit. | Add error log entry<br/>Throw an exception
-The execution time of hook exceeds the soft timeout limit. |   Add a notice to the error log
+The execution time of hook exceeds the soft timeout limit. | Add a notice to the error log
+
+## Database logging
+
+You can enable database logging for debugging webhooks from the Admin. You should not enable database logging in production environments, as it can affect the performance.
+
+To enable database logging, navigate to **Stores** > Settings > **Configuration** > **Adobe Services** > **Webhooks** > **Database logging configuration** and set the **Enabled** option to **Yes**.
+
+![Webhooks database logging configuration](../_images/webhooks/database-logging-configuration.png)
+
+You can configure the minimum log level to store logs in the database and log retention time. The available log levels are `DEBUG`, `INFO`, `WARNING`, and `ERROR`.
+
+The logs are cleared once per day based on the retention time.
+
+When database logging is enabled, the webhook logs are stored in the `webhook_log` table. To check logs in the Admin, navigate to **System** > **Webhooks** > **Webhook Logs**.
+
+![Webhooks database logging](../_images/webhooks/database-logging.png)
+
+You can filter logs by multiple fields, such as webhook method, type, hook name, and request ID.