-
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
Remove & replacewebpa-common/logging
&go-kit/log
& go-kit/kit/log
with uber zap
#708
Remove & replacewebpa-common/logging
&go-kit/log
& go-kit/kit/log
with uber zap
#708
Conversation
@johnabass hey john I'm not sure how we envisioned `Enrich` to interact with go-kit sd.Instancer. It's not clear how `Instancer` would enrich logging atm Here's a past note we left behind // Instancer is the go-kit sd.Instancer which sent this event. This instance can be used to enrich // logging via sallust.Enrich.
Vulnerable Libraries (3)
More info on how to fix Vulnerable Libraries in Go. 👉 Go to the dashboard for detailed results. 📥 Happy? Share your feedback with us. |
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.
good job!
reverting service/consul packages back to use gokit log because of gokitzk.NewRegistrar |
…f gokitzk.NewRegistrar
Kudos, SonarCloud Quality Gate passed! |
What's included:
logging
package and replace go-kit/kit/log & go-kit/log withzap
#686bookkeeping
package tests #465closes #686
closes #465
related to #655
Dependent on:
webpa-common/logging
Utilities sallust#39webpa common/logging
,go-kit/log
withzap
argus#333