make adding the db.statement tag configurable in jdbc calls #1103
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.
This PR makes it possible to decide whether the db.statement tag is going to be added to spans created by the JDBC instrumentation. There are three possible settings:
db.statement
tag to spansdb.statement
tag when the traced execution was made with a PreparedStatement, which should ensure no placeholder values are leaked to the tracing backenddb.statement
tag to spans