-
Notifications
You must be signed in to change notification settings - Fork 26
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
bug-fix: better configuration of plugin loggers + trace all algod requests #91
Conversation
Codecov Report
@@ Coverage Diff @@
## master #91 +/- ##
==========================================
+ Coverage 67.66% 69.31% +1.65%
==========================================
Files 32 36 +4
Lines 1976 2428 +452
==========================================
+ Hits 1337 1683 +346
- Misses 570 653 +83
- Partials 69 92 +23
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
lgr := log.New() | ||
lgr.SetOutput(p.logger.Out) | ||
lgr.SetLevel(p.logger.Level) | ||
lgr.SetFormatter(makePluginLogFormatter(string(pluginType), cfg.Name)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously, all plugin loggers were assigned "processor" as their source.
l.SetFormatter(makePluginLogFormatter(plugins.Processor, cfg.Name)) | ||
lgr := log.New() | ||
lgr.SetOutput(p.logger.Out) | ||
lgr.SetLevel(p.logger.Level) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Inheriting the log level from the pipeline
Summary
In preparing the bugfix in algorand/go-algorand#5449, I discovered that conduit's logger wasn't printing out at the log-level that I was expecting (TRACE). I made some minor fixes to address this problem and also added the traces that I found helpful. Finally, a couple of logs were missing the received error from algod, so I added these.
Test Plan
CI + local testing