fullstorydev / fullstorydev/grpcurl
How to trace request/response http calls
- Dominant language
- Go
- Stars
- 12.8k
- Forks
- 580
- Avg merge
- 1h 8m
- Merged PRs (30d)
- 5
Description
Hi,
Can you please tell me if there is any way of tracing the http calls during a grpc communication session ? To trace maybe the req/resp headers, body, etc ?
I tried to run grpcurl --v, but still we get only some basic info.
We are trying to connect to some grpc endpoints and with grpcurl everything works fine, but with our .net client is failing, so we would like to compare the requests and check for differences.
Thank you in advance.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing grpcurl's existing `--v` output and the request/response details it currently exposes. The issue names no files or tests; done would mean providing a way to compare HTTP headers and bodies from grpcurl with those sent by the .NET client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100