Repository navigation
feat(issues): Show the agent run an error was raised in - #130898
Open
sentry-junior[bot] wants to merge 1 commit into
Open
sentry-junior[bot] wants to merge 1 commit into
sentry-junior[bot] wants to merge 1 commit into
Conversation
Behind organizations:issue-details-agent-run. When an error event's trace shows it was raised inside an AI span, issue details gets an Agent Run section with the run's AI spans and a link to the failing span in the trace's Agent Activity tab. When the trace has AI spans but the error is outside them, Trace Preview gets a hint linking to that tab. Co-Authored-By: ale <alexandra.cota@sentry.io>
github-actions
Bot
added
the
Scope: Frontend
This branch was successfully deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue details only links to an error's trace as a plain waterfall. When the error came from an AI agent, the useful view is the trace's Agent Activity tab, but nothing on the issue page points there.
Behind
organizations:issue-details-agent-run(registered in #130897, which must land first):AiSpanTimeline, with the failing step selected. Open Agent Activity and clicking a step link to/trace/<id>/?tab=ai-spans&node=span-<id>, which opens the Agent Activity timeline with that span selected.Detection fetches the event's trace once with the same extra attributes the Agent Activity tab requests. The fetch is pinned to the event's timestamp and ID. It then walks up from the error's span to the nearest AI span and its agent span. The fetch only runs when the flag is on and the issue already shows Trace Preview.
The plan is to enable the flag for the Sentry org first. On our own data, about half of the issues in agent-heavy projects with a stored trace were raised inside an agent run.
I haven't checked the section visually against real data. The first dogfood pass should confirm how it renders on a long agent run.
via ale.
--
View Session [Sentry]