Lag when adding aws xray daemon

We saw an increase of about 3 seconds when we started to send transactions to the aws xray daemon from our spring boot application. While debugging with `time nc -vz -u localhost 2000` we see there is a 3s duration for the connection when we add the aws xray daemon as a sidecar to our debug pod. We get the same result when we try to run the aws xray daemon as a deployment. We tried to change the port but got the same result. Is there a way to try to use TCP protocol instead of UDP protocol for the aws xray daemon or is there something else we can try to remove the lag we noticed after we added the aws xray daemon?

Start with the AWS X-Ray daemon's UDP listener on port 2000 and reproduce the reported timing in the Kubernetes debug-pod sidecar and deployment setups. Compare the `time nc -vz -u localhost 2000` result with each setup and investigate whether the delay is tied to connection probing or daemon traffic. Done means identifying the cause and documenting a verified workaround or whether TCP is supported.

Written by the indexing model from the issue text.