.NET Tracer for IIS in windows docker container not working

[ilbarone87]

Tracer Version(s)

3.5

Operating system and platform

Windows Server 2022

Instrumentation Mode

automatic

TFM

.net framework 4.8

Bug Report

Hello,
we have an IIS application written in .NET framework 4.8 that is running in windows docker (docker engine CE).
The application is built on top of a custom image that includes the apm msi installed with the suggested variable from the documentation:

CORECLR_ENABLE_PROFILING=1
CORECLR_PROFILER={846F5F1C-F9AE-4B07-969E-05C26BC060D8}
DD_PROFILING_ENABLE=1

Datadog Agent is running on the host (windows Server 2022) and APM enabled to listen on default port 8126. During the deployment process these arguments get added to the docker run:

DD_AGENT_HOST=docker_default_gateway_ip
DD_TRACE_AGENT_URL=http://HOST_IP:8126/

Anyway none of these seems to help to make the tracing appearing in the datadog traces explorer. I was wondering if we are not hitting some kind of limitations for apm tracing or is actually a bug.

Thanks

Reproduction Code

No response

[lucaspimentel]

Hello, @ilbarone87. Please contact our Support team by creating a new ticket at https://www.datadoghq.com/support/ and include a reference to this issue. This way we can collect additional information about your environment and other data like debug logs or agent flares, that we can't do other GitHub Issues.

Thanks!

edit: You can also use the "Bug Report (Helpdesk)" option when creating a new issue from github.