I find debugging gRPC requests can be a pain because debugging proxies like Fiddler/Charles don’t natively understand gRPC. So I built grpc-dump to try and make this easier by doing interception at the gRPC level rather than the HTTP level.
Without requiring any client/server changes, grpc-dump transparently intercepts traffic on your machine and logs a JSON stream of all gRPC(-Web) requests that are made. This stream/dump is already useful for debugging but I’ve also started adding tools like grpc-fixture which uses this dump and responds to future client requests with the saved server responses from the dump.
1 comment
[ 3.2 ms ] story [ 10.1 ms ] threadWithout requiring any client/server changes, grpc-dump transparently intercepts traffic on your machine and logs a JSON stream of all gRPC(-Web) requests that are made. This stream/dump is already useful for debugging but I’ve also started adding tools like grpc-fixture which uses this dump and responds to future client requests with the saved server responses from the dump.