-
Notifications
You must be signed in to change notification settings - Fork 723
otel-auto-instrumentation-python - __sched_cpufree: symbol not found #3573
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
Comments
@jpicara That stacktrace is a report of not being able to load |
Yeah, it is true that adding that under annotations I am not getting that stacktrace.
However I cannot still see any trace in my backend storage. This is how the CRD is configured
There is not any error log in the applications nor in the opentelemetry operator. Forgot to add that I am using the opentelemetry-operator
Is there anything I am missing or something I could add to find where my traces "are lost" in case they are ingested. |
Are there chances you are sending http traffic to a grpc endpoint? 😅 |
No, as collector is the same than Java components. |
I can see these logs lines in the application related to opentelemetry
Do you please have any clue why it is not working at all? |
Uh oh!
There was an error while loading. Please reload this page.
Describe your environment
No response
What happened?
Hello,
I am trying to get the auto instrumentation for my Python apps. It was successfully tested for my Java components.
Instrumentation CRD (based on https://opentelemetry.io/docs/platforms/kubernetes/operator/automatic/)
Also added the needed annotations under spec.template.metadata.annotations in my app:
Init-container is properly created named: opentelemetry-auto-instrumentation-python:
Successfully pulled image "ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-python:0.53b1
But got the following output on my desired application:
Steps to Reproduce
Created and applied the CRD, added the needed annotation and got the unexpected log output
Expected Result
Traces are being sent properly to my exporter backend.
Actual Result
Not traces visible getting the error message above exposed
Additional context
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: