Audit

The Audit functionality collects and presents audit information for streams and usage. You can use the information to filter data flows, as well as track the input and output data. The audit information is presented on the Audit page which can be opened from the Stream editor once the stream has been run. 

Audit is useful for investigating the data flow between the Usage Engine service and the generated upstream/downstream traffic. Data flow investigation can also be done by following the input/output from one stream to another in the solutions used under the account holder. You can use it to troubleshoot potential revenue leakage, for example. 

Audit structure

Any audit functions implemented in the stream are aligned with the transaction checkpoints. The audit information consists of standard metadata: identifiers, timestamps, transaction IDs, and related data. The audit information will be available when the transactions have been completed. 

Two audit types are supported, usage audit and stream audit, and you can use both of them at the same time. 

Audit page

You open the Audit page for a stream by clicking on the View audit button in the Stream editor.

audit-page.png
Audit page for a stream

The Audit page contains three tabs;

Audit Dashboard - In this tab, you can observe trends and patterns to help make informed decisions that can help avoid revenue leakage. You can view default and custom audit metrics related to the streams you have in your solutions.

Usage Audit: - In this tab, you can see the audit information for each function, which you can use to display relevant information when the transactions are completed. If you want to define customized audit that provides deeper insights, you can design this by using related commands in the Script Function.  

Stream Audit - In this tab, you can see detailed audit metrics on the target stream. 

All audit information is stored in an internally managed data storage. The collected audit records are isolated per account and kept in storage for 30 days. The data will be automatically removed after this period ends.

Subsections

This section has the following subsections: