Janek Lasocki-Biczysko

> I guess we could make something like, if it's defined, we set override, and pass in the necessary config. That could work, and would bring together the way we...

The following is a decent workaround until `ts-jest` supports this directly (if ever -- im still not sure if it's possible given how this behaviour is achieved in vanilla `jest`)...

Hi @rochdev - could you please provide an update on this ticket (ie. will any of the current efforts you're working on solve this?).

> At a minimum, it might be good to allow for `dogstatsd.host` to be an API option for `init()`, so that users can take advantage of the `socat` workaround [suggested...

> if you configure dd-trace to use UDS, I've got dd-trace configured to use UDS _for tracing_ (using `DD_TRACE_AGENT_URL=unix:///var/run/datadog/apm.socket`), but when I use that I don't get runtime metrics reported....

> Was it working before without UDS? Yes, it was working fine before (we had `DD_AGENT_HOST` configured correctly, and the agent was listening on 8125/udp and 8126) > The PR...

It may be worth noting that we have `hot-shots` working using `protocol: "uds"` (though we are occasionally seeing the "congestion" error). Also, the agent's statsd container is reporting: ``` datadog-q8mmp...

Thanks @rochdev - does that mean my configuration above is sufficient?

> @janeklb Since you said it was working before with UDP, then yes the only change that should be needed (other than the URL pointing to UDS instead of HTTP)...

> I'm also now realizing its possible the custom resolver is part of the problem, but I also think that if Jest could avoid eagerly crawling the filesystem (somehow), and...