Getting Started: autoinstrumentation, no spans in the output #3543
Labels
bug
Something isn't working
Comments
tigrannajaryan
changed the title
|
I believe this is a duplicate of #3482 |
flands
added a commit
to flands/opentelemetry.io
that referenced
this issue
Jan 4, 2024
OTel Python automatic instrumentation doesn't support Flask or Werkzeug 3.0+. This will be addressed in [this PR](open-telemetry/opentelemetry-python-contrib#2013) As a result, the automatic instrumentation example doesn't work. This has been an issue since Oct and reported in multiple issues across multiple repositories. The getting started automatic instrumentation does work as it's pinned to versions less than 3.0. Update the documentation for the automatic instrumentation so it work. Addresses: open-telemetry/opentelemetry-python#3543 Also switch to venv over virtualenv to be consistent with getting started documentation and to remove an additional dependency. Once the above PR is merged, both the getting started and automatic instrumentation example documentation should be updated to remove the pinning.
|
Yeah, looks like issues with missing instrumentation for flask 3, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe your environment
Mac OS X
Python 3.9.6
Steps to reproduce
Follow steps in https://opentelemetry.io/docs/instrumentation/python/getting-started/
What is the expected behavior?
Spans in the output.
What is the actual behavior?
No spans in the output. Only logs in the output, which also have 0 traceid and spanid. See attached output.
output.json
Additional context
Part of review open-telemetry/community#1751
The text was updated successfully, but these errors were encountered: