Add traces to OpenTelemetry source - #38749
Open
maycmlee wants to merge 3 commits into
Open
Conversation
Contributor
Preview links (active after the
|
maycmlee
changed the title
janine-c
approved these changes
Aug 7, 2026
janine-c
left a comment
janine-c
left a comment
Contributor
There was a problem hiding this comment.
Looks great! Looks like this doesn't strictly need approval because it's merging into a branch other than master, but approving anyway to get it out of the queue 🙂
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
2 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?
Adds traces info to OpenTelemetry source.
Child PR of: #38665
For PR reviewer: Most of the content is the same as what's been published for the logs and metrics tabs, so the only updates are that it's for traces.
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Additional notes