-
Notifications
You must be signed in to change notification settings - Fork 606
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
SQLAlchemy: Use SQL operation and DB name as the Span name #254
Merged
codeboten
merged 1 commit into
open-telemetry:master
from
owais:fix-sqlalchemy-operation-name
Jan 20, 2021
Merged
SQLAlchemy: Use SQL operation and DB name as the Span name #254
codeboten
merged 1 commit into
open-telemetry:master
from
owais:fix-sqlalchemy-operation-name
Jan 20, 2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
owais
force-pushed
the
fix-sqlalchemy-operation-name
branch
8 times, most recently
from
December 14, 2020 15:57
1ec0595
to
28fd8d3
Compare
owais
requested review from
a team,
aabmass and
ocelotl
and removed request for
a team
December 14, 2020 16:52
aabmass
reviewed
Dec 14, 2020
...ntelemetry-instrumentation-sqlalchemy/src/opentelemetry/instrumentation/sqlalchemy/engine.py
Outdated
Show resolved
Hide resolved
...ntelemetry-instrumentation-sqlalchemy/src/opentelemetry/instrumentation/sqlalchemy/engine.py
Outdated
Show resolved
Hide resolved
...ntelemetry-instrumentation-sqlalchemy/src/opentelemetry/instrumentation/sqlalchemy/engine.py
Outdated
Show resolved
Hide resolved
Part of #159 |
owais
force-pushed
the
fix-sqlalchemy-operation-name
branch
5 times, most recently
from
January 8, 2021 09:11
8b43444
to
b71d93b
Compare
owais
force-pushed
the
fix-sqlalchemy-operation-name
branch
2 times, most recently
from
January 11, 2021 14:53
75b995a
to
2dfe7cc
Compare
lzchen
approved these changes
Jan 12, 2021
ocelotl
suggested changes
Jan 19, 2021
...ntelemetry-instrumentation-sqlalchemy/src/opentelemetry/instrumentation/sqlalchemy/engine.py
Show resolved
Hide resolved
...ntelemetry-instrumentation-sqlalchemy/src/opentelemetry/instrumentation/sqlalchemy/engine.py
Outdated
Show resolved
Hide resolved
...ntelemetry-instrumentation-sqlalchemy/src/opentelemetry/instrumentation/sqlalchemy/engine.py
Outdated
Show resolved
Hide resolved
...ntelemetry-instrumentation-sqlalchemy/src/opentelemetry/instrumentation/sqlalchemy/engine.py
Outdated
Show resolved
Hide resolved
...ntelemetry-instrumentation-sqlalchemy/src/opentelemetry/instrumentation/sqlalchemy/engine.py
Outdated
Show resolved
Hide resolved
...ntelemetry-instrumentation-sqlalchemy/src/opentelemetry/instrumentation/sqlalchemy/engine.py
Show resolved
Hide resolved
owais
force-pushed
the
fix-sqlalchemy-operation-name
branch
from
January 19, 2021 20:27
2dfe7cc
to
2b9e435
Compare
owais
force-pushed
the
fix-sqlalchemy-operation-name
branch
from
January 20, 2021 09:50
2b9e435
to
928c7a2
Compare
12 tasks
Current instrumentation uses the entire SQL query as the operation name which makes traces very hard to read and understand in addition to introducing high-cardinality issues. This commit fixes the problem by using only the SQL operation name and the DB name instead of the entire query.
owais
force-pushed
the
fix-sqlalchemy-operation-name
branch
from
January 20, 2021 09:55
928c7a2
to
d8cf958
Compare
ocelotl
approved these changes
Jan 20, 2021
codeboten
approved these changes
Jan 20, 2021
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.
👍
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Current instrumentation uses the entire SQL query as the operation name
which makes traces very hard to read and understand in addition to
introducing high-cardinality issues. This commit fixes the problem by
using only the SQL operation name and the DB name instead of the entire
query.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Does This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.