Piotr Kiełkowicz

One more comment, similar breaking change was also introduced into base-collecto version, between 0.41.0 and 0.42.0 0.41.0: `/etc/otel/config.yaml` 0.42.0: `/etc/otelcol/config.yaml` For details, please check https://github.com/open-telemetry/opentelemetry-collector-releases/blob/606b9299551267c8c80c818b057f08a9444458d7/distributions/otelcol/Dockerfile#L19

@vishweshbankwar, on the AutoInstrumentation side also for DevOps scenarios it will be great to have possibility to reconfigure all instrumentation libraries by the environmental variables. Please check https://github.com/open-telemetry/opentelemetry-dotnet-contrib/issues/519

Same issue on my side. It is strange, the same instrumented library is used both for .NET Core 3.1 and .NET 6.0

The issue is related to all async method. Exceptions occurs in managed log file: ```log [2022-08-05T08:48:29.6013132Z] [Error] Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. Could not find...

More data https://www.nuget.org/packages/System.Diagnostics.DiagnosticSource/6.0.0#dependencies-body-tab depends on System.Runtime.CompilerServices.Unsafe v 6.0.0 System.Runtime.CompilerServices.Unsafe.dll v. 6.0.0 is availalbe in two folders in our distribution: * tracer-home\store\x64\netcoreapp3.1\system.runtime.compilerservices.unsafe\6.0.0\lib\netcoreapp3.1 * tracer-home\netcoreapp3.1 When the code related to Unsafe is...

@rajkumar-rangaraj, I can confirm. I have extended standard Splash Screen: ```logs Command line: --redis 63687 Profiler attached: True Platform: x64 DOTNET_ADDITIONAL_DEPS: C:\GitHub\opentelemetry-dotnet-instrumentation\bin\tracer-home\AdditionalDeps DOTNET_SHARED_STORE: C:\GitHub\opentelemetry-dotnet-instrumentation\bin\tracer-home\store ``` The folder matches location on...

Notes after call with @rajkumar-rangaraj Enabled logging for our application based on https://docs.microsoft.com/en-us/dotnet/core/dependency-loading/default-probing#how-do-i-debug-the-probing-properties-construction The results are: ```logs Replacing deps entry [C:\GitHub\opentelemetry-dotnet-instrumentation\test\test-applications\integrations\TestApplication.StackExchangeRedis\bin\x64\Debug\netcoreapp3.1\System.Runtime.CompilerServices.Unsafe.dll, AssemblyVersion:4.0.6.0, FileVersion:4.700.20.12001] with [C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.28\System.Runtime.CompilerServices.Unsafe.dll, AssemblyVersion:4.0.6.0, FileVersion:4.700.22.36301] ``` @rajkumar-rangaraj...

Closing for now, please rise new ticket if we can help.

> Flaky? Is it a problem with the generated password? In my opinion it is not related to generated password. I was able to take generated password from failing execution...

All failures are related to exit code 134. Is it `SIGABORT`?