Dear Wowza team,
we use Wowza Server 3.1.2 together with Longtailvideos JW player V5.10 to publish and play a livestream (RTMP and HTML5 mode, respectively).
For reporting services we use Sawmill afterwards to analyse the live stream access data and to generate statistics from the Wowza server stat logfiles.
However, we do not entirely understand the data output in the Wowza server stat logfiles, maybe you can clarify them a bit for us.
In order to analyze the number of concurrent viewers, our statistic tool uses a counter that is increased whenever a play event occurs and is decreased on stop and pause stream events.
In a log sample, there are 2,243 "play" events, 2,024 "stop" and 33 "pause" events. The difference between the play and the pause+stop numbers, is 186, interpreted as a number of concurrent streams "left over". This indicates the Wowza server is either not logging the stop/pause events, or that there is no stop event associated with these streams.
What might be the reason for this behavior? My explanation would be that the stream events are triggered by the client video player and whenever a user simply closes the web browser window without stopping the stream playback in the JW player, then the current stream for this client remains in idle state on server side? or something like that...
How could be get an appropriate number for concurrent viewers in a specified time range, what would be the best way?
Thanks in advance