-
Notifications
You must be signed in to change notification settings - Fork 881
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
Instrument jdbc batch queries #12797
Conversation
...ary/src/main/java/io/opentelemetry/instrumentation/jdbc/internal/OpenTelemetryStatement.java
Outdated
Show resolved
Hide resolved
...ary/src/main/java/io/opentelemetry/instrumentation/jdbc/internal/OpenTelemetryStatement.java
Outdated
Show resolved
Hide resolved
I didn't see this in the code, did you end up removing it? |
didn't implement it as I couldn't find it in the semconv |
oh, got it, the issue proposed the attribute, thanks 👍 |
@laurit let me know what you think: laurit#408 I'm thinking it's ok to support batches directly in SqlClientAttributesGetter (it will force people to think about it). The other changes are mainly me re-writing some of the extractor code in the process of trying to make it make sense to me. I'm not sure if I ended up just replacing your complex code with my complex code though 😅. |
Updates to jdbc-batch
merged. I also considered this but wasn't sure we want to force the multiple statement handling on all sql instrumentations since jdbc seemed to be the only one that uses it.
|
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.
thanks @laurit!
Part of #12608
Resolves #4476 Note that this issue proposes an attribute (
db.statement.error.count
) for tracking failed statements in the batch which I didn't notice in the semantic conventions.