Gathering logs from RPI

Saving Workflow Diagnostics

When investigating or submitting a case to Redpoint support for failed workflow activities, it is recommended that you gather the associated diagnostic information.

From the Interaction Results window, select the Download Diagnostics option.

This will allow you to save all available logs and information for that particular workflow instance.

The job created when selecting that option controls the download of a diagnostics zip file, which contains a series of files that can be used in determining why a workflow failure occurred. On the job's successful completion, an Open File Location button is shown. Selecting it displays the diagnostics zip file in Windows Explorer. The zip file contains the following:

AuditHistorytxt
ExecutionPlan.txt
- Used by the Execution Service to execute activity within the workflow.
ExecutionSchedule.txt
- The state of activity execution at the Execution Service.
Interaction Workflow.json
- A dump from the table of the same name.
QueryTrace.txt
ServerLog.txt
Summary.txt
- High-level summary information.
SystemHealth.json
For each audience/fulfillment activity
- Audience: dump from the DataWorkflow table.
- Instance: serialized activity details.
- Log: relating to the current activity's execution.
Files
- The exported interaction files.

Gathering full Server/Client, SQL Trace, and Audit logs

These are located in the Management>Operations tab.

Filter results accordingly and use the Export log option to save the files to your local drives.

Filter options
- Server & Client log
  - From - To dates
  - Severity levels
    - Critical
    - Error
    - Information
    - Warning
- Query Trace log
  - From - To dates
  - Status
    - Completed
    - Failed

Physical log locations

RPI log data is stored in the following operational database tables:

SQL Trace Logs: InteractionAudit_xxx..SQLTraceLog
ClientServer Logs: Pulse_Logging..Log
Audit Logs: InteractionAudit_xxx..AuditHistory