llmobs: show how to disable otel span conversion #33253
Draft
+26
−0
Conversation
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
Contributor
Preview links (active after the
|
barieom
reviewed
Dec 10, 2025
|
|
||
| </div> | ||
|
|
||
| ## Disabling LLM Observability conversion |
Contributor
There was a problem hiding this comment.
let's move this down all the way to the bottom. Having it this prominent/high up in this doc here may confuse non-APM customers who want to set up
|
|
||
| ## Disabling LLM Observability conversion | ||
|
|
||
| If you'd only like your generative AI spans to remain in APM and not appear in LLM Observability, you can disable the automatic conversion by setting the `dd_llmobs_enabled` attribute to `false`. Setting this attribute on any span in a trace prevents the entire trace from being converted to LLM Observability. |
Contributor
There was a problem hiding this comment.
we should move all this content here to the new doc that'll be added to docs.datadoghq.com/opentelemetry/, linking out to that new section/doc from this section. These instructions are more relevant for existing APM customers
Contributor
Author
There was a problem hiding this comment.
Hmm it kind of seems like other otel integrations put their entry in the integrations page and then link out to their product pages instead? https://docs.datadoghq.com/opentelemetry/integrations/. Although I do see what you're saying. Will think more.
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?
Allow customers to opt out of the apm to llm span conversion when using otel gen ai span attributes
Merge instructions
waiting on https://github.com/DataDog/dd-go/pull/210705
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