Fix instrumentation of SQLAlchemy when using sqlalchemy.engine_from_config #2816
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes a bug where SQLAlchemy engines created via
sqlalchemy.engine_from_config(...)
are not instrumented bySQLAlchemyInstrumentor
.sqlalchemy.engine_from_config(...)
directly callscreate_engine(...)
imported fromsqlalchemy.engine.create
. If we don't wrap that copy of thecreate_engine
method then engines created viaengine_from_config
are notinstrumented.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Does This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.