 |  |
| | |
The user activity logging infrastructure changed substantially in 6.3. Prior to 6.3 user activity events used to be written into a file adjacent to each course. From 6.3 on all such user activity events are written into the database to allow easier processing later.
This change has several implications:
The old course log files have gone - during migration from 6.2 to 6.3 they are zipped and stored into the course' storage folder under old_course_logs.
All user activity logging events are now stored in one table: o_loggingtable. Depending on the traffic of the particular OLAT instance, this table can grow rather large. It is strongly recommended to monitor this table and keep the size reasonable. Possible solutions in this area include e.g. periodic cleanup of old data or compressing on a monthly basis and using merge tables.
It allows to process these logging information into meaningful statistics - both online as described in this documentation as well as offline for further research-type studies. This provides better e-learning controlling from both an author and an administrator's point of view.
Technically, the logging no longer happens via JMS and a single-service: RemoteAuditLogger has gone.
What used to be called 'course log file export' is still available with the new logging. The difference is that this time it is a select in the o_loggingtable compared to the copying of a file in 6.2. This means that a course log export now potentially takes longer - which is why there are restrictions on how many can do this (default is 2 per node simultaneously). It also implies that for this to be done in a performant way it might be necessary to use stored procedures (depending on the amount of data you have in your installation).
The format of the logging is no longer free text but rather structured - which means the developer needs to be aware of this and needs to follow this structure. This logging and statistics documentation describes how this is best done.
| |  | |
 |