Sean

Experiencing the same thing. The profiler is adding significant CPU usage to containers, in the range of 40-60%.

For those who are running into this, there is a workaround. You can set `skip_child_token = true`. Be aware of the potential security implications when using this workaround: https://registry.terraform.io/providers/hashicorp/vault/latest/docs#skip_child_token https://registry.terraform.io/providers/hashicorp/vault/latest/docs#using-vault-credentials-in-terraform-configuration...

This can also be useful in development to sanity check the traces (especially custom ones) without having to push up to a real environment where datadog agents are available.

I used the musl artifact as its an alpine container: https://github.com/DataDog/dd-trace-dotnet/releases/download/v2.14.0/datadog-dotnet-apm-2.14.0-musl.tar.gz I haven't tested yet with: https://github.com/DataDog/dd-trace-dotnet/releases/download/v2.14.0/datadog-dotnet-apm-2.14.0.arm64.tar.gz EDIT: I'm aware profiling is de-activated on ARM64 at the moment due to...

Switching to https://github.com/DataDog/dd-trace-dotnet/releases/download/v2.14.0/datadog-dotnet-apm-2.14.0.arm64.tar.gz has other issues. LD_PRELOAD doesn't immediately cause problems, however I get a segfault if I try start a dotnet app with: ``` ENV CORECLR_ENABLE_PROFILING=1 ENV CORECLR_PROFILER={846F5F1C-F9AE-4B07-969E-05C26BC060D8} ENV...

There was originally a workaround for this using: https://github.com/sgerrand/alpine-pkg-glibc You have to use `v2.34-r0`, not the latest version which has its own problems. That still seems to get the csharp...

Sure, I can push what I have my side.

@belenkoArrival Yes the problem still exists. I apologize, I haven't had time to push up a PR with the fix (which is quite simple), my youngest son was born just...

For those running into this, it seems to be as a result of a terraform bug when `http_endpoint` isn't explicitly set. Setting `http_endpoint = "enabled"` makes things work as expected.

The only thing I can see that might be wrong is when you change your .fsproj files to use `net6.0`, remember to also change `framework: net5.0` to `framework: net6.0` in...