Solution - User Activity Tracing
Purpose
This solution performs the user login/logout activity audit. By default, the script will audit the last 24 hours of data and replace any existing duplicates. Therefore, the script should be scheduled at a quicker interval than 24 hours to provide a buffer and ensure that no data is missed.
Associated Content
Content | Type | Function |
---|---|---|
Activity Logging Reporting [DV, Global] | Script | This script is used to perform the audit of the login/logout of the users. |
User Activity Audit [Script] | Dataview | The dataview shows the login/logout audit of the users. |
pvl_login_logout_audit | Table | This table stores the user login/logout data. |
Implementation
-
Import the script Activity Logging Reporting [DV, Global].
-
Import the dataview User Activity Audit [Script].
-
Run the script once by setting the User Parameter value 'SetEnvironment' to 1, as shown below:
This will create the table and also establish the system property 'ProVal_UserLogIn_Out_Threshold_Days' with the global parameter value 'DataRetention_Threshold' in days, as provided in the script for data retention (defaults to 90 days retention).
-
Then, schedule the script on the Windows machines.
NOTE: This script is not suitable for execution on the DC servers to avoid the noise of multiple user login/logout traces in the system event log as well as in the database table. The DC server is excluded from the script for execution.