Thanks for the reply. This is the problem, we skip this tracer, commenting on it, like this:
#TraceOneMethodWithParametersIfFlagged: SocketTracing SocketConnectTracer InternalConnect"SocketConnectTracer"
Apparently the socket tracing metrics were not affected. Now the challenge is to justify the workaround, explain to the client what makes this method and if this problem is a bug or something that could occur and so the workaround would be definitive.