Who is this article for?

Users who want to report on daily usage.

Database or PleaseReport access will be required.

In Please Review, monitoring daily and hourly usage provides valuable insights into user activity and system performance. This article explores the challenges and theories behind generating comprehensive reports on usage patterns over specified time intervals.

1. Challenges
2. Theory

1. Challenges

Please Review stores only the last login date and time for each user in the T_Subject table. As a web application, Please Review relies on users logging out to end their sessions. However, users may inadvertently keep sessions active by closing their laptop or leaving the browser open, which can extend session durations.

The Admin then Users Logged In feature offers insights into users' recent activity by displaying their last clicks. However, this data is restricted to the server where Please Review is running and is unavailable for reporting purposes, especially in load-balanced environments. It is not accessible in the database and therefore cannot be used for reporting.

2. Theory

By using database access or PleaseReport functionality, you can periodically query the last login date and time of each user and store this information in a separate table. You may then analyse this data for reporting purposes if deemed useful. However, custom reporting is the responsibility of customers as it falls outside the scope of Support.

It's crucial to execute only SELECT queries on the Please Review database tables and refrain from direct updates or deletions unless provided by Support for specific reasons. If you wish to include the roles users were consuming at the time of login, you can extend the query accordingly. However, seeking assistance beyond Support, such as further reporting help from your account manager, may be necessary for complex queries.