kiska
/
transfer.sh
1
0
Fork 2
Code Issues 0 Pull Requests 0 Releases 11 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
316 Commits
9 Branches
34 MiB
 
 
 
Tree: 61a4b4fe33
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '61a4b4fe33'
${ noResults }
transfer.sh/vendor/google.golang.org/grpc/examples/features/debugging
Andrea Spacca ec086b4eb3 Bump google.golang.org/api 5 years ago
..
client Bump google.golang.org/api 5 years ago
server Bump google.golang.org/api 5 years ago
README.md Bump google.golang.org/api 5 years ago

README.md

Debugging

Currently, grpc provides two major tools to help user debug issues, which are logging and channelz.

Logs

gRPC has put substantial logging instruments on critical paths of gRPC to help users debug issues. The Log Levels doc describes what each log level means in the gRPC context.

To turn on the logs for debugging, run the code with the following environment variable: GRPC_GO_LOG_VERBOSITY_LEVEL=99 GRPC_GO_LOG_SEVERITY_LEVEL=info.

Channelz

We also provides a runtime debugging tool, Channelz, to help users with live debugging.

See the channelz blog post here (link) for details about how to use channelz service to debug live program.

Try it

The example is able to showcase how logging and channelz can help with debugging. See the channelz blog post linked above for full explanation.

go run server/main.go

go run client/main.go