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
Add TROUBLESHOOTING.md #15940
Add TROUBLESHOOTING.md #15940
Conversation
|
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a great idea!! We can eliminate one round trip on the community mailing thread since asking for trace is usually the first thing that happens.
I have some ideas to build this doc out too
TROUBLESHOOTING.md
Outdated
|
||
## GRPC_VERBOSITY | ||
|
||
`GRPC_VERBOSITY` is used to set the minimum level of log messages printed by gRPC (supported values are `DEBUG`, `INFO` and `ERROR`). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add: "If this environment variable is unset, only ERROR logs will be printed"
TROUBLESHOOTING.md
Outdated
# Print info about invocations of low-level C core API. | ||
# Note that trace logs of log level DEBUG won't be displayed | ||
# as GRPC_VERBOSITY and GRPC_TRACE are 2 independent settings. | ||
GRPC_TRACE=api ./helloworld_application_using_grpc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Setting trace w/o verbosity does not accomplish much, since all the tracers use the INFO level of printing.
To test this, I ran
GRPC_TRACE=all bins/opt/h2_full_test simple_request
And nothing was output
|
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.