Replicated Audit Log Basics

Events in an audit log must be ordered

At it’s core, the Replicated Audit Log consists of 3 components:

  • The Publisher API, which is used by a vendor application to report audit events to Retraced.
  • A Logs Viewer which can be embedded in the frontend of a vendor application to allow end customers to view, search, and export logs.
  • The Enterprise IT Integration API which be used by end customers to consume audit log events programmatically.

The first step in any Retraced integration is sending an event to the Publisher API. Once events have been published to Retraced, they can be consumed either by embedding the logs viewer or by accessing the Enterprise IT Integration API.