Article ID: 5344
|
Creation Date: 10/13/2006 3:35 PM
|
Product: SiteRemote
|
Attachment: -
|
ArticleType: FAQ
|
Version: 4.x (and later)
|
Language: English
|
Views: 63493
|
Last Modification Date: 6/14/2021 9:14 AM
|
Platform: Windows Server
|
|
Level: Closed
|
|
|
FAQ: How are end user sessions counted in SiteRemote reports?
A. Session counting and usage time
The session and usage time will be calculated from the log file information the SiteKiosk client sends to SiteRemote.
The SiteRemote Server distinguishes between activated and deactivated payment device.
1. Session counting and usage time when a payment device is activated in SiteKiosk (Windows):
A session starts with the log message 2003:
[SiteCash] Beginning session (Available money: <Amount>, Access control status: Negative),
and ends with message 2004:
[SiteCash] Session ended. Total revenue: <Amount> Duration: <Duration>
Usage Time:
The time stamp of the log entries for session start and session end will be used to calculate the usage time
2. Session counting and usage time when no payment device is activated in SiteKiosk:
The session starts with one of the following log messages:
1001 [SiteKiosk] started
1007 [SiteKiosk] Screen Saver deactivated
The session ends with one of the following log messages:
1002 [SiteKiosk] closed
1003 [SiteKiosk] abnormal program termination
1006 [SiteKiosk] Screen Saver activated after <Interval> seconds
Exceptions:
If there is no activity between SiteKiosk startup and screen saver activation (the browser remains on the start page URL) this session will not be counted.
Usage Time:
The time stamp of the log entries for session start and session end will be used to calculate the usage time
Additionally the (screen saver) Idle time will be discounted from the session time.
Exceptions:
If there is no activity between SiteKiosk startup and screen saver activation (the browser remains on the start page URL) this session time will not be counted.
Otherwise the session (time) count will start with the second “[SiteKiosk] Navigation:” log entry after “[SiteKiosk] started”.
B. General Runtime accounting
The Runtime is the total run time of the SiteKiosk application
1001 [SiteKiosk] started
1002 [SiteKiosk] closed
For example:
1001 08:00 [SiteKiosk] started
1004 08:00 [SiteKiosk] Navigation: http://www.provisio.com/
...
1006 08:10 [SiteKiosk] Screen Saver activated after 300 seconds
1007 12:45 [SiteKiosk] Screen Saver deactivated
...
1006 13:05 [SiteKiosk] Screen Saver activated after 300 seconds
1007 14:45 [SiteKiosk] Screen Saver deactivated
...
1002 15:00 [SiteKiosk] closed.
These results two sessions (from 12:45 to 13:00 and from 14:45 to 15:00)
The total runtime is 7 hours
The usage time is 30 minutes
1001 08:00 [SiteKiosk] started
1004 08:00 [SiteKiosk] Navigation: http://www.provisio.com/
1004 08:02 [SiteKiosk] Navigation: ....
...
1006 08:10 [SiteKiosk] Screen Saver activated after 300 seconds
1007 12:45 [SiteKiosk] Screen Saver deactivated
...
1006 13:05 [SiteKiosk] Screen Saver activated after 300 seconds
1007 14:45 [SiteKiosk] Screen Saver deactivated
...
1002 15:00 [SiteKiosk] closed.
These results three sessions (from 08:02 to 8:05, from 12:45 to 13:00 and from 14:45 to 15:00)
The total runtime is 7 hours
The usage time is 33 minutes