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
Is your feature request related to a problem? Please describe.
There does not seem to be any documentation on how view headers from a gRPC request.
For example, the Host gets set for apmhttp (See #280) but not for apmgrpc. Why not, when grpc is over an HTTP2 connection?
Describe the solution you'd like
I would love if it could store the same request headers and the same response headers as apmhttp modules does. Thus, its easy to see standard headers from the apmgrpc interceptors. Ideality, it should happen in getIncomingMetadataTraceContext since it already pulls the Request Metadata.
Describe alternatives you've considered
Alternatives include creating our own interceptor that runs after the apmgrpc interceptor. It adds the headers to the parent span.
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
There does not seem to be any documentation on how view headers from a gRPC request.
For example, the
Host
gets set forapmhttp
(See #280) but not forapmgrpc
. Why not, when grpc is over an HTTP2 connection?Describe the solution you'd like
I would love if it could store the same request headers and the same response headers as
apmhttp
modules does. Thus, its easy to see standard headers from theapmgrpc
interceptors. Ideality, it should happen ingetIncomingMetadataTraceContext
since it already pulls the Request Metadata.Describe alternatives you've considered
Alternatives include creating our own interceptor that runs after the
apmgrpc
interceptor. It adds the headers to the parent span.Additional context
The text was updated successfully, but these errors were encountered: