You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all log messages are written to stderr which means all messages are interpreted as error messages by aggregators/log-forwarders. For example, logs are displayed as errors by google stackdriver.
Although fix should be in logrus (sirupsen/logrus#403), they don't seem interested in fixing this. So, either this would need change of logging util or some workaround given in the thread.
Expected behavior
Based on log levels, they should be written to stdout or stderr.
Version
1.8
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently all log messages are written to stderr which means all messages are interpreted as error messages by aggregators/log-forwarders. For example, logs are displayed as errors by google stackdriver.
Although fix should be in
logrus
(sirupsen/logrus#403), they don't seem interested in fixing this. So, either this would need change of logging util or some workaround given in the thread.Expected behavior
Based on log levels, they should be written to stdout or stderr.
Version
1.8
The text was updated successfully, but these errors were encountered: