Click Menu > IT and Integrations > Operational Console.

The Operational Console page opens with the last occurred events. Operational events are available for 10 days. The events are tracked in the UTC time zone and rendered in the user’s selected time zone.

Click the image to enlarge.

Click the image to enlarge.

Click the Event Definition ID of a grouped entry to view the events under the entry. The following screenshot shows the two events under the LOGCAPTURE-1000 event ID. To exit the expanded view, turn on the Show Grouped Events toggle.

Click the image to enlarge.  

Operational events are available for 10 days. By default, the start date of the calendar displays the date before the last occurred event and the end date displays the current date.

1. To filter operational events by time, perform one of the following steps:
   • To select a preset time filter, select a value from the Select relative time drop-down.
   • To specify a custom time duration, select time values from the time drop-downs or type the hour and minutes values in the time text boxes. Then, specify whether AM or PM.

Click the image to enlarge.

To filter operational events by date range, follow these steps:

1. 1. Click within the Start or End date field. The calendar appears.
   2. Click to select a start date, and then click to select an end date. 

Click the image to enlarge.

2. Filter operational events by entity name or ID and/or event definition ID.

• • To filter by event definition ID, select a value from the Event Definition ID drop-down.

Click the image to enlarge.

To clear the event definition ID filter, click the Event Definition ID drop-down and select ALL. 

• • To filter by entity name or ID, follow these steps:

Enter an entity name or ID in the Entity Name or ID search field. To clear the value that you entered and the filter, click Clear on the Entity Name or ID field.

Click the image to enlarge.

1. Click Additional Event Details for an operational event on the Operational Console page to view more details. The Additional Event Details window appears.
   Note: The details that appear in the Additional Event Details window vary based on the event definition ID.

Click the image to enlarge.

2. To view further troubleshooting details for the operational event, click Supporting link.
   Note: This link is not available for all operational events. When the link is available, click the link to navigate to a relevant view. For example, the ARCHITECT-0002 event takes you to the Architect Replay mode, which shows the area of the flow that is broken.

Click the event definition ID of an operational event to dynamically view related content from the Event Catalog. A reading pane opens to the left with details that include troubleshooting steps, context on potential causes, and testing recommendations.

Click the image to enlarge.

A trigger is a method within Genesys Cloud that allows customers to configure a response to specific events that occur within Genesys Cloud, such as those in the Operational Console. For more information about the requirements to create and configure triggers, see Requirements for triggers.

With triggers, users can:

• Send an email to a user when a specific operational event occurs. For more information, refer to this example.
• Use one or more data actions to retrieve relevant information from an external data store.
• Use a data action to invoke the agentless SMS endpoint to send an SMS.

• For more information about how to set up, install, configure, and use Amazon EventBridge, see the articles in About the Amazon EventBridge integration.
• For other technical details and to view other available events, seeAmazon EventBridge integration.

1. Open the Event Catalog.
2. To open the documentation for an event, either click the event name on the left navigation pane or scroll down on the Event Catalog and click an EventID.
3. Read through the documentation for the event, proceed through the recommended diagnosis steps, and apply the troubleshooting steps as needed.
4. Follow the directions that indicate the best points to evaluate if the event scenario resolves and how to proceed if the scenario does not resolve.