1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Hi InWaveStudio,
GameLift by default uploads game session logs every hour, and is provided to you via the GetGameSessionLogUrl API. If you have setup your log path correctly (via ProcessReady parameter), you should be able to see your game session logs there.
The quickest way to terminate your game session is by remote accessing your fleet instance and kill the process, see instructions. You might also be able to find the logs for your game session on the instance, especially you didn't setup log paths correctly or if your logs were truncated due size exceeding the limit for upload.
Slightly slower way is by setting your fleet's capacity to 0 instances (via UpdateFleetCapacity API), let all instances terminate, then re-spin up your instances.
回答済み 2年前
関連するコンテンツ
AWS公式更新しました 3年前
Thanks for your answer. I've set the log path via ProcessReady paremeter. But it seem like every game sessions all write log into single file at log path because when I open log file of some game sessions, it looks weird, sometime it has full log content, sometime it has just a part of log. Do I need to define log path for each game session to make it write correctly? ( like add game session id into general log path) ? Sorry for my bad English :D