-
Notifications
You must be signed in to change notification settings - Fork 231
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
[Enhancement] Update SDK to return BaseResponse version 3.0 and new trace tree format #2251
Conversation
… base response to use new trace tree format
- Update version for backward-compatible response (`string` and `funcResponse`) - Update base response trace type to be compatible with the trace tree format from the SDK - Remove condition check for version value in `isBaseResponse`
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
… `CreateSpan` model, and update usage attribute in types
…3.0 and improve nested value extraction - Added handling for version 3.0 response structure. - Introduced a helper function `get_nested_value` to safely retrieve nested values from dictionaries. - Updated trace latency calculation for version 3.0 with microsecond precision. - Enhanced handling of missing or unexpected fields in the response. - Ensured backward compatibility with version 2.0 and generic responses.
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.
@aybruhm
Regarding the SDK, you might want to check apis.fastapi.models.py
and AgentaNodesResponse
/AgentaTreesResponse
/AgentaRootsResponse
to use in trace
in BaseResponse
/
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.
@aybruhm
Regarding the SDK, you might want to check core.observability.service
and ingest
and query
to make sure that the different processing steps are all there, including connect_children()
/calculate_costs()
/cumulate_costs()
/cumulate_tokens()
…eresponse-version30' into feature/age-1288-inline-traces-update-backend-to-use-baseresponse-version30
…eresponse-version30' into feature/age-1288-inline-traces-update-backend-to-use-baseresponse-version30
…eresponse-version30' into AGE-1286/-update-web-ui-to-use-baseresponse-version-3.0
…d extract field values from trace trees for BaseResponse v3.0, with backward compatibility
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.
Left a single comment.
Non-blocking but I'd argue that it's important.
…e-baseresponse-version-3.0 (frontend)[Age-1286]: Update web UI to use BaseResponse version 3.0 in the Playground
…_inputs in map function
…s-update-backend-to-use-baseresponse-version30 [Enhancement] Extend Backend to Support SDK base response version 3.0 for RAG Evaluators
df10790
into
feature-observability/inline-traces
Description:
This PR updates the SDK to remove the legacy inline trace tree format to the new improved format, and refactors the web code to enhance compatibility with the updated SDK.
Related Issue
Closes AGE-1285