-
Notifications
You must be signed in to change notification settings - Fork 759
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
Labels
enhancement
New feature or request
Comments
github-actions
bot
added
the
Stale
Issues and pull requests which have been flagged for closing due to inactivity
label
Jan 27, 2022
cijothomas
removed
the
Stale
Issues and pull requests which have been flagged for closing due to inactivity
label
Jan 27, 2022
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
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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)
The text was updated successfully, but these errors were encountered: