Add Java to OpenTelemetry Logs API support page#36719
Merged
Merged
Conversation
dd-trace-java 1.62.0 ships native OpenTelemetry Logs API support and OTLP/HTTP log export. Update the API support page to remove the "not available" warning for Java logs and add Prerequisites, Setup, Examples, Migrate, and Troubleshooting content alongside the existing supported languages.
Contributor
Preview links (active after the
|
Match the structure of the existing Java metrics content in the same file: - Trim Prerequisites to the Datadog SDK + opentelemetry-api version bullets. - Mirror Setup wording and indentation (3-space) used by Java metrics. - Revert Migrate to mirror Setup, matching how Java metrics handles migration (dd-trace-java is an agent-based implementation, not a manual SDK setup, so there is no SdkLoggerProvider/exporter to remove). - Trim Troubleshooting to the two most relevant bullets.
janine-c
approved these changes
May 14, 2026
Contributor
janine-c
left a comment
janine-c
left a comment
There was a problem hiding this comment.
Looks great, Brian! I have some really minor suggestions, but otherwise let's get this published 🚀
The page already lists 'Verify DD_LOGS_OTEL_ENABLED is set to true' as a shared bullet at the top of the Troubleshooting section, so repeating it in the Java-specific block is redundant.
- Backtick `dd-trace-java` in the Java prerequisites for consistency with the other languages in the logs section. - Reorder the opentelemetry-api version qualifier so 'or later' attaches directly to 1.27.0 rather than being split by the parenthetical. - Drop the /opentelemetry/instrument/api_support/java/logs alias since no historical page existed at that URL to redirect from.
mcculls
approved these changes
May 15, 2026
…d fix prereq spacing - Tighten Java troubleshooting bullets in Metrics and Logs sections to explain why the javaagent is required (replaces vague "automatic instrumentation" phrasing) - Add blank line between Java logs prerequisite bullets for consistent rendering Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Duncan Hewett <duncanhewett@users.noreply.github.com>
duncanhewett
approved these changes
May 15, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What does this PR do? What is the motivation?
dd-trace-java1.62.0 ships native OpenTelemetry Logs API support and OTLP/HTTP log export. This PR updates the OpenTelemetry API Support page so the Java + Logs filter combination no longer shows "not available."Specifically, in
content/en/opentelemetry/instrument/dd_sdks/api_support.mdoc.md:javato theincludes()guards for the logs section and the native-implementation note./opentelemetry/instrument/api_support/java/logsalias.Requested in the SDK Capabilities fortnightly status thread.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
AI assistance
Drafted with Claude Code. Java code examples verified against the OTel Logs API and the dd-trace-java 1.62.0 implementation; pre-push code review (two reviewer agents + Codex adversarial review) applied before pushing.
Additional notes
No DOCS Jira ticket filed for this one — happy to add one if the team prefers.