Ahmed Mezghani

@joneslee85 thank you for mentioning that. The PR it is about the `DD_ENTITY_ID` env var also, if set, it would be very useful to add it as a tag with...

+1 that would be super useful indeed. @ashokirla any chance we could get this soon?

Hi @ppennanen Thank you for reporting this and for the workaround that you suggested (by setting `DD_CRI_SOCKET_PATH` to `null`) We're aware of this issue and we're working on a [fix](https://github.com/DataDog/datadog-operator/pull/51)...

Hey @arzarif ! Thanks for opening this issue and sorry for the trouble. We're looking into it, but it would be super useful for us if you could share any...

Another potential use-case is sending traces to different agents.

@darccio #2319 would definitely help here!

Hi all, sorry for the inconvenience! These logs from the java library indicate that the tracer and profiler couldn't reach the agent, this is likely because of a misconfiguration in...

> Interesting. On our large deployments, sparing 10% of >1GB sounds significant but if you already performed some tests, 90% is probably a value we can go with, knowing that...

Hi @anhkhoa45 Thanks for opening this issue! Could you provide more information about the agent version you're using, and the whether you're using the [KSM core check](https://docs.datadoghq.com/integrations/kubernetes_state_core/) or not? Ideally,...

> is there a unit test here that could be updated to cover this change? There is not - I can probably add new one