Tracing Adobe I/O Events
To troubleshoot issues with event-registrations, Adobe offers Debug Tracing feature. Using Debug Tracing, you can inspect the activity between the Adobe service and your integration to see what data is being sent and how your integration is responding. Each trace comprises of the event delivery HTTP request (sent by I/O Events), and response by the consumer application. This information can be of critical importance to your debugging efforts.
Debug Tracing is only available for event registrations with either a Webhook, Runtime Action or Amazon EventBridge as their delivery destination.
To access Debug Tracing:
Log into Adobe Developer Console and select the project containing the event registration.
From the Project Overview, select the event under Events in the left navigation.
From the Registration Details, select the Debug Tracing tab. You will see a list of events, beginning with the most recent.
The Debug Tracing tab shows last 100 traces for your event registration.
Select any trace in the list to expand its view and see more details. By default, the request (sent by Adobe) is shown, with headers and body. Select Response to view your integration's response to the event.
By inspecting the details of the request and response, you can examine the communication loop between Adobe and your integration to diagnose any breakdown in the flow or processing of events.
Filters
- Use the "delivery status" dropdown to selectively fetch "success" or "error" traces only.
- Use the "Add Filter" button to filter traces by one or more granular metrics, like response-time, response-code and retry-deliveries. These filtering options work seamlessly offline without fetching new data from the server.
Retention of Traces
All traces older than 7 days are deleted for GDPR compliance.
Traces from last 100 'success' and 'error' deliveries are retained. All older traces are automatically deleted.
