-
Notifications
You must be signed in to change notification settings - Fork 458
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
Issues with Python AutoInstrumentation #682
Comments
@henrikrexed were you able to resolve this? If yes could you please share what was the problem and if no would it be possible to share a docker image with the reproducer? I am not working on the python ecosystem but @anuraaga could perhaps help here. |
Hi, here is the repo related to the episode : The image generating the issue are : Best regards, |
Are the images just upstream hipstershop source code? |
No i have created a specific version with for a dedicated content explaining how to instrument your code using openTelemetry. Here is the link to the repo : |
Hey @henrikrexed , |
Thanks @mat-rumian! I think it makes sense to add the other propagators to the instrumentation image too. |
Hi, I made the changes on my various deployment files and it works perfectly. |
Hi,
I'm currently building content to promote the Operator.
Side of the content I'm building a tutorial showing how the operator injec the auto instrumentation library.
For the moment the nodejs, java services are very well instrumented , but I'm getting errors with my python services.
Here is the log generated on the container :
How can i resolve this?
The text was updated successfully, but these errors were encountered: