Meanwhile, we have identified the cause: Sometime after the version 1.10.1 four new fields for the table log_visit have been introduced, one is called "config_os_version". In our intranet many user sessions are running under Citrix. The corresponding calculated value for this field is "Server 2003". With this value, the write operation goes wrong. The complete record is not written.
The call Piwik_Tracker getDatabase :: () -> query ($ sql, $ bind) in Visit.php is not coming back, the action is not counted!.
So 3,500 visitors per day with all actions are lost in our statistics.
As a quick workaround, we now reduced the length of the value in Visits.php to "2003". We dit not check if the error is caused by the length or the white space of the original entries. We also do not know whether the field is ever evaluated, there is still the old field config_os, obviously with a sufficient value "WS3" for the OS statistics.
As a real fix of course the writing process has to be corrected.
Most troubling to us ist, that there were no errors in any logs on the data loss. Finally these entries are the basis of all statistics.
The call Piwik_Tracker getDatabase :: () -> query ($ sql, $ bind) in Visit.php is not coming back, the action is not counted!.
So 3,500 visitors per day with all actions are lost in our statistics.
As a quick workaround, we now reduced the length of the value in Visits.php to "2003". We dit not check if the error is caused by the length or the white space of the original entries. We also do not know whether the field is ever evaluated, there is still the old field config_os, obviously with a sufficient value "WS3" for the OS statistics.
As a real fix of course the writing process has to be corrected.
Most troubling to us ist, that there were no errors in any logs on the data loss. Finally these entries are the basis of all statistics.