Skip to content
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

Feature request to add correlation id to SignalR clients #59156

Open
1 task done
vicancy opened this issue Nov 26, 2024 · 0 comments
Open
1 task done

Feature request to add correlation id to SignalR clients #59156

vicancy opened this issue Nov 26, 2024 · 0 comments
Labels
area-signalr Includes: SignalR clients and servers

Comments

@vicancy
Copy link
Contributor

vicancy commented Nov 26, 2024

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.

Describe the solution you'd like

Azure SignalR team recently has some customers requesting for “reconnect” related metrics to evaluate the impact to their customers when the connections are interrupted by service maintenance events, for example, the latency between the disconnect and reconnect, the success rate of a connect attempt.

However, from the service side, it is currently a little bit hard to correlate the reconnects if the hubconnection restarts because the connectionId is changed. We currently try with the same “userId” and “IP”. I am wondering if it is valuable to append some “correlationid” to a HubConnection in the client SDK by default, so that we could track the lifetime of the HubConnection when it re-starts? It could also be used to correlate the negotiate request to the app server with the negotiate/connect request to the SignalR service.

Additional context

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added the area-signalr Includes: SignalR clients and servers label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-signalr Includes: SignalR clients and servers
Projects
None yet
Development

No branches or pull requests

1 participant