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
Hello.
I have a suggestion to add support to check the response time for the WebSocket.
Currently, there's only timeout logic which provides no details upon failure. I believe that having timeout and response time check will be more useful and provide a more comprehensive way to analyze failed checks. This approach would provide an upper bound with the timeout parameter, while also allowing for check failure based on excessive response times, thereby enabling more detailed logging and analysis.
Do it in the same way as for HTTP .check(responseTimeInMillis...)
Hello.
I have a suggestion to add support to check the response time for the WebSocket.
Currently, there's only timeout logic which provides no details upon failure. I believe that having timeout and response time check will be more useful and provide a more comprehensive way to analyze failed checks. This approach would provide an upper bound with the timeout parameter, while also allowing for check failure based on excessive response times, thereby enabling more detailed logging and analysis.
Do it in the same way as for HTTP
.check(responseTimeInMillis...)
How does sound this idea?
Thanks!
The text was updated successfully, but these errors were encountered: