Other audits
Cluster Auditing
Certain activities are audited at the cluster, rather than tenant, level. These audit records are not visible in the Operations Audit Log. Rather, they can be accessed at the AuditHistory table in the Pulse_Logging database.
The following activities are audited at the cluster level:
| Audit Sub-Type |
Interaction Event | Pause All Request |
Interaction Event | Resume All Request |
Security | Create User |
Security | Delete User |
Security | Edit User (including details of current and previous user groups) |
Security | Sign In |
Security | Sign In Failed |
Security | Password Reset |
Security | Reset User Password |
Security | Unlock User |
Auditing Table and Column Usage
RPI allows you to audit the usage of data warehouse tables and columns when running audiences in production interaction workflows. Such auditing is controlled by system configuration setting AuditAudienceFieldUsage. Table and column auditing is switched on when this setting is set to 1, and off when set to 0. When auditing table and column usage, the following audit tables are populated:
DataflowAuditSummary: one row is created per audience segment. For each segment, the following are captured:
OutputID
DataflowInstanceID
OutputName
WorkflowAssociationInstanceID
OutputCount
ExecutionDate
ResolutionTable
ResolutionKey
DataflowAuditFields: multiple rows are created per DataflowAuditSummary record. For each field, the following are captured:
ID
OutputID
TableName
ColumnName
Operator
Values
DataflowInstanceID
DataflowAuditExecutionLookup: if the audience is used in e.g. an email offer or in data extract file generation, a record in this table is used to link to the ChannelExecutionID, which can be used to link to the Channel Execution table in the tenant’s Interaction operational database and the Offer History tables in the data warehouse. The following are captured:
OutputID
ChannelExecutionID
DataflowInstanceID