[MLOB-7336] Document automatic user/session tagging from RUM baggage#36240
Draft
Kyle-Verhoog wants to merge 1 commit intomasterfrom
Draft
[MLOB-7336] Document automatic user/session tagging from RUM baggage#36240Kyle-Verhoog wants to merge 1 commit intomasterfrom
Kyle-Verhoog wants to merge 1 commit intomasterfrom
Conversation
Adds a subsection to the LLMObs SDK "Tracking user sessions" doc explaining that the Python and Node.js SDKs now auto-apply session_id, usr.id, and usr.account_id to LLMObs spans when the RUM Browser SDK's propagateTraceBaggage option is enabled. MLOB-7336
Contributor
Preview links (active after the
|
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
1 participant
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?
Fixes MLOB-7336
Documents the new automatic user/session tagging behavior in the Python and Node.js LLMObs SDKs. When the RUM Browser SDK's
propagateTraceBaggageoption is enabled, outgoing requests carry OTel baggage (session.id,user.id,account.id). The LLMObs SDKs now read those values from the active trace context and auto-apply them to LLMObs spans as Datadog standard attributes (session_id,usr.id,usr.account_id). ExplicitLLMObs.annotate()values still take precedence.Companion SDK PRs (land these first):
Parent epic: MLOB-7330
Merge instructions
Merge readiness:
Additional notes
Holding as draft until the SDK PRs ship so the docs don't describe unreleased behavior.