-
Notifications
You must be signed in to change notification settings - Fork 621
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
Respect provided tracer provider when instrumenting SQLAlchemy #728
Respect provided tracer provider when instrumenting SQLAlchemy #728
Conversation
...ntelemetry-instrumentation-sqlalchemy/src/opentelemetry/instrumentation/sqlalchemy/engine.py
Outdated
Show resolved
Hide resolved
@jfmyers9 thanks for fixing this. Please sign the CLA as described here: #728 (comment) |
@jfmyers9 thanks. please also add a changelog entry |
f55d582
to
bc02c59
Compare
Working on getting the CLA signed. Will get back to you when I figure that out. |
This change updates the SQLALchemyInstrumentor to respect the tracer provider that is passed in through the kwargs when patching the `create_engine` functionality provided by SQLAlchemy. Previously, it would default to the global tracer provider.
Head branch was pushed to by a user without write access
bc02c59
to
cd32211
Compare
Head branch was pushed to by a user without write access
@owais Is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Description
This change updates the SQLALchemyInstrumentor to respect the tracer provider that is passed in through the kwargs when patching the
create_engine
functionality provided by SQLAlchemy. Previously, it would default to the global tracer provider.Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Unit tested and tested in a real environment.
Does This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.