muhaook
muhaook
I think sooner or later we will have requirements to profile otel-auto-instrumentation. e.g. to find out where the CPU spike is or where large memory is used, etc. as far...
the sample application was running on IIS. env info: - Windows Server 2022 - CPU: 1 Core, 2 logical processors, base speed 2.19GHz - Memory: 12GB The sample I was...
## Expected Behavior Assembly should be redirected to 4.2.0.0 during loading System.Net.Http.dll according to [https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/v0.6.0[…]lemetry.AutoInstrumentation.Native/netfx_assembly_redirection.h](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/v0.6.0/src/OpenTelemetry.AutoInstrumentation.Native/netfx_assembly_redirection.h#L96) I am using this sample [WebApiStartupNetfx.zip](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/files/11137476/WebApiStartupNetfx.zip) in the following issues. Note that System.Net.Http.dll did not...
`OTEL_DOTNET_AUTO_PLUGINS `is used to specify plugins, but it can be confusing in some scenarios. e.g. we have both `net4.6.2 `and `net6.0 `applications on IIS and we want to create plugins...
# Bug Report List of [all OpenTelemetry NuGet packages](https://www.nuget.org/profiles/OpenTelemetry) and version that you are using (e.g. `OpenTelemetry 1.0.2`):  Runtime version: `net462` ## Symptom seeing a lot of warnings in...
### Testcontainers version 3.8.0 ### Using the latest Testcontainers version? Yes ### Host OS Linux ### Host arch x86 ### .NET version 8.0.204 ### Docker version ```shell $ podman --version...
### Component OpenTelemetry.Instrumentation.Http ### What is the expected behavior? [OTel spec](https://opentelemetry.io/docs/specs/semconv/http/http-spans/) suggests to use {method} {target} as span name for http client. Currently, only {method} is used. ``` HTTP span...
we have 2 .net framework applications deployed into 1 application pool in IIS. The issue is that the otel-dotnet-auto-instrumentation (1.11.0) can not be triggered for the second application. Looks like...