Server should log to stdout by default

[jamielennox]

In a docker or container management world the container should not be responsible for maintaining its own log directory. Particularly when this is managed in a cluster situation I want to use the docker logging that i can configure at a cluster level rather than have to deal with volume mounts on individual containers.

Under the hood teamcity server should be log4j so i'd expect people will want a way to override these settings anyway, but by default it's best practice to just log to stdout and then let your container runtime manage sending logs to the right place.

[flaw]

Any news on this? The current behavior makes integration with automatic log collection tools rather cumbersome. We have tooling which neatly collects logs from all the workloads we have running in our Kubernetes cluster, but TeamCity with it's non-standard logging setup doesn't play nicely with that.

[kir]

Hi, I've filed this request to our main tracker: https://youtrack.jetbrains.com/issue/TW-67552

[dzwicker]

We have ovritten the log4j config to just log everthing to the stdout. But three files remain in the logs-directory

• teamcity-wrapper.log
• teamcity-mavenServer.log
• teamcity-javaLogging-yyyy-mm-dd.log

[eblfo]

@dzwicker do you have any more details ? which log4j file did you modify ?