Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

icecast2 <session_time> ignored in piwik session time reports #6501

Closed
ghost opened this issue Oct 22, 2014 · 3 comments
Closed

icecast2 <session_time> ignored in piwik session time reports #6501

ghost opened this issue Oct 22, 2014 · 3 comments
Labels
duplicate For issues that already existed in our issue tracker and were reported previously. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone
Long term

Comments

@ghost
Copy link

ghost commented Oct 22, 2014

It would be very nice if the <session_time> 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 <session_time> 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
Copy link
Member

mattab commented Nov 3, 2014

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 <session_time> - Piwik processes the visit time based on the timestamp of the last action/pageview request minus the timestamp of the first action/pageview.

@mattab mattab added the Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. label Nov 3, 2014
@mattab mattab added this to the Mid term milestone Nov 3, 2014
@ghost
Copy link
Author

ghost commented Nov 3, 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.

@ghost ghost mentioned this issue Nov 3, 2014
Open
@mattab
Copy link
Member

mattab commented Mar 12, 2015

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

refs #7163

@mattab mattab closed this as completed Mar 12, 2015
@mattab mattab added the duplicate For issues that already existed in our issue tracker and were reported previously. label Mar 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate For issues that already existed in our issue tracker and were reported previously. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Milestone
Long term
Development

No branches or pull requests
1 participant
@mattab