## 4.2.13.8.10  Monitoring Events
## Prerequisites
- You have established a connection through the configuration of the communication arrangement in the previous steps. For more information, refer to Communication Arrangements [page 1125].
- The Enterprise Event Enablement - Event Monitor app is visible.
- If the Enterprise Event Enablement - Event Monitor app is not visible, add the Enterprise Event Enablement business catalog to the SAP\_BR\_ADMINISTRATOR role using the Maintain Business Roles app. The change in your role becomes effective after you have logged out and logged in again.
## Context
Using the Enterprise Event Enablement - Event Monitor app, you can monitor events by status and access the payload.
## Procedure
1. Log on to the SAP Fiori launchpad in the ABAP environment system.
2. In the Communication Management app, select the Enterprise Event Enablement - Event Monitor app. You will see an overview of all configured channels. The columns filled with numbers correspond to the number of events for a given status.
3. Choose a channel name (created in Creating Communication Arrangements [page 1125]) to access detailed information. The Inbound Events and Outbound Events tabs contain all inbound or outbound events by topic and status.
4. Select a Topic .
All events for the given topic and status are listed.
5. Select an event to access detailed information. The detailed view of a consumer inbound event contains:
| Times       | • Publish Time • Arrival Time • Consume Time • Fail Time   |
|-------------|------------------------------------------------------------|
| Event Data  | • Cloud Event Source • Cloud Event ID • Quality of Service |
| Consumed by | • Consumer ID • Consumer Version                           |
| Payload     | • Payload • Size (kB)                                      |
Events reside in an internal queue of the enterprise event enablement. Once the processing of an event is finalized, it is deleted from the queue after a certain time period. Processing an event is finalized if the status is acknowledged or failed.
| Deletion timeline                   | Event status      | Description                                                                                                                                                                                                                     |
|-------------------------------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Hourly before the current full hour | Acknowledged      | The event has been successfully pub- lished or consumed according to the chosen quality of service. An hourly background job deletes all acknowl- edged events from the event monitor.                                          |
| No deletion                         | Failed            | The enterprise event enablement either failed to publish the event after 5 at- tempts or the event could not be con- sumed by the corresponding consumer. Failed events are stored until you either delete or retry them again. |
| No deletion                         | Not processed yet | All events that have a different status than acknowledged or failed are not de- leted since they are not yet fully proc- essed.                                                                                                 |
The timeline for deleting is subject to change.