-
Notifications
You must be signed in to change notification settings - Fork 419
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
question: can you make log.UseLogger public API? #1331
Comments
Hi @gbbr. I'm sorry, I forgot to mention I want to change the logger from This |
I'll add that to the profiler to match the tracer 👍 |
nsrip-dd
added a commit
that referenced
this issue
Jun 9, 2022
nsrip-dd
added a commit
that referenced
this issue
Sep 14, 2022
Make the internal UseLogger function public so that users can specify a single logger for all tracer and profiler logs. Right now the profiler doesn't have a configurable logger, and the tracer has the WithLogger option, which sets the global logger anyway. Fixes #1331.
knusbaum
pushed a commit
that referenced
this issue
Sep 21, 2022
Make the internal UseLogger function public so that users can specify a single logger for all tracer and profiler logs. Right now the profiler doesn't have a configurable logger, and the tracer has the WithLogger option, which sets the global logger anyway. Fixes #1331.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello everyone.
I think would be awesome if we could change the logger like you guys did in the tests, using the function
UseLogger
:dd-trace-go/internal/log/log.go
Line 41 in 87a049b
But we can't do it, internal pkg means internal stuff indeed.
And we have a problem 'cause the current log pattern is way different from what we're using here.
We're disabling for a while.
Is there any workaround to inject our logger into it?
Thanks.
The text was updated successfully, but these errors were encountered: