You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our gRPC and in HTTP handlers we're using request IDs in headers to correlate the tree of requests that "spawn" out of an original request.
Golang has an awesome /debug/requests and /debug/events, which are incredibly helpful, especially for gRPC.
Ideally, we'd move from our custom middleware/interceptors that we use with request ID to propagate (in our internal network) as trace spans. Unfortunately, you cannot read the trace ID in order for it to be serialized into headers. This would make it possible to have a consistent view of request IDs in our logs and /debug/requests.
Also it would make it easier to ship stuff to DapperCloud Trace :)
The text was updated successfully, but these errors were encountered:
quentinmit
changed the title
x/net/trace usable: add GetSpanId and GetTraceId for cross-request tracking.
x/net/trace: add GetSpanId and GetTraceId for cross-request tracking.
Sep 13, 2016
In our gRPC and in HTTP handlers we're using request IDs in headers to correlate the tree of requests that "spawn" out of an original request.
Golang has an awesome
/debug/requests
and/debug/events
, which are incredibly helpful, especially for gRPC.Ideally, we'd move from our custom middleware/interceptors that we use with request ID to propagate (in our internal network) as trace spans. Unfortunately, you cannot read the trace ID in order for it to be serialized into headers. This would make it possible to have a consistent view of request IDs in our logs and
/debug/requests
.Also it would make it easier to ship stuff to
DapperCloud Trace :)The text was updated successfully, but these errors were encountered: