@streamradio opened this Issue on October 22nd 2014

It would be very nice if the field from the icecast2 log import, is taken into account to calculate the session times. Otherwise i need to insert manually a start GET request seconds before the actual log entry, which can couse problems in some cases, and its also somehow annoying. Or is there a setting to activate this behaviour per website, or is it solvable via plugin?

@mattab commented on November 3rd 2014 Owner

Thanks for the report. can you please give a sample log file, and explain what is the bug that you have? we haven't used this log format ourselves and I'm not familiar with - Piwik processes the visit time based on the timestamp of the last action/pageview request minus the timestamp of the first action/pageview.

@streamradio commented on November 3rd 2014

The special thing about icecast log messages is that there is no connect message, but only a disconnect message, with the connected streamtime appended to the end of the message, so there is only one action, and piwik is unable to get the visit time. According to log import source that field is implemented. A log message looks as follows:

82.113.98.12 - - [02/Nov/2014:07:10:43 +0000] "GET /stream-48 HTTP/1.0" 200 74694 "http://shoutcast.com" "foobar2000/1.3.2" 933

in this case the timestamp is the connection time, and the integer at the and represents the seconds connected.

What happens now in Piwik is that the visit time for the stream connects is calculated with the time between those disconnect messages, so if there are at least 2 disconnect "GET /stream.." messages from a client a visit time is generated, but only with one message not. But those generated visit times between disconnects are not the ones i'm interrested in.

@mattab commented on March 12th 2015 Owner

Issue was moved to the new repository for Piwik Log Analytics: https://github.com/piwik/piwik-log-analytics/issues

refs #7163

This Issue was closed on March 12th 2015
Powered by GitHub Issue Mirror