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.
Currently, we only instrument the inbound/outbound RPC duration for client/server. It would be better if we also start instrumenting the inbound/outbound request/response sizes as we do for HTTP.
Describe the solution you'd like
I have a use case where I need to get the GRPC client request/response size metrics with similar attributes we have for RPC duration. I have already implemented this using ClientStreamTracer and an Interceptor for one of our services. Still, it would be great if it is available in Opentelemetry itself, and we can use it directly for all our services.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, we only instrument the inbound/outbound RPC duration for client/server. It would be better if we also start instrumenting the inbound/outbound request/response sizes as we do for HTTP.
Describe the solution you'd like
I have a use case where I need to get the GRPC client request/response size metrics with similar attributes we have for RPC duration. I have already implemented this using ClientStreamTracer and an Interceptor for one of our services. Still, it would be great if it is available in Opentelemetry itself, and we can use it directly for all our services.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: