-
Notifications
You must be signed in to change notification settings - Fork 561
fix(telemetry): prevent double counting of usage metrics #1327
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
fix(telemetry): prevent double counting of usage metrics #1327
Conversation
…vent double counting
|
I created a new pull request for this pull request# 1327 |
|
@rajib76 could you update the code based on this reply: #1267 (comment) I can make the new PR too if preferred. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
a06b5d8 to
adf38bf
Compare
adf38bf to
76a1577
Compare
|
Thank you very much @poshinchen for resolving this so quickly! Would love to connect with you on discord, pls share details if okay with it. This change will go in 1.21.0, right? If yes, when can we expect the package release. |
|
Sorry I don't have discord account. The next release should be on next Tuesday / Wednesday. |
…nts#1327) * fix(telemetry): remove duplicate accumulation of usage metrics to prevent double counting * add langfuse observation type to invoke_agent to prevent double counting --------- Co-authored-by: RAJIB DEB <rajibdeb@mac.lan> Co-authored-by: poshinchen <pschen@amazon.com>
Description
This is a fix for the below bug:
_[BUG] OpenTelemetry token/cost metrics double-counted in Langfuse due to duplicate reporting on parent and child spans #1267
Related Issues
#1267
Documentation PR
Type of Change
Bug fix
Bug fix
New feature
Breaking change
Documentation update
Other (please describe):
Testing
How have you tested the change? Verify that the changes do not break functionality or introduce warnings in consuming repositories: agents-docs, agents-tools, agents-cli
hatch run prepareChecklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.