dotnet/aspnetcore

Ability to monitor circuit activity

SteveSandersonMS opened this issue · 6 comments

SteveSandersonMS commented

Ability to monitor circuit activity so that circuits can then be terminated as appropriate. Provide callbacks when an event, JS interop call, or other activity happens on the circuit.

The ability to terminate circuits from client/server is tracked separately by #17866.

Split out from #27885

msftbot commented

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

msftbot commented

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

mkArtakMSFT commented

Moving this out of 6.0 to make room for Razor tooling asks for the Razor compiler.

msftbot commented

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

vflame commented

Is it possible to access Blazor's signalr hub/hubcontext to disconnect clients and to override the OnConnectedAsync and OnDisconnectedAsync events as a workaround? How about making the HttpContext used to establish the underlying signalr connection available when a circuit is opened/up?