Add JDBC tracing info to the OpenTelemetry guide #24583
Merged
+32
−0
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
|
Thanks for your pull request! The title of your pull request does not follow our editorial rules. Could you have a look?
|
jhalliday
changed the title
gsmet
approved these changes
Mar 28, 2022
| implementation("io.opentelemetry.instrumentation:opentelemetry-jdbc") | ||
| ---- | ||
|
|
||
| As it uses a dedicated JDBC driver, you must configure your datasource and Hibernate to use it. |
There was a problem hiding this comment.
Looks good, thanks!
I will just s/Hibernate/Hibernate ORM/ and merge.
gsmet
added
triage/waiting-for-ci
quarkus-bot
bot
removed
the
triage/waiting-for-ci
|
Does something like this exist for Mongodb? |
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.
OpenTelemetry version of the older OpenTracing JDBC setup steps