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
HTTP 101 indicates that the server is switching protocol, this means that the duration of the request is most likely no longer a relevant metric in the HTTP context. Often this results into the connection being upgraded to a websocket which can lasts many minutes, instantly carrying the average processing time over the web_log_web_slow threshold when it closes and appears in the log. This completely ruins the graph, making it impossible to use and also triggers warning and critical alerts depending on the traffic and time the socket was open.
Expected behavior
HTTP 101 requests should be omitted from the web_log.request_processing_time log by default. I shouldn't have to dig into any custom configuration to not be spammed with warning and critical alerts for using websockets on my server, nor should they prevent me from diagnosing actual delays on my server.
Steps to reproduce
Open a websocket using any software that supports it
Close the websocket after sufficient time to raise your average significantly
Watch web_log.request_processing_time spike unnecessarily and trigger either warning or critical alerts for no reason
...
Bug description
HTTP 101 indicates that the server is switching protocol, this means that the duration of the request is most likely no longer a relevant metric in the HTTP context. Often this results into the connection being upgraded to a websocket which can lasts many minutes, instantly carrying the average processing time over the web_log_web_slow threshold when it closes and appears in the log. This completely ruins the graph, making it impossible to use and also triggers warning and critical alerts depending on the traffic and time the socket was open.
Expected behavior
HTTP 101 requests should be omitted from the web_log.request_processing_time log by default. I shouldn't have to dig into any custom configuration to not be spammed with warning and critical alerts for using websockets on my server, nor should they prevent me from diagnosing actual delays on my server.
Steps to reproduce
...
Installation method
kickstart.sh
System info
Netdata build info
Additional info
No response
The text was updated successfully, but these errors were encountered: