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

Use OTel SDK's self-diagnostics - managed code - document troubleshooting #959

Closed
pellared opened this issue Jul 20, 2022 · 4 comments
Closed
Milestone

Comments

@pellared
Copy link
Member

pellared commented Jul 20, 2022

We should use OTel SDK's self-diagnostics for internal logging.

@nrcventura
Copy link
Member

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.

  1. Figuring out which directory to place this special file in
  2. Having enough permissions to get a file added to that directory

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.

@nrcventura nrcventura added this to the 0.4.0-beta milestone Jul 27, 2022
@nrcventura nrcventura modified the milestones: 0.4.0-beta, 0.5.0-beta Sep 21, 2022
@pjanotti pjanotti modified the milestones: 0.5.0-beta, 0.6.0-beta Nov 2, 2022
@pellared pellared modified the milestones: 0.6.0-beta, 0.7.1, 0.7.0 Nov 16, 2022
@Kielek
Copy link
Contributor

Kielek commented Jan 19, 2023

Only describe in troubleshooting doc how to do it.

@Kielek Kielek changed the title Use OTel SDK's self-diagnostics - managed code Use OTel SDK's self-diagnostics - managed code - document troubleshooting Jan 19, 2023
@Kielek Kielek modified the milestones: 0.5.2, 1.0.0-rc Jan 19, 2023
@lachmatt
Copy link
Contributor

SdkSelfDiagnosticsEventListener fulfills similar purpose.
I think with recent logging improvements to internal logger, this is no longer needed.

@Kielek
Copy link
Contributor

Kielek commented Mar 23, 2023

Closing per previous comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

5 participants