Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow per-system levels to be set in environment variable or file #100

Closed
lanzafame opened this issue Jul 23, 2020 · 1 comment · Fixed by #109
Closed

Allow per-system levels to be set in environment variable or file #100

lanzafame opened this issue Jul 23, 2020 · 1 comment · Fixed by #109
Labels
need/triage Needs initial labeling and prioritization

Comments

@lanzafame
Copy link
Contributor

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.

@lanzafame lanzafame added the need/triage Needs initial labeling and prioritization label Jul 23, 2020
@andrew
Copy link

andrew commented Nov 17, 2020

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.

Stebalien added a commit that referenced this issue Apr 17, 2021
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
Stebalien added a commit that referenced this issue Apr 17, 2021
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants