Error & Critical level logging issue

[op]

Error & Critical level logging issue

[allengeorge]

Interesting - I'm noticing this for "INFO" as well...

[emilevauge]

It seams to be related to the logging level.
Here is the results using example with level DEBUG:

go run test.go
debug ******
14:34:30.005 main ▶ DEBU 001 debug ******
info
14:34:30.005 main ▶ INFO 002 info
notice mlhj
14:34:30.006 main ▶ NOTI 003 notice mlhj
warning
14:34:30.006 main ▶ WARN 004 warning
err
14:34:30.006 main ▶ ERRO 005 err
crit
14:34:30.006 main ▶ CRIT 006 crit

And using level CRITICAL:

go run test.go
14:35:10.744 main ▶ DEBU 001 debug ******
14:35:10.744 main ▶ INFO 002 info
14:35:10.744 main ▶ NOTI 003 notice mlhj
14:35:10.744 main ▶ WARN 004 warning
14:35:10.744 main ▶ ERRO 005 err
crit
14:35:10.744 main ▶ CRIT 006 crit

Anyone on this?

[emilevauge]

OK I found it...
This is because you don't have to copy/paste the example...

// Set the backends to be used.
logging.SetBackend(backend1Leveled, backend2Formatter)

should be

// Set the backends to be used.
logging.SetBackend(backend2Formatter)

Funny ;)

[op]

Great. Thanks @emilevauge