Usage audit

Audit generates basic information about a transaction once it has been completed successfully. The usage-based audit is the process of acquiring information about transaction records based on collected analytics data. The usage audit logs are retained for 180 days and can be accessed by navigating to the Usage audit tab in the main Audit view.

The Usage Audit tab in the main Audit view

There are several options for filtering the information. To reload the data, click the Refresh icon on the right side. 

Date and time selection: Click on the blue calendar icon. A pop-up window will open and you can select the start and end date and time.

The data in the Usage Audit tab is shown in a table, organized by different fields. Next to every column title are the options to sort (Ascending or Descending) and search. These interactive options can be used to gain a detailed understanding of given values: 

  • Sort – Click on the arrow icons next to the column titles to sort the data into ascending (smallest to largest) or descending (largest to smallest) order.

  • Search – Click on the magnifying glass icon to search for a given value or character inside the data in the column.

The Usage Audit display organizes the data in the following columns: 

Field

Description

Field

Description

Execution

Shows the stream ID

Transaction Start Time

Indicates the start date and time of the audit capture

Transaction End Time

Indicates the end date and time of the audit capture

Filename

Indicates filenames of the incoming records

Origin

Shows the source of the records

Total Input

Shows the total number of input records in the stream

Total Output

Shows the total number of output records in the stream

Duplicated

Shows the number of results that have been duplicated, according to the Deduplicate Function

Rejected

Shows the number of invalid records, according to the Validation Function

Custom Audit

Custom Audit provides deeper business insights. To enable Custom Audit, use the audit-specific statements in the Script Function. Configuration is done in the node. If any custom columns are added, they will be distinguished by a border and light blue coloring.