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

Outputting OTEL Self Diagnostics log to Console #2732

Closed
venkatramanchandirasekaran opened this issue Dec 8, 2021 · 2 comments
Closed

Outputting OTEL Self Diagnostics log to Console #2732

venkatramanchandirasekaran opened this issue Dec 8, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@venkatramanchandirasekaran

Feature Request

Outputting OTEL Self Diagnostics log to Console instead of file. Refer this GIT hub issue for more details - #2699 (comment)

Before opening a feature request against this repo, consider whether the feature
should/could be implemented in the other OpenTelemetry client
libraries
. If so, please open an issue on
opentelemetry-specification

first.

Is your feature request related to a problem?
Yes. When GRPC calls are failing, we would like to have visibility in to how often it happens. Since we are using open shift containers, we would like to have OTEL Self Diagnostics log to Console so we can pull these in to Splunk.

If so, provide a concise description of the problem.

Describe the solution you'd like:
see above

What do you want to happen instead? What is the expected behavior?
see above

Describe alternatives you've considered.
We could write our own listener but this option should be provided by framework, so it can benefit all customers using the framework.

Which alternative solutions or features have you considered?
see above

Additional Context

Add any other context about the feature request here.
Refer this GIT hub issue for more details - #2699 (comment)

@venkatramanchandirasekaran venkatramanchandirasekaran added the enhancement New feature or request label Dec 8, 2021
@github-actions github-actions bot added the Stale Issues and pull requests which have been flagged for closing due to inactivity label Jan 27, 2022
@cijothomas cijothomas removed the Stale Issues and pull requests which have been flagged for closing due to inactivity label Jan 27, 2022
@Code-Grump
Copy link

I keep finding myself implementing this pattern. In Kubernetes it's not very convenient to output to a file - writing to stderr tends to be a much simpler solution to this.

A ConfigMap would still let us use the config file to switch this on and off during runtime, but perhaps we could add an "output" setting to switch between file output and stderr?

{
    "Output": "stderr"
    "LogLevel": "Warning"
}

@cijothomas
Copy link
Member

#3881 is coming, which basically means, logs can be routed anywhere like console!

Closing this as a duplicate. Feel free to use #3881 for comments/feedbacks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants