You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like MsQuic to have a built-in support for health probing, such that application layer can respond to the health signal and kick in mitigation steps if the underlying network stack is having trouble.
Production services usually have a need to be able to automatically mitigate situation in worst case scenario. So if MsQuic stack is having trouble in some outlier situation, application layer would want to be able to switch to kernel networking stack as a general fallback mechanism to ensure liveness.
Application layer can use certain error conditions emitted from MsQuic API for this purpose, of course. But it would be much more straightforward if there's a built-in health signaling API that simply gives a boolean signal to application layer.
Additional context
No response
The text was updated successfully, but these errors were encountered:
@pongba I'm trying to remember exactly what was needed here. Is the ask just to get a callback when the stack has entered the DoS mitigation mode internally?
Describe the feature you'd like supported
I would like MsQuic to have a built-in support for health probing, such that application layer can respond to the health signal and kick in mitigation steps if the underlying network stack is having trouble.
Production services usually have a need to be able to automatically mitigate situation in worst case scenario. So if MsQuic stack is having trouble in some outlier situation, application layer would want to be able to switch to kernel networking stack as a general fallback mechanism to ensure liveness.
Application layer can use certain error conditions emitted from MsQuic API for this purpose, of course. But it would be much more straightforward if there's a built-in health signaling API that simply gives a boolean signal to application layer.
Additional context
No response
The text was updated successfully, but these errors were encountered: