We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now, when I use the default exporter, for logs traces and metrics, I get a couple console statements from diag.info
diag.info
OTEL_LOGS_EXPORTER is empty. Using default otlp exporter. OTEL_TRACES_EXPORTER is empty. Using default otlp exporter.
It is frustrating to have to see this as it discourages using defaults. You might try to do something else just to get rid of the output.
I would like to not see things in console output about using defaults, and not have to adjust diag settings to do so.
there are also some glitches trying to set the level from info to warning to avoid the same. Looks like this:
Current logger will be overwritten from Error --snip Current logger will overwrite one already registered from Error --snip
related issue about undesired output when attempting to change the diag level to warning #4447
The text was updated successfully, but these errors were encountered:
Hi - yep i think we should not use info in that case. Let's change it to debug - @codefromthecrypt would that solve the issue?
Sorry, something went wrong.
No branches or pull requests
Is your feature request related to a problem? Please describe.
Right now, when I use the default exporter, for logs traces and metrics, I get a couple console statements from
diag.info
It is frustrating to have to see this as it discourages using defaults. You might try to do something else just to get rid of the output.
Describe the solution you'd like
I would like to not see things in console output about using defaults, and not have to adjust diag settings to do so.
Describe alternatives you've considered
there are also some glitches trying to set the level from info to warning to avoid the same. Looks like this:
Additional context
related issue about undesired output when attempting to change the diag level to warning #4447
The text was updated successfully, but these errors were encountered: