Describe the solution you'd like
Can we have response_size_histogram inside the opentelemetry-instrumentation-asgi logic?
Currently, we do have access to content-length header from the response inside the OpenTelemetryMiddleware, so it would be beneficial that we can have the ability to record response_size like duration.
Describe alternatives you've considered
Currently, I'm thinking about disable the FastAPI auto instrumentation and implement both response size and duration.
Additional context
The only instrumentator I could find that have the ability to record response_size is opentelemetry-instrumentation-tornado (HTTP_SERVER_RESPONSE_SIZE).
Let me know if that makes sense.
Thanks.
Describe the solution you'd like
Can we have
response_size_histograminside theopentelemetry-instrumentation-asgilogic?Currently, we do have access to
content-lengthheader from the response inside theOpenTelemetryMiddleware, so it would be beneficial that we can have the ability to record response_size like duration.Describe alternatives you've considered
Currently, I'm thinking about disable the FastAPI auto instrumentation and implement both response size and duration.
Additional context
The only instrumentator I could find that have the ability to record response_size is
opentelemetry-instrumentation-tornado(HTTP_SERVER_RESPONSE_SIZE).Let me know if that makes sense.
Thanks.