Who is this article for?

Users and IT Administrators needing to understand how events, errors and data changes are logged.

Internal Audit logs various information.  This article signposts articles describing the logging options.

1. Service/client event and error logging
2. The Robot and Robot Jobs
3. Diagnosing SSO via SAML
4. The Audit Trail / Data Changes

Service/client event and error logging

Each of the application services logs initialisation events and errors to a text file in its own application folder.  The client logs errors to the user profile.  In addition, each component can have its logging level raised to provide more verbose output.

These locations and settings are discussed in detail in this article: Accessing log file locations and settings – Internal Audit

Note that in order for log files to be created, the service account requires write permission to the parent folder.  See Troubleshooting service log files creation issues – Internal Audit for further information.

It is important to understand the effect of time zones on log entries.  Logging and time zones – Internal Audit describes how this works.

The Robot and Robot Jobs

Events and errors are logged to a text file that is located in the Robot service application folder.  Further information on this can be found in this article:  Accessing log file locations and settings – Internal Audit

Some information is also logged to a database table called RobotJobHistory.  More information on this is available here:  Ideagen Internal Audit (Aura): Inconsistencies in Robot activity logging – Internal Audit

Optionally, jobs that create emails can log for email Date/Time, To and Subject.  Setting this up is described at Enabling Robot job email logging – Internal Audit.

Diagnosing SSO via SAML

When this is enabled, the application will log diagnostic information about the SAML connection to a text file at SamlMvc\logs or WebUI\logs.  Doing so is documented here: Enabling logging for SSO via SAML2 – Internal Audit.

The Audit Trail / Data Changes

Where logging of data changes is enabled, a user can see the activity history for a particular record via the Properties Panel.  This is described in more detail here:  Understanding the Audit Trail – Internal Audit

Note that when opening the Properties Panel the audit trail can often appear blank, but this is due to the default filter setting.  For more information on this, see:  The audit trail may appear blank – Internal Audit

A 'worked example' for querying a log table is available here:  Exporting deleted Sample Results from the log table (Example) – Internal Audit