-
Notifications
You must be signed in to change notification settings - Fork 142
feat: Add otel spans to tool calls #206
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
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.
agree overall to more instrumentation, just concerned about the LogTraceArguments
option.
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.
This does look helpful, I think we should unconditionally create spans and propagate the context though?
Perhaps we should use the flag to determine whether to instantiate an OTel exporter in our CLI?
I think we've got this addressed and we have span creation by default now with a cleaner contract, if there's anything still outstanding I can throw those changes on too. |
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.
The reflection is a bit odd but I guess it does save an import!
Co-authored-by: Ben Sully <ben.sully@grafana.com>
@sd2k commit + some tidy up for testing and the extra nil checks are done, this should be good to go |
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.
Nice, ty!
TestExtractGrafanaInfoFromHeaders
that was causing failures whenGRAFANA_API_KEY
environment variables were present.