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.

Sign up for GitHub

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

Jump to bottom

Need to log unit action activity without enabling DEBUG logging #346

Closed
ryan-beisner opened this issue Aug 26, 2019 · 1 comment
Closed

Need to log unit action activity without enabling DEBUG logging #346

ryan-beisner opened this issue Aug 26, 2019 · 1 comment

Comments

@ryan-beisner
Copy link
Contributor

There are certain activities which I need to log in OpenStack Charm testing, but they are set in libjuju at the DEBUG level. The DEBUG level is hyper-verbose, with tons of Watcher and Pinger noise. While that is helpful when triaging tricky issues, it prevents us from seeing some useful log messages because we can't enable DEBUG everywhere on all test runs due to the noise level.

I'm proposing to shift a number of log.debug() entries to a log.info() level to improve the general observability and UX.
ryan-beisner pushed a commit to ryan-beisner/python-libjuju that referenced this issue Aug 26, 2019
Lower the log level to INFO for common test activities
8460317 
Closes: juju#346
@ryan-beisner ryan-beisner mentioned this issue Aug 26, 2019
Closed
@juanmanuel-tirado
Copy link
Contributor

This was already fixed in #347

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Lower the log level to INFO for common test activities ryan-beisner/python-libjuju
2 participants
@juanmanuel-tirado @ryan-beisner