-
Notifications
You must be signed in to change notification settings - Fork 93
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
Use OTel SDK's self-diagnostics - managed code - document troubleshooting #959
Comments
One thing that I do not like about this approach, based on the current functionality in that feature, is that it requires someone to drop a file in a particular location to get the log files generated. The problems that I have seen people experience with that approach are the following.
If we had the ability to control these log files via environment variables, I think that would improve the experience, and simplify things for us and our users. |
Only describe in troubleshooting doc how to do it. |
SdkSelfDiagnosticsEventListener fulfills similar purpose. |
Closing per previous comment. |
We should use OTel SDK's self-diagnostics for internal logging.
The text was updated successfully, but these errors were encountered: