llmobs: clarify we only need evals tag for otel spans when submitted directly to api#33319
Merged
drichards-87 merged 4 commits intomasterfrom Dec 17, 2025
Merged
llmobs: clarify we only need evals tag for otel spans when submitted directly to api#33319drichards-87 merged 4 commits intomasterfrom
drichards-87 merged 4 commits intomasterfrom
Conversation
…ce sdks automatically add the tag
Contributor
Preview links (active after the
|
drichards-87
requested changes
Dec 16, 2025
Contributor
drichards-87
left a comment
There was a problem hiding this comment.
Left a couple of minor pieces of feedback from Docs.
Co-authored-by: DeForest Richards <56796055+drichards-87@users.noreply.github.com>
…ion.md Co-authored-by: DeForest Richards <56796055+drichards-87@users.noreply.github.com>
Co-authored-by: DeForest Richards <56796055+drichards-87@users.noreply.github.com>
drichards-87
approved these changes
Dec 17, 2025
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
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?
Merge instructions
waiting for DataDog/dd-trace-py#15538 and DataDog/dd-trace-js#7113 to be merged
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.
Additional notes