Skip to content

fix(agent-insights): Handle string content in input section #93316

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

ArthurKnaus
Copy link
Member

Handle string content for user and assistant messages in AI Input section of span details.
Use otel keys for tool and model attributes.

@ArthurKnaus ArthurKnaus requested review from a team as code owners June 11, 2025 12:52
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jun 11, 2025
@ArthurKnaus ArthurKnaus merged commit 205489b into master Jun 12, 2025
43 checks passed
@ArthurKnaus ArthurKnaus deleted the aknaus/fix/agent-insights/handle-string-content-in-input-section branch June 12, 2025 08:54
vishnupsatish pushed a commit that referenced this pull request Jun 12, 2025
Handle string content for user and assistant messages in AI Input
section of span details.
Use otel keys for tool and model attributes.

- part of [TET-576: Trace View - Update span details logic to new sdk
data](https://linear.app/getsentry/issue/TET-576/trace-view-update-span-details-logic-to-new-sdk-data)
andrewshie-sentry pushed a commit that referenced this pull request Jun 19, 2025
Handle string content for user and assistant messages in AI Input
section of span details.
Use otel keys for tool and model attributes.

- part of [TET-576: Trace View - Update span details logic to new sdk
data](https://linear.app/getsentry/issue/TET-576/trace-view-update-span-details-logic-to-new-sdk-data)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants