-
Notifications
You must be signed in to change notification settings - Fork 226
feat: Add SQL Comment Propagator #1818
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
Open
arielvalentin
wants to merge
8
commits into
open-telemetry:main
Choose a base branch
from
arielvalentin:sql-comment-propagation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
feat: Add SQL Comment Propagator #1818
arielvalentin
wants to merge
8
commits into
open-telemetry:main
from
arielvalentin:sql-comment-propagation
+454
−11
Conversation
This file contains hidden or 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
Implements a helper to propagate context via SQL comments as specified here: > Instrumentations MAY propagate context using SQL commenter by injecting comments into SQL queries before execution. SQL commenter-based context propagation SHOULD NOT be enabled by default, but instrumentation MAY allow users to opt into it. > > The instrumentation implementation SHOULD append the comment to the end of the query. Semantic conventions for individual database systems MAY specify different format, which may include different position, encoding, or schema, depending on the specific database system’s requirements or preferences. > > The instrumentation SHOULD allow users to pass a propagator to overwrite the global propagator. If no propagator is provided by the user, instrumentation SHOULD use the global propagator. https://opentelemetry.io/docs/specs/semconv/database/database-spans/#context-propagation This helper conforms to the propagator inject interface, since it does not ever extract values we are skipping that implementation. Once the processors replaces the obfuscator then we can include the propagators in the SQL gems for trilogy, mysql2, and pg
arielvalentin
commented
Nov 27, 2025
| - name: opentelemetry-sampler-xray | ||
| directory: sampler/xray | ||
| version_constant: [OpenTelemetry, Sampler, XRay, VERSION] | ||
| version_constant: [OpenTelemetry, Sampler, XRay, VERSION] |
Contributor
Author
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.
unrelated but I am fixing a missing new line at the end of this file
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.
Implements a helper to propagate context via SQL comments as specified here:
https://opentelemetry.io/docs/specs/semconv/database/database-spans/#context-propagation
This helper conforms to the propagator inject interface, since it does not ever extract values we are skipping that implementation.
Once the processors replaces the obfuscator then we can include the propagators in the SQL gems for trilogy, mysql2, and pgFixes #479