Draft
Conversation
…stinction - Add span data model section grounded in actual backend schema - Clearly separate completion API and agentic API instrumentation - Use `tool` span type for agentic tool executions - Inline span attributes reference - Add TODO section for embedding and multimodal APIs Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
|
||
| ## Span Attributes Reference | ||
|
|
||
| Braintrust-specific OTel span attributes used by the SDK instrumentation: |
Member
There was a problem hiding this comment.
there are more here that the otel based sdks use, like java/ruby/go. I'd just the agent to point at the java or go sdk and get these.
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.
Bit random but just a simple guide summarizing what SDK instrumentation should do and collect.