When a client used Connection: keep-alive header, only the first request was being captured. Subsequent requests were using the same context and so we were adding data in the same first span that was ended.
We are setting the context as null when we end the span, so that whenever a new request comes, no matter, it will create a new context and a new span.
Tested this for both connection keep-alive and close.
When a client used
Connection: keep-aliveheader, only the first request was being captured. Subsequent requests were using the same context and so we were adding data in the same first span that was ended.We are setting the context as null when we end the span, so that whenever a new request comes, no matter, it will create a new context and a new span.
Tested this for both connection keep-alive and close.