-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run example/demo error on Mac,no tracing generated #3586
Comments
I guess the emulator outputs environment as Linux. In case of using emulators you may need to tweak the envs manually using https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/docs/config.md |
the emulator outputs the right environment variable , linux with arm64 arch. docker build works fine, intalls the right so,
docker-compose.yaml
otel-dotnet.env hardcode CORECLR_PROFILER_PATH with linux-x64 ,which is wrong under mac m2 pro.
|
@caterchong Shouldn't it be linux-x64 after the emulation? If emulator outputs arm64 instead of x64, it's definitely wrong. |
I couldn't get hold of a arm mac to try to repro this. Until some dev on the SIG can get a hold of one it is going to be hard to make progress without detailed repro steps. |
Bug Report
Symptom
Mac's chip: Apple M2 pro
docker: docker desktop(v4.33.0). settings->General-> User Rosetta for x86_64/amd64 emulation on Apple Silicon opened.
There is no tracing. in demo/log dir, all log files are empty.
check demo-service, /var/log/opentelemetry/dotnet/otel-dotnet-auto-1-Examples.Service-StartupHook-20240822.log
[Error] CLR profiler (64bit) is not found at '/otel-dotnet-auto/linux-x64/OpenTelemetry.AutoInstrumentation.Native.so'. Recheck 'CORECLR_PROFILER_PATH'.
should auto instrument and output tracing normally
bug reason
in demo/otel-dotnet.env
It's hard-coded to linux-x64
The text was updated successfully, but these errors were encountered: