-
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
[Feature] Observability: Inline traces #2277
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… 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`
… `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.
…ke use of AgentaNodesResponse type
…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
…e-baseresponse-version-3.0 (frontend)[Age-1286]: Update web UI to use BaseResponse version 3.0 in the Playground
jp-agenta
changed the title
[Enhancement]: Inline Traces
[Feature] Observability: Inline traces
Nov 25, 2024
jp-agenta
approved these changes
Nov 25, 2024
…f `extract_result_from_response`
…n evaluators_service
jp-agenta
approved these changes
Nov 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Backend
CLI
enhancement
New feature or request
size:XXL
This PR changes 1000+ lines, ignoring generated files.
tests
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces improvements to inline traces in the Playground view, along with backend and web support for running evaluations based on the new base response v3 trace data.