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

[FEAT] Set log_level via environment variables #732

Open
instantdreams opened this issue Dec 17, 2024 · 0 comments
Open

[FEAT] Set log_level via environment variables #732

instantdreams opened this issue Dec 17, 2024 · 0 comments

Comments

@instantdreams
Copy link

instantdreams commented Dec 17, 2024

Feature Description
I wish to be able to adjust the log level of Scrutiny (web, collector, omnibus, doesn't matter) using environment variables (for docker) or flags (for bare metal).

At the moment, creating a scrutiny.yaml file with the following entries works but is clunky when I wish to keep my configuration in environment variables only:

version: 1
log:
  file: ''
  level: WARN

Feature Solution
Implement variable SCRUTINY_LOG_LEVEL with the usual enums of Trace, Debug, Info, Warn, Error, Critical, None or similar as supported by Scrutiny application. Apply a similar flag to the command line of --log-level.

Variable SCRUTINY_LOG_LEVEL to apply to all flavours of Scrutiny - omnibus, web, collector - and restrict the output to the appropriate level.

Additional Context
A list of all environment variables would be useful for the docs section, too!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant