Closed bmorelli25 closed 2 years ago
the below badges are clickable and redirect to their specific view in the CI or DOCS
![]()
![]()
![]()
![]()
![]()
#### Build stats * Start Time: 2022-03-29T20:21:38.775+0000 * Duration: 7 min 8 sec #### Test stats :test_tube: | Test | Results | | ------------ | :-----------------------------: | | Failed | 0 | | Passed | 196 | | Skipped | 0 | | Total | 196 |
To re-run your PR in the CI, just comment with:
/test
: Re-trigger the build.
run
elasticsearch-ci/docs
: Re-trigger the docs validation. (use unformatted text in the comment!)
Because only the 1.x version of the Java agent docs are published, we don't have anywhere to send users who are using a version > 1.30. I'm wondering if we should keep deprecated enable_log_correlation documentation for these users.
See https://github.com/elastic/apm-agent-java/issues/2535#issuecomment-1079852953 - would a plain mention in the agent docs with a similar explanation and/or reference to this page here be sufficient?
See https://github.com/elastic/apm-agent-java/issues/2535#issuecomment-1079852953 - would a plain mention in the agent docs with a similar explanation and/or reference to this page here be sufficient?
Added a note to these docs in cb6d7f6.
Status | Branch | Result |
---|---|---|
ā | 1.x |
Please refer to the Backport tool documentation
Status | Branch | Result |
---|---|---|
ā | 0.x |
Please refer to the Backport tool documentation
Summary
Fixes the following broken links by removing step 2 from the setup guide. Log correlation is enabled by default in version 1.30:
Downside / Question
Because only the 1.x version of the Java agent docs are published, we don't have anywhere to send users who are using a version > 1.30. I'm wondering if we should keep deprecated
enable_log_correlation
documentation for these users. See https://github.com/elastic/apm-agent-java/issues/2535#issuecomment-1075580099 for more context.Related
For https://github.com/elastic/apm-agent-java/issues/2535.
Backport
Backport to
1.x
and0.x
.