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

Move ohai to structured logging #1161

Merged
merged 2 commits into from
Mar 17, 2018
Merged

Move ohai to structured logging #1161

merged 2 commits into from
Mar 17, 2018

Conversation

thommay
Copy link
Contributor

@thommay thommay commented Mar 14, 2018

This does two things:
it moves away from the old model of using a log module throughout, to injecting the logger in to the various classes. This means that each class can attach metadata to the logger, allowing - in future - us to add tooling to drill into specific plugins or similar.
It converts (the second commit) everything to be at log level trace rather than debug. In general, a cookbook author does not give two hoots about which ohai plugins are loaded or in we failed to load a hint on azure, and we should respect their attention.

Thom May added 2 commits March 15, 2018 16:53
This allows us to bubble up a single logging object with metadata
throughout ohai, rather than the current janky way. We also move some
debug output to trace.

Signed-off-by: Thom May <thom@chef.io>
Signed-off-by: Thom May <thom@chef.io>
@thommay thommay changed the title [WIP] Move ohai to structured logging Move ohai to structured logging Mar 16, 2018
@@ -31,7 +31,7 @@
# Notification: kqueue
# Architecture: amd64
# Disabled: none
# Misc: softdebug
# Misc: softtrace
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

find/replace

@tas50 tas50 merged commit f443b20 into master Mar 17, 2018
@tas50 tas50 deleted the tm/inject_log branch April 17, 2018 17:36
@lock
Copy link

lock bot commented Jan 25, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants