Open tisba opened 7 years ago
I just cannot wrap my head around, why exactly the HTTP status code could not be determined. As far as I can tell none
is the default in the http#status
record and for some reason ts_http_common:parse_status/2
was not called or did not update the value. Unfortunately I have not yet figured out, how to reliably reproduce that behavior.
For the reason size_rcv
is not counted, I guess we have to look around ts_client:handle_data_msg
. I think we do not call ts_mon:add
with size_rcv
in case we get too little data. Can you maybe help to trace this down, @nniclausse?
I'm still investigating what actually happens, but here is what I have observed so far.
error_no_http_status
status codes:1481819141.918814;<0.667.0>;1320;get;host.example.com;/path;error_no_http_status;0;57.704;-;;;
. I guess this happened because the target system was quite overloaded.size_rcv
reported intsung.log
was always 0 during the time we saw onlyerror_no_http_status
. It was okay before we saw theerror_no_http_status
responses.stats: {recvpackets,"os_mon@ip-172-31-8-102"} 1 4836.0 0.0 4836 205 1768.059190031152 321
See example stats dump from
tsung.log
:size_rcv
was exactly 0 andsize_sent
was non zero. That makes no sense for a ~20 minute period.My suspicion is, that the
size_rcv
is not properly calculated (or maybe even skipped?) whenerror_no_http_status
happened.