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
feat: Added ability to recordLlmFeedbackEvent by traceId #2043
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2043 +/- ##
==========================================
- Coverage 97.15% 97.15% -0.01%
==========================================
Files 248 247 -1
Lines 41600 41560 -40
==========================================
- Hits 40418 40378 -40
Misses 1182 1182
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Looks good to me once tests pass. We will need to update all of the existing sample applications, as they all utilize the removed API methods.
Yea I will queue those up. We cannot merge until the agent has been released. |
Ok this Pr will have a branched version of aws-sdk instrumentation. I cannot merge that until we release a new version of the agent |
30e6b8b
to
93d458f
Compare
Description
Updated
api.recordLlmFeedbackEvent
to require atraceId
obtained viaapi.getTraceMetadata
. I also removedgetLlmMessageIds
api as it no longer needed to get the relevant ids to post feedback. Lastly, we no longer need thetx.llm.responses
set to store these ids to be used ingetLlmMessageIds
. This is technically a breaking change but since AIM is in limited preview we are no releasing as a semver major.Related Issues
Closes #2042