...
Audit is useful for the investigation of 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. It is used to troubleshoot potential revenue leakage and any documented issues can help document them.
Audit Structure
Any audit Functions that are functions implemented in the stream are aligned with the transaction checkpoints. The audit information is comprised of standard metadata: identifiers, timestamps, transaction IDs, and related data. Note that the audit is present when the transactions have been completed.
...
All audit information is stored in an internally managed data storage. The collected audit records are isolated per account and kept in storage for 180 days, data will be automatically removed after this period ends. There are two audit types supported:
Audit Dashboard: 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.
There are two audit types supported and both of them can be run at the same time.
Usage Audit: The results from the audit Functionfunction are used to display relevant information when the transactions are completed. A Default Audit allows for the presentation of basic information, while a Custom Audit provides deeper insights. The custom audit statements can be accessed by enabling the relevant commands in the Script Function.
Stream Audit - This Function gives out provides detailed audit metrics on the target stream.
...
.
Subsections
This section has the following subsections:
...