The Data Activity Reports are located under Tools > Logs > Data Activity.
Last Data Activities: helps administrators troubleshoot any data missing issues from AccessPatrol, BrowseReporter, and enPowerManager.
Data Data Uploads: count the total number of daily uploads from AccessPatrol and BrowseReporter for baseline monitoring.
Assess whether or not your active users are reporting data to the server regularly to ensure data integrity in your database. Identify inactive users who haven’t uploaded data to your server in a while. Remove inactive users and decommission computers to optimize the performance of your database.
User: this report is grouped by users.
Group: the group your users belong to in CurrentWare.
Last activity date: this is the last time your users have uploaded any data from any CurrentWare solutions to the server.
Days since the last activity: the number of days from the last activity uploaded.
Last login date: the last time your user connected to the server.
Days since last user login: the number of days from your user’s last connection.
Action: to view the details of each last activity and the uploaded computer.
View Last Activities
See the last activity date for each solution data type and which computer it was uploaded from.
Activity: the tracked solution data type includes:
Last activity date: this is the last time your users have uploaded solution data to the server.
Computer: this is the computer data was uploaded from.
1. Data integrity health check
When you first run this report, go through the list and see if you can identify active users. If your list is empty or only contains inactive users, then your server is running smoothly and is receiving data from all of your users.
2. Identify active users with missing data
Active users should not be displayed on this list. Normally, active users should be constantly uploading data server. If you see an active user on this list, it is an indication that the user is not connected to the server.
To troubleshoot this issue, follow the recommendations on our client connection troubleshooting guide to fix your issue.
3. Identify active users with missing data & recent logins
If you see a user with a recent login date but hasn’t uploaded to the server in a while (see an example screenshot below). This is an indication that the user is connecting to the server but hasn’t uploaded any data to it for a while. There is a possibility that this user is experiencing a tracking or uploading issue.
To troubleshoot this issue, make sure your CurrentWare ports are open for data upload. Contact the CurrentWare support team for further technical assistance.
Monitor data uploads and look for patterns deviating from the usual daily average. This can help spot issues such as disconnected clients or errors occurring during data uploads.
1. Data integrity health check
When the record count and user count for your data remain consistent on a day-to-day basis, this is a good sign. Your server is receiving data normally from your users.
2. A significant drop in the record count and number of users
When
the record count of your data and the number of users drop
significantly from the daily average, check the calendar to see if the
drop is expected. For example, the count drop could be due to a holiday,
office events, or the weekend.
If you see a pattern of significant drop for more than several days, review the client connection troubleshooting guide and make sure your make sure your CurrentWare ports are open. Contact the CurrentWare support team for further technical assistance.
Both
reports allow the administrator to conveniently export the data in the
current view of the table to .XLSX or a .PDF file for further data
analysis.