-
Notifications
You must be signed in to change notification settings - Fork 493
feat(contrib/go-sdk): Initial go-sdk tracer implementation
#4199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
go-sdk tracer implementation
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🔗 Commit SHA: a1b1e1a | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
d680e25 to
e62619f
Compare
e62619f to
79e412f
Compare
4285bb9 to
f99dd20
Compare
d58bedd to
299d5b6
Compare
rarguelloF
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, left a comment about a potential improvement on the llmobs SDK (which can be done/discussed in a future PR)
| type textIOSpan interface { | ||
| AnnotateTextIO(input, output string, opts ...llmobs.AnnotateOption) | ||
| Finish(opts ...llmobs.FinishSpanOption) | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if this kind of code is gonna be common when using our llmobs sdk, it might be worth it to include something in the core llmobs package itself to make life easier for all users.
Maybe AnnotateTextIO should be available in all span types, including AnySpan, WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice if llmobs just exported the textIOSpan interface it already has (llmobs.go:389)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, that's not an interface.
I didn't see an elegant way to publish a nice, reusable interface that's widely useful. Played with it for a bit.
We could add it to all span types but it looks like llm spans don't support it and use messages instead and I don't want methods that are not applicable.
I'm not going to go further down this rabbit hole for now.
299d5b6 to
b30dc5b
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
🚀 New features to boost your workflow:
|
|
View all feedbacks in Devflow UI.
The expected merge time in
This merge request conflicts with another merge request ahead in the queue. The merge requests in front of this one are: |
b30dc5b to
a1b1e1a
Compare
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
The expected merge time in
|

What does this PR do?
Implements tracing of
modelcontextprotocol/go-sdk with the same functionality asmark3labs/mcp-go.Motivation
Closes https://datadoghq.atlassian.net/browse/MLOB-4639
Reviewer's Checklist
./scripts/lint.shlocally.Unsure? Have a question? Request a review!