pfqgauxfb
/
gitlink_help_center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7f0a14ee07'
${ noResults }
gitlink_help_center/docs/retraced/getting-started/retraced-basics.md

839 B
Raw Blame History

Retraced Basics

At it's core, Retraced 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.