Audit trail - Data360_DQ+ - Latest

Audit trail events

These are the main events that can occur in the system. They are general in nature and may be described with more granularity in the audit trail event entries panel by a specific action type.

Event types

Create

This event is logged whenever an object is defined for the first time - note that this extends beyond data stages. For example, both the creation of a data store and the creation of a user would cause a Create event to be logged.

Update

This event is logged whenever the definition of a preexisting object is changed. For example, changing a field name in a data store, scheduling a data view to execute, or making a user an administrator would all cause an Update event to be logged.

Delete

This event is logged whenever an object is deleted. For example, deleting an Analysis or deleting an Environment would both cause a Delete event to be logged.

Duplicate

This event is logged whenever a data stage is duplicated. Note that a Duplicate will also cause Create action types to be logged in the audit trail event entries panel.

Copy

This event is logged whenever a data stage is copied.

Move

This event is logged whenever a data stage is moved.

View

This event is logged for configured read-only activity, such as opening a case store or data store search screen, opening a case or record form screen, or viewing a case from search results.

Bulk Update

This event is logged when multiple case or record updates are grouped into a single audit trail event.

Bulk Fast Track

This event is logged when multiple case fast-track transitions are grouped into a single audit trail event.

Bulk Delete

This event is logged when multiple case or record deletions are grouped into a single audit trail event.

Import

This event is logged whenever a data stage or set of data stages is imported into an environment. Additionally, an action type is logged for each item that is Imported.

For example, if you import a pipeline containing multiple data stages into a new environment, the Import event type is logged in the audit trail event panel and a Create action type is logged for each imported data stage in the audit trail event entries panel, because importing data stages means that they are "created" in the target environment.

Export

This event is logged whenever a data stage or set of data stages is exported from an environment. Additionally, the Update action type might be logged for each exported item if reset dirty state was performed during the export.

Export Data

This event is logged when a user exports data from a case store or data store. It records the export as a distinct audit trail event so administrators can identify who exported the data, when the export occurred, and which store the export came from. This is useful for monitoring data access and supporting audit or compliance reviews.

Promote

This event is logged whenever a data stage or set of data stages is promoted from one environment to another. Additionally, the Update action type is logged for each item that has its dirty state reset and Create action types will be logged for each item that is created in the target environment.

Execute

This event is logged whenever a data stage executes. More details about what type of execution occurred will also be logged in the audit trail event entries panel.

Session

This event is logged whenever a user log ins or logs out. Which specific action occurred will be logged in the audit trail event entries panel as Begin Session or End Session.

Member name

This section of the audit trail event panel simply logs the full name and email of the user that performed the listed event.

Time occurred

This section of the audit trail event panel logs the time at which the event occurred. Note that the listed time will be in the system time zone set in administrator preferences.

Audit trail event entries

When an event is logged in the audit trail event panel, it may have one or multiple sub-events associated with it. The audit trail event entries panel logs these sub-events, providing more specific information about the general event that occurred.

Environment name

This section lists the environment that the event occurred in. Note that any environment you administer in which an event took place can be listed. Environment listings are not limited to the environment you are in while viewing the audit trail.

Object type

This section lists the type of object the event occurred on. Listed object types can be data stages or other system objects. For example, if a data store were created, the listed object type would be data store, however, if a user logged into the system, the listed object type would be user session.

For user activity auditing, object types can also include Search Screen, Form Screen, Case Store Data, and Data Store Data.

Object name

This section simply lists the name of the object the event occurred on.

For search screen and form screen activity, the object name uses the store and screen path, for example Case Store Name / Search Screen Name or Data Store Name / Form Screen Name / Record Identity.

Action type

This is the section of the audit trail event entries panel that lists the specific type of sub-event that occurred within a general event. Some sub-events have the same type as their parent event, while others have more descriptive types. Specific examples are provided below, however, in most cases the administrator should be able to identify what has occurred based on naming convention alone.

Create

Logged whenever an object is created. For example, when a data store is created by a user the audit trail will log Create as the event type and Create as the action type. As a more complicated example, Create could be logged multiple times as an action type when a pipeline containing multiple data stages is imported.

Update

Logged whenever an object is updated. Many different events can produce this entry. For example, editing an existing data view would cause Update to be logged in the audit trail event panel and in the audit trail event entries panel.

As a more complicated example, promoting a pipeline would cause Promote to be logged in the audit trail event panel and Update to be logged for each item that was promoted in the audit trail event entries panel.

Delete

This action type is logged whenever a Delete event occurs. For example, deleting an analysis or deleting an environment would both cause a Delete event and a Delete action type to be logged.

Move

This action type is logged whenever a Move event occurs. Note that a Move will also cause an Update action type to be logged in the audit trail event entries panel.

View

This action type is logged when a user opens a configured search screen or form screen.

Search

This action type is logged when a user performs a user-initiated search on a configured search screen.

Transition

This action type is logged when a case transitions to another state, including bulk fast-track operations.

Merge

This action type is logged when cases are merged.

Move Record

This action type is logged when a detail record is moved from one case to another.

Claim user

This action type is logged whenever a user account is claimed. Newly created user accounts must be claimed to be functional. Since all newly created users are automatically claimed, creating a new user would log Claim User in the audit trail event entries panel, as would explicitly claiming a user at any time.

Unclaim user

This action type is logged whenever a user account is unclaimed.

Enable user

This action type is logged whenever a user account is enabled. New user accounts are automatically enabled by default.

Disable user

This action type is logged whenever a user account is disabled.

Make admin user

This action type is logged whenever the administrator privilege is given to a user account.

Remove admin user

This action type is logged whenever the administrator privilege is removed from a user account.

Run

This action type is logged whenever an executable data stage runs. The logging of Run is meant to provide more specific information for the Execute audit trail event.

Rerun

This action type is logged whenever an executable data stage reruns. Note that a rerun will automatically rollback the most recent execution of the data stage if it has not already been rolled back, so a rerun action type will sometimes be logged with a rollback action type.

Rebuild

This action type is logged whenever an executable data stage rebuilds. The logging of Rebuild is meant to provide more specific information for the Execute audit trail event.

Terminate

This action type is logged whenever a user terminates a data stage that is running. The logging of Terminate is meant to provide more specific information for the Execute audit trail event.

Rollback

This action type is logged whenever an executable data stage is rolled back. The logging of Rollback is meant to provide more specific information for the Execute audit trail event.

Begin session

This action type is associated with the Session audit trail event. It is logged whenever a user logs on.

End session

This action type is associated with the session audit trail event. It is logged whenever a user logs off.

Schedule

This action type is logged whenever a user schedules an executable data stage to execute. As scheduling is an act of updating a data stage, Schedule is associated with the Update audit trail event and will be logged alongside an Update action type.

Cancel schedule

This action type is logged whenever a user cancels the scheduling of an executable data stage's execution. As scheduling is an act of updating a data stage, Cancel Schedule is associated with the Update audit trail event and will be logged alongside an Update action type.