SignalR .NET client telemetry

[JamesNK]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

The SignalR .NET client doesn't have telemetry. This is a gap compared to .NET clients for HTTP and RPC. HttpClient and GrpcChannel have metrics and activities for tracking usage.

Describe the solution you'd like

SignalR .NET client should have metrics:

• Conenction-level metrics. This would be similar to the metrics offered on the server.
• Invocation-level metrics. e.g. current active invocations, invocation duration

And it should create an activity for invocations so they show up in tracing.

Additional context

No response

[BrennanConroy]

And it should create an activity for invocations so they show up in tracing.

Tracked by #51557

SignalR .NET client should have metrics:

Tracked by #2461
If you have specific ones add them to the issue.

[JamesNK]

I made this issue because so far all the discussion I've seen is about server improvements. It can be closed if the other metrics and tracing issues cover both client and server.

[adityamandaleeka]

I suggest moving any client-specific stuff from #2461 to here and closing that one. That issue is long and largely stale.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.