Skip to main content
Version: 2.2

Activity log


You must have the admin role assigned to view the following Settings pages in the UI:

  • LDAP Authentication
  • Access Control
  • Activity Log

The WANdisco® UI logs all user-driven interactions and resulting changes (including errors) to /var/log/wandisco/audit/ui. Use this to monitor user activity in Data Migrator.


Only UI-driven actions are recorded in the activity log.

View the activity log from the UI

  1. Select Settings.

  2. Select Activity log.

Activity log records

Data Migrator creates two audit records for each operation. For example, you see two audit records for each user sign-in:

  1. The first record shows that the sign-in method has been entered and shows the user assigned at that point. The user is anonymous because nobody is signed in yet.
  2. The second record shows that the sign-in method has returned.
    1. If sign-in was successful, it shows the user assigned at that point, which is the registered username.
    2. If sign-in was unsuccessful, it shows the anonymous user.

Default logging configuration

File nameDirectory nameRotation periodRetention period
livedata_ui_audit.yyyy-MM-dd.log/var/log/wandisco/audit/uiDaily90 days
  • No activity log is created for days that have no UI activity.
  • You can't change the rotation period.

See WANdisco UI - Logging to change the configuration.

Entry types

There are three types of entries in the activity log:

  1. METHOD_ENTERED The user-driven action that was recorded.
  2. METHOD_RETURNED The user-driven change as a result of the action.
  3. METHOD_EXCEPTION Any exception/error that occurred as a result of the action.

Entry contents

For each entry, the following is recorded:

  • The timestamp of the action.
  • Who performed the action.
  • What type of entry it is.
  • The action data depending on the type of entry:
    • METHOD_ENTERED The data used to take the action.
    • METHOD_RETURNED The result of the action.
    • METHOD_EXCEPTION The contents of the exception thrown.

Entry examples


Example of a user sign-in request
2021-04-28 14:22:49,377 [livedata-ui-async-task-4525] AuditEvent [timestamp=2021-04-28T14:22:49.376Z, principal=anonymousUser, type=METHOD_ENTERED, data={args=[LoginVM{username='', rememberMe=null}], operation=Logged In}]


Example result of user sign-in request
2021-04-28 14:22:49,529 [livedata-ui-async-task-4505] AuditEvent [timestamp=2021-04-28T14:22:49.529Z,, type=METHOD_RETURNED, data={operation=Logged In, methodResultData=<200 OK OK,$JWTToken@60c2fe20,[Authorization:"Bearer eyJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJ1c2VyQGxvY2FsaG9zdC5jb20iLCJhdXRoIjoiUk9MRV9BRE1JTiIsImV4cCI6MTYxOTc5MjU2OX0.3HvgOb82_UpEk_Yy-nWrvEXyU71pubM5EZKR_MgskViAJdflASzsLH5rqr2fmHgGLTMiMWIxRabJWKYt7Hz9aQ"]>}]


Example of a failed user sign-in request
2021-04-29 16:16:46,656 [livedata-ui-async-task-5360] AuditEvent [timestamp=2021-04-29T16:16:46.655Z, principal=anonymousUser, type=METHOD_EXCEPTION, data={exception=/fusion{401, EMAIL_OR_PASSWORD_INCORRECT, i18nParams={}}, operation=Logged In}]

Redaction policy

By default, all sensitive information (such as passwords and filesystem access keys) are redacted in the entries.