Skip to content

[H/3] Distributed Tracing / Telemetry #104783

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ManickaP opened this issue Jul 12, 2024 · 1 comment · Fixed by #114083
Closed

[H/3] Distributed Tracing / Telemetry #104783

ManickaP opened this issue Jul 12, 2024 · 1 comment · Fixed by #114083
Labels
area-System.Net.Http enhancement Product code improvement that does NOT require public API changes/additions
Milestone

Comments

@ManickaP
Copy link
Member

Right now, we emit very short telemetry / activity "wait for connection" for every H/3 request, even if the request is immediately handled by the connection and doesn't wait. Follow queueStartingTimestamp in:

long queueStartingTimestamp = HttpTelemetry.Log.IsEnabled() || Settings._metrics!.RequestsQueueDuration.Enabled ? Stopwatch.GetTimestamp() : 0;

We shouldn't emit those events (if the connection can handle the request immediately). We do have _availableRequestStreamsCount in H3 connection which we could use:

Also, right now the code differs from H/2 pool because of the internal waiting in S.N.Quic OpenOutboundStreamAsync.

connection = await http3ConnectionWaiter.WaitWithCancellationAsync(cancellationToken).ConfigureAwait(false);

vs
connection = await http2ConnectionWaiter.WaitForConnectionAsync(request, this, async, cancellationToken).ConfigureAwait(false);

So if we can bring the code closer to H/2 with this change, it would be an added bonus.

Original discussion: #103922 (comment)

@ghost ghost added the area-System.Net.Http label Jul 12, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Jul 12, 2024
@ManickaP ManickaP added enhancement Product code improvement that does NOT require public API changes/additions and removed untriaged New issue has not been triaged by the area owner labels Jul 12, 2024
Copy link
Contributor

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

@ManickaP ManickaP added this to the 10.0.0 milestone Jul 12, 2024
@github-actions github-actions bot locked and limited conversation to collaborators May 25, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Net.Http enhancement Product code improvement that does NOT require public API changes/additions
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant