-
Notifications
You must be signed in to change notification settings - Fork 867
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
Update log4j instrumentation docs #4915
Update log4j instrumentation docs #4915
Conversation
…y-base-version-docs
moving to draft to avoid accidentally merging early |
…y-base-version-docs
@@ -22,7 +22,7 @@ To use it, add the module to your application's runtime classpath. | |||
|
|||
```kotlin | |||
dependencies { | |||
runtimeOnly("io.opentelemetry.instrumentation:opentelemetry-log4j-2.13.2:0.17.0-alpha") | |||
runtimeOnly("io.opentelemetry.instrumentation:opentelemetry-log4j-thread-context-2.16-autoconfigure:1.10.0-alpha") |
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.
Uhh, this makes me think about our naming schema...
…y-base-version-docs
Discussed in yesterday special topics meeting, and decided holding doc PRs until release is a hassle, and so |
* Update log4j instrumentation docs for 1.10.0 release * More log4j doc changes for 0.10.0 * Updates for open-telemetry#4937 * Fix log4j documentation * Update instrumentation/log4j/log4j-2.16/library/README.md Co-authored-by: jack-berg <[email protected]>
Doc updates for #4914. This PR is split out if we want to merge during/after 1.10 release.
Or should I just include the doc updates in #4914 and tags can be used now for viewing stable release docs?