Merge pull request AdobeDocs#283 from AdobeDocs/develop

Publish updates for eventing 1.9 and webhooks 1.6

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,6 +12,22 @@ These release notes describe the latest version of Adobe I/O Events for Adobe Co
 
 See [Update Adobe I/O Events for Adobe Commerce](installation.md#update-adobe-io-events-for-adobe-commerce) for upgrade instructions.
 
+## Version 1.9.0
+
+### Release date
+
+October 30, 2024
+
+### Enhancements
+
+* Added the **Events Status** grid to the Admin. This grid can be used to monitor the status of triggered events. <!--- CEXT-3593 -->
+
+* Added more detailed error messages for the **Execute Synchronization** and **Test Connection** buttons in the Adobe I/O Events configuration section of the Admin. <!--- CEXT-3594 -->
+
+* Added additional observer events to the list of supported event names. <!--CEXT-3671 -->
+
+* Renamed the **Events** item in the System menu of the Admin to **Events List**. <!--- CEXT-3658 -->
+
 ## Version 1.8.2
 
 ### Release date

src/pages/_images/webhooks/database-logging-configuration.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.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/events/module-development.md

@@ -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/release-notes.md

@@ -9,6 +9,26 @@ keywords:
 
 These release notes describe the latest version of Adobe Commerce Webhooks.
 
+## Version 1.6.0
+
+### Release date
+
+October 30, 2024
+
+### Enhancements
+
+* Added the **Webhooks Logs** grid to the Admin for viewing webhook execution information. <!--CEXT-3510 -->
+
+* Added additional debug logging related to webhooks response caching. <!--CEXT-3586 -->
+
+* Added additional observer events to the list of supported webhook event names. <!--CEXT-3671 -->
+
+* Updated copyrights in the generated module files. <!--- CEXT-3508 -->
+
+## Bug fix
+
+* Fixed an issue causing `null` values to be returned in some payloads output by the `webhooks:info` command <!--CEXT-3608 -->
+
 ## Version 1.5.1
 
 ### Release date