How to Monitor and Manage Integration Logs
Integration log records what activities the system tried to pass to integration and to which registrant/attendees. The activities include the status of each attempt (Success/Failure) and each registrant /attendee. This enables you to monitor failed actions and retry or fix any issues. The logs are grouped into batches for easy viewing, and the page provides necessary options that help you monitor your log conveniently.
To access the integration logs:
-
Log in to your Zuddl dashboard.
-
Go to the integration listing page.
-
Click the View logs link for the required integration.
On the integration logs page, the left-hand side column shows the batches in the order of recency. The Action column (center) shows logs within the selected batch. On the right side, the request and response are shown. The request body contains all the details of a particular action. For example, the 'Add_on_modified' request shows the 'oldRegistration' object along with other details, or the 'Ticket_modified' request shows the 'oldTicketDetails' object along with other details.
Response is only shown for errors.
Searching for logs
The search bar is available on both the Integration logs column and the Actions column. You can search for logs by entering the email address (fully or partially) or utilize filters to search for the required actions.
When using the filter, you can choose the following options to filter:
- Status: select 'Failed' or 'Success' logs
- Event id: select an event Id to filter
- Dates: Choose a date from the date picker
- Activities: Select the desired activity
How to read an integration log
Integration logs
The left side shows all the batches ordered by recency. A batch card shows the following details:
- Event id: Shows the event id of the batch. Every log is associated to an Event id.
- Date and time: The date and time of the action
- Activity name: The name of the activity recorded
- Action label: Shows the number of actions/logs in the batch.
When you are on the logs pages, many logs are flooding in. Instead of scrolling through the logs, you can directly click the Jump to recent button, as shown below, to reach the topmost (recent) log.
At the center, the Actions column shows all the logs in a batch. You can filter the logs for success or failure and take actions accordingly.
Retrying data for failed logs
On the Actions column, clicking Retry will retry all logs of that batch.
Clicking ‘Retry’ for a particular registrant’s/attendee’s email will retry syncing the data only for that registrant/attendee. Once a failed log is retried, the retry button disappears for that log.
Retrying will result in either/all of the following in your integrations:
For Salesforce, Marketo, and HubSpot integrations:
- Contact/Lead fields will get updated (according to the update policy defined in the field mapping step of the integration setup)
- The Campaign/Program member status of a registrant/attendee will be out of sync
- Data of Campaign/Program member fields will be overridden with the retried data
- Activities may be created at an inaccurate time, which may trigger your workflows/automations to run
For Slack, Slack + Salesforce integrations:
- Untimely message notifications may be sent to Slack channels and to owners (if configured).
Once the retry is complete, a link appears on the log action "New log created". Clicking it opens a new browser tab to view the log of the retried attempt’. Alternatively, you can also click the Jump to Recent Logs icon on the Integration Logs column (left-hand side column).
Bulk retry
The bulk retry option retries all the logs in a batch. All the failed logs that got retried are grouped in a batch. Only failed logs are retried. Once the bulk retry for all the failed logs in a batch is complete, the ‘Retry’ button for individual logs and the ‘Retry all’ icon for the entire batch will disappear.
Request and Response
On the right, the request and response are shown. The JSON request shows all required details of an activity.
Copying the logs
You can copy the entire request body by clicking the Copy button on the Request/Response column.