Support chunked request and response http dependency tracking about applicationinsights-dotnet-server HOT 1 CLOSED

Today we use following HTTP dependency tracking mechanisms:

1. .NET Fx: DiagnosticSource. The end event is fired when HttpResponseMessage is disposed i.e. after response is read. The issue is not relevant
2. .NET Fx: profiler: we instrumented OnEndGetResponse
3. .NET Core DiagnosticSource

For both p2 and p3 there are caveats.
HttpClient methods have an overload that takes HttpCompletionOptions that specify if the response should be read and buffered before returning the result. By default it is set to ResponseContentRead, i.e. response streams are buffered (up to some huge size).
So by default, we track time to last byte.

However, users can (and should for huge responses) supply HttpCompletionOptions.ResponseHeadersRead and then response body is not read or buffered before the user explicitly reads it. This is out of ApplicationInsights control and for now, users should track this extra time manually with StartOperation.

I'm closing this issue for now, as there is no work planned to address it. Please upvote and reopen if this affects you.

from applicationinsights-dotnet-server.