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
In applications like lotus where there is a long list of log systems from every layer of the stack, applying INFO to all of them is not very useful as it provides too much information at the lower layers and not enough, in certain cases, at the higher levels. Having the ability to configure the levels in a way that is persistent between restarts of the application is important when the logs are collected into systems like Loki or Elastisearch and operators don't have direct access to running application.
The text was updated successfully, but these errors were encountered:
This would be very helpful for me as well, changing the log level of just one subsystem via config/env/flag in an ipfs daemon would reduce lots of complexity in log running systems.
Ex:
GOLOG_LOG_LEVEL=error,foo=info,bar=debug
This will set the default log-level to error, foo's log-level o info,
and bar's log-level to debug.
fixes#100
Ex:
GOLOG_LOG_LEVEL=error,foo=info,bar=debug
This will set the default log-level to error, foo's log-level o info,
and bar's log-level to debug.
fixes#100
In applications like
lotus
where there is a long list of log systems from every layer of the stack, applyingINFO
to all of them is not very useful as it provides too much information at the lower layers and not enough, in certain cases, at the higher levels. Having the ability to configure the levels in a way that is persistent between restarts of the application is important when the logs are collected into systems like Loki or Elastisearch and operators don't have direct access to running application.The text was updated successfully, but these errors were encountered: