Closed yhan closed 3 years ago
@kevingosse confirmed that this is not supported: https://twitter.com/KooKiz/status/1435878364913541125
@yhan, the libraries we support on .NET Framework are listed in the docs here: https://docs.datadoghq.com/tracing/setup_overview/compatibility_requirements/dotnet-framework/#integrations
ASP.NET Core and Devart.Data.PostgreSql and not listed there, which means the .NET Tracer does not automatically instrument those libraries. Please reach out to support@datadoghq.com if you have any questions about support for a specific library or to request support for a new library. Thanks!
Describe the bug All processes are coded under ASP.NET CORE 2.2 targeting .NET Framework 4.8 hosted in IIS do not emit traces on received HTTP requests.
To Reproduce Here is a sample code with which we can reproduce the problem: https://github.com/yhan/aspdotnetcore.target.dotnetfwk4.8
When I am invoking a testing endpoint: GET http://localhost/api/values/query-google
The tracer DID NOT create an index for GET http://localhost/api/values/query-google, but did created a span for the out-going one:
I expect not only the HTTP client used in the service is detected, but also the server side, which is missing (i.e,
aspnetcore.api.fwk
)Which results the httpclient detected: https://app.datadoghq.eu/apm/traces?query=service%3Aaspnetcore.api.fwk-http-client%20env%3Arecette%20operation_name%3Ahttp.request&cols=core_service%2Ccore_resource_name%2Clog_duration%2Clog_http.method%2Clog_http.status_code&messageDisplay=inline&sort=desc&streamTraces=true&start=1630999636639&end=1631172436639&paused=false
What I consider as expected behavior is that the Tracer emits traces regarding receiving HTTP requests like this:
The expected behavior as above of Microsoft ASP.NET (not ASP.NET Core) targetting .NET Framework 4.8. All processes in ASP.NET CORE 2.2 targeting .NET Framework 4.8 do not work.
Can you please suggest?
Runtime environment (please complete the following information):