Only the last log file of a server is shown in the dashboard

Hello,

I can only see the last log file of a server in the dashboard, What is wrong with my configuration?

See the attached image for example of server logs:

My build configuration is:
-nographics -batchMode -port $$port$$ -queryport $$query_port$$ -logFile $$log_dir$$/Engine.log

Can you elaborate with what you were hoping to see? I’m not fully sure I understand your expectation when you say you see “only the last log file”.

I expect to see log file per server session. The log file is being truncated on every session and I’m losing loggings of all previous sessions.
I’d like to mention that I’m shutting down the server as the game session ends (Application.Quit), as suggested by the docs. Can it be reason? What is the best practice?

I think for every new allocation the log file is being recreated.
But I also would love to see a server log and an allocation log - so we have a better way to trace down problems. Because sometimes we run logic once and then we just clean up server states for allocation/deallocation.

Right @airburst_studios . This is exactly the problem. It’s impossible to trace down an issue if the server has already been allocated for another game session.

One thing you could do here is use the $$timestamp$$ variable in your build configuration, as documented here -Launch parameters

This value will contain the timestamp at which the server started, so in your case the launch parameters would look something like:

-nographics -batchMode -port $$port$$ -queryport $$query_port$$ -logFile $$log_dir$$/Engine-$$timestamp$$.log

2 Likes

Excellent! Exactly what I needed. Is there a retention policy or limits for logging? Every instance can take ~100k so it might consume some storage after a while.

Hey spikyworm5, have you seen our logging closed beta post ? This could be interesting for you.

Hi. That sounds great. Currently it is very hard to navigate the logs. I registered