Concurrent access log
- Log Name : hive_concurrent_user_log
- The fields in the table below do not include fields that are required when creating logs or employing analytics tools.
- You can choose whether or not to send Hive’s client co-access logs by selecting the ‘Minimize Network Communication’ option in the Hive console.
(Path: Hive Console > App Center > Manage Project > Hive Product Settings)
(Reference : https://developers.withhive.com/operation/appcenter/gamemanagement/#list02-05)
| Field Name | Description | Data Type |
| appIndex | Numeric appIndex that corresponds to appId in App Center | INTEGER |
| sessionId | A key value that identifies it as a single client session | INTEGER |
| playtime | Time left in the foreground between ccu log transmission words (in seconds) Because it is based on the foreground, the numbers rise to 0, 120, 240, and 360 |
INTEGER |
| playOutTime | Background time. Time not actually played | INTEGER |
| prevLatency | When transmitting concurrently in the previous cycle, the Request-Response response time of this https protocol was milliseconds (1/1000th of a second) | INTEGER |
| timestampMillis | The current client time value in milliseconds (1/1000th of a second) while calling Active | INTEGER |
| timestampMillisStandby | The current client time value in milliseconds (1/1000th of a second) when calling StandBy | INTEGER |
| activeTime | Actual playtime (seconds) since the previous concurrent transmission * Measures just foreground status, with a maximum of 120 seconds | INTEGER |