Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign up/flags does not reflect log.level flag #2330
Comments
brian-brazil
added
the
kind/bug
label
Apr 4, 2017
This comment has been minimized.
This comment has been minimized.
|
Confirmed. |
Conorbro
referenced this issue
Apr 25, 2017
Merged
Added function to assign log level flag after parsing #80
juliusv
referenced this issue
Apr 26, 2017
Closed
Log level flag not picked up - "-log.level=debug" - in 1.4 #24
Conorbro
referenced this issue
Apr 27, 2017
Merged
Updated vendoring for log level reporting issue #2660
brian-brazil
closed this
in
#2660
Apr 27, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
cburroughs commentedJan 9, 2017
What did you do?
-log.level=erroror-log.level=debug/flagsWhat did you expect to see?
log.levelon/flagsto have the value I set.What did you see instead? Under which circumstances?
log.levelon/flagsalways shows"info"It is unclear to me if this is purely a reporting issue, or if the log level is not being used correctly. When I set the log level to
errorI see noINFOmessages onstderr(as expected), but if I set it todebugthe only additional message I see isDEBU[0011] Target manager stopped source=targetmanager.go:89on shutdown.Environment
# uname -srm Linux 4.3.0 x86_64at
debug