Document decimal format requirement for span/trace IDs in LLM Obs OTel evals#35137
Merged
Kyle-Verhoog merged 1 commit intomasterfrom Mar 10, 2026
Merged
Document decimal format requirement for span/trace IDs in LLM Obs OTel evals#35137Kyle-Verhoog merged 1 commit intomasterfrom
Kyle-Verhoog merged 1 commit intomasterfrom
Conversation
…bs OTel evaluations Clarify that span_id and trace_id must be provided as decimal strings when submitting evaluations, especially for OTel users whose instrumentation natively produces hexadecimal IDs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
Kyle-Verhoog
commented
Mar 10, 2026
cswatt
approved these changes
Mar 10, 2026
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.
Summary
span_idandtrace_idmust be decimal strings when submitting evaluations for OTel-instrumented spansotel_instrumentation.md,external_evaluations.md, andapi.mdContext
OTel uses hexadecimal span/trace IDs natively, but the backend stores and matches them as decimal strings. Users submitting evals with hex span IDs were experiencing silent join failures (evals not appearing on spans).
Test plan
🤖 Generated with Claude Code