ref(tracing): Drop per-string cap on gen_ai log attributes#630
Open
obostjancic wants to merge 1 commit into
Open
ref(tracing): Drop per-string cap on gen_ai log attributes#630obostjancic wants to merge 1 commit into
obostjancic wants to merge 1 commit into
Conversation
Gen-AI log attribute strings were capped at 2,000 characters per value before serialization. Remove the per-string truncation so individual string values are no longer clipped; the 12,000-character cap on the whole serialized attribute still bounds total output, and secret redaction and blob omission are unchanged. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
obostjancic
changed the title
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.
Removes the 2,000-character per-string cap on gen_ai log attributes so values are no longer clipped mid-content. The cap was especially harmful for user messages formatted with XML-style tags, where truncation cut tags in half and broke formatting in Conversations UI (example).
Total output is still bounded by the 12,000-character cap on the whole serialized attribute in
serializeGenAiAttribute; secret redaction and blob omission are unchanged.