Auditing
In the Audit Viewer dialog, you can view and search for Designer auditing data. Audit entries are recorded automatically when you enable the Auditing feature.
To open the Audit Viewer dialog, select . Click the Logging tab and click . To use the Auditing feature, you must have the permission Administer Audit on the farm level.
The Audit Viewer dialog provides a variety of search capabilities to search for recorded audit entries, so that you can quickly find the data you are looking for.
These are basic searching scenarios:
- Show all audit entries between a start and end date.
- Show all audit entries for a specific user.
- Show all audit entries for a specific application.
- Show all audit entries for a specific audit event (requires to also set the application).
- Show all audit entries for a specific audit event of an application filtered by additional fields.
You can use these search criteria in the Audit Viewer dialog:
- From, To: Time period in which the audit event happened.
- Repository user: The Repository user who performed the audit event. This is the user login name in Repository.
- Windows user: Windows user name under which the audit event happened. This is the fully qualified Windows user name.
- IP address: IP addresses of the physical machine where the audit event happened. This is a semicolon separated list of all IP addresses the current local machine has assigned.
- Computer name: Name of the physical machine where the audit event happened. This is the current local machine name from the operating system.
- Process name: Name of the Windows process (executable) in which the audit event happened. This is the name of the process without extension.
-
Application: Predefined list of applications that offer auditing. You can select Designer from the drop-down list. The Event field shows a list of application-specific audit events that are recorded by Designer.
- Project: List of available projects in the current repository in which the audit event happened. This is the unique name of the repository project. You can select <Any> here to consider all projects in the current repository, or <Unknown> if projects were deleted meanwhile and cannot be mapped to existing projects.
- Event: Audit event that happened. The list of audit events shown here depends on the selected application. Custom fields that are linked to an audit event are available for filtering if a certain audit event is selected. In such a case, a specific set of additional fields appears in the filter section for the selected audit event. You can select <Any> here to consider all events in the current repository respectively application.
If you select a combination of different search criteria, they are always
combined with a logical and
when a database
query is performed. The only criteria that you must always specify are the time range and
the application. You can leave other search criteria empty or use the <Any> option.
To start the search according to the specified search criteria, click
. On the right side of the dialog, a list of the resulting audit entries is shown. By default, this list shows the common column information without custom field information. If you perform a search by using a specific audit event as a filter, in addition applicable custom columns are shown that are based on the selected event.To reset the specified search criteria, click
. To start the export of the search result to a .csv
file, click . In the Save As dialog, specify
the file name and click .
The current view of audit entries of the previous search is saved to the file.