Introduction
Auditing provides insights into tenant usage and can be used to identify usage patterns, monitoring trends, or investigate unwanted scenarios. The audit log file contains operations performed by all identities, including users viewing instructions, editors creating and maintaining content, and administrators modifying configurations.
Explanation of columns
An audit log file contains the following columns:
- Timestamp
The date and time the operation was performed (in UTC). - ActorId
The unique id of the user performing the operation. For build in actors (e.g. system or guest) this field is empty. - ActorName
The last known name of the user performing the operation, making the ActorId easier to interpret. - Domain
The functional area within the application to which the operation belongs. - EntityId
The unique id of the entity affected by the operation. This field might be empty if the domain does use entities. For example, assigning ownership links a user to an instruction and does not have a separate entity. - EntityName
The last known name of the entity, making the EntityId easier to interpret. - Operation
The action that was performed. - Description
Optional additional details about the operation, such as the id of the user assigned as owner of an instruction.
Supported operations
Auditing is developed as a generic feature within the product. The data included in the audit log file depends on how individual functionality support auditing.
Audit coverage is expanded over time as:
- New features are developed and prepared for general availablity
- Existing features are updated to include auditing support
The table below provides an overview of the currently supported operations:
| Domain | Operation | Remarks |
|---|
| Instructions | Opened | Only for created instructions, opened in the product or browser extension |
| Ownership | Updated | Assigning an owner or updating the quick check date |
