Audit
By default, no persistent information is kept about service invocations that are completed. To keep a log audit service inputs and outputs, it is possible to use this simple interface to configure automatically an event emitter of type Audit that allows to store audit logs for a duration of up to 30 days based on basic criteria.
| Audit defined on an environment is only visible to the user that defined it. |
Creating an audit configuration
Clicking on the Add Audit Log button allows to define a new audit configuration for the selected environment.
When creating a new audit configuration, the following options are available:
Group |
Keep an audit log of services defined only in the selected group. Defaults to all groups. |
Artifact |
Keep an audit log of services defined as the given artifact. Defaults to all artifacts. |
Version |
Keep an audit log of a specific version of a defined service. Defaults to all versions. |
Service |
Keep an audit log of a specific service name. Defaults to all services. |
Input |
Check to keep an audit logs of service inputs. |
Output |
Check to keep an audit logs of service outputs. |
Downloading an audit log
Clicking on the icon allows to download the log of a given audit configuration.
| The dates to enter are based on GMT |
The downloaded file contains one JSON object per line representing a log entry. The format follows the service events definition defined at: https://<instance.trisotech.com>/publicapi/doc-events/#/service.