Default logging format different across architectures

[wsw70]

log.Debug("connection OK") outputs

• DEBU[0000] connection OK when compiled on or for Linux/amd64
• time="2018-05-30T09:38:26+02:00" level=debug msg="connection OK" when compiled on Windows 10

Is a different default behaviour between systems for the same code something expected?

(apologies if this is obvious - I am just starting with Go, coming from Python and JS)

[lepinkainen]

logrus is not detecting a TTY on Windows, so it defaults to TextFormatter.

[dgsb]

@wsw70 would you mind to try that again with a more recent version of logrus (v1.1.0) ? We have recently merged some improvement regarding terminal management on windows.

[jtnord]

seen this on the jenkins-x project with logrus 1.4.1

[jtnord]

this conditional just says screw windows regardless :)

[dgsb]

@wsw70 you may also want to use a JSONFormatter which will valid json for each trace.

[alex-yust]

Not only is the default format different across architectures, a Linux worker on Azure Pipelines (Ubuntu 16.04) also outputs JSON by default 8(

May be the reason to this is related to the fact that 'docker login' reports the worker's shell as 'non tty'.

[arxeiss]

I think it is related to colors as well.

var log = logrus.New()
log.Formatter = &logrus.TextFormatter{
	DisableColors: true,
}
log.Out = os.Stdout

log.Error("Starting the server")

Output: time="2020-10-21T14:14:07+02:00" level=error msg="Starting the server"

When I comment out the DisableColors

- 	DisableColors: true,
+ 	// DisableColors: true,

Output is: ERRO[0000] Starting the server and ERRO is in red color.